Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. The command "netsh interface ipv4 dump" does not export the subnet mask setting in Windows 7, in Windows Server 2008 R2, in Windows Server 2008, and in Windows Vista

The command "netsh interface ipv4 dump" does not export the subnet mask setting in Windows 7, in Windows Server 2008 R2, in Windows Server 2008, and in Windows Vista

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You use the netsh interface ipv4 dump command to export and back up the persistent configuration settings for the network interface on a computer that is running one of the following operating systems:
    • Windows 7
    • Windows Server 2008 R2
    • Windows Server 2008
    • Windows Vista
  • You import this backup of the configuration settings.
In this scenario, an incorrect subnet mask is set.

Note The Netsh command can output the script for the network configuration settings of the computer. By using this command, you can copy the script so that you can run the script to restore the settings if you reinstall the operating system.

↑ Back to the top

Cause

This issue occurs because the information about the subnet mask is not exported when you run the netsh interface ipv4 dump command. Therefore, an incorrect subnet mask is set when you import the backup of the configuration settings.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, your computer must be running one of the following operating systems:
  • Windows Vista Service Pack 1 (SP1)
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows 7
  • Windows Server 2008 R2
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600 1 . 22xxxWindows Vista and Windows Server 2008SP1LDR
    6.0.600 2 . 22xxxWindows Vista and Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Arp.exe6.0.6001.2260819,96819-Jan-201019:52x86
Finger.exe6.0.6001.2260810,24019-Jan-201019:52x86
Hostname.exe6.0.6001.226088,70419-Jan-201019:52x86
Mrinfo.exe6.0.6001.2260811,26419-Jan-201019:52x86
Netiohlp.dll6.0.6001.22608105,47219-Jan-201022:02x86
Netstat.exe6.0.6001.2260827,13619-Jan-201019:52x86
Route.exe6.0.6001.2260817,92019-Jan-201019:52x86
Tcpsvcs.exe6.0.6001.226089,72819-Jan-201019:52x86
Arp.exe6.0.6002.2231419,96819-Jan-201019:46x86
Finger.exe6.0.6002.2231410,24019-Jan-201019:46x86
Hostname.exe6.0.6002.223148,70419-Jan-201019:46x86
Mrinfo.exe6.0.6002.2231411,26419-Jan-201019:46x86
Netiohlp.dll6.0.6002.22314106,49619-Jan-201022:00x86
Netstat.exe6.0.6002.2231427,13619-Jan-201019:46x86
Route.exe6.0.6002.2231417,92019-Jan-201019:46x86
Tcpsvcs.exe6.0.6002.223149,72819-Jan-201019:46x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Arp.exe6.0.6001.2260823,04019-Jan-201020:18x64
Finger.exe6.0.6001.2260811,26419-Jan-201020:18x64
Hostname.exe6.0.6001.2260810,24019-Jan-201020:18x64
Mrinfo.exe6.0.6001.2260812,80019-Jan-201020:18x64
Netiohlp.dll6.0.6001.22608141,82419-Jan-201022:25x64
Netstat.exe6.0.6001.2260832,25619-Jan-201020:18x64
Route.exe6.0.6001.2260821,50419-Jan-201020:18x64
Tcpsvcs.exe6.0.6001.2260810,75219-Jan-201020:18x64
Arp.exe6.0.6002.2231423,04019-Jan-201020:11x64
Finger.exe6.0.6002.2231411,26419-Jan-201020:11x64
Hostname.exe6.0.6002.2231410,24019-Jan-201020:11x64
Mrinfo.exe6.0.6002.2231412,80019-Jan-201020:11x64
Netiohlp.dll6.0.6002.22314144,38419-Jan-201022:04x64
Netstat.exe6.0.6002.2231432,25619-Jan-201020:11x64
Route.exe6.0.6002.2231421,50419-Jan-201020:11x64
Tcpsvcs.exe6.0.6002.2231410,75219-Jan-201020:11x64
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Arp.exe6.0.6001.2260845,56819-Jan-201011:13IA-64
Finger.exe6.0.6001.2260822,52819-Jan-201011:13IA-64
Hostname.exe6.0.6001.2260815,87219-Jan-201011:13IA-64
Mrinfo.exe6.0.6001.2260825,60019-Jan-201011:13IA-64
Netiohlp.dll6.0.6001.22608263,16819-Jan-201013:00IA-64
Netstat.exe6.0.6001.2260864,00019-Jan-201011:13IA-64
Route.exe6.0.6001.2260845,05619-Jan-201011:13IA-64
Tcpsvcs.exe6.0.6001.2260820,48019-Jan-201011:14IA-64
Arp.exe6.0.6002.2231445,56819-Jan-201011:02IA-64
Finger.exe6.0.6002.2231422,52819-Jan-201011:02IA-64
Hostname.exe6.0.6002.2231415,87219-Jan-201011:02IA-64
Mrinfo.exe6.0.6002.2231425,60019-Jan-201011:02IA-64
Netiohlp.dll6.0.6002.22314267,77619-Jan-201012:48IA-64
Netstat.exe6.0.6002.2231464,00019-Jan-201011:02IA-64
Route.exe6.0.6002.2231445,05619-Jan-201011:02IA-64
Tcpsvcs.exe6.0.6002.2231420,48019-Jan-201011:02IA-64
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Arp.exe6.1.7600.1638520,99214-Jul-200901:14x86
Finger.exe6.1.7600.1638510,24014-Jul-200901:14x86
Hostname.exe6.1.7600.163858,70414-Jul-200901:14x86
Mrinfo.exe6.1.7600.1638511,26414-Jul-200901:14x86
Netiohlp.dll6.1.7600.20618165,88815-Jan-201020:05x86
Netstat.exe6.1.7600.1638527,13614-Jul-200901:14x86
Route.exe6.1.7600.1638517,92014-Jul-200901:14x86
Tcpsvcs.exe6.1.7600.163859,21614-Jul-200901:14x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Arp.exe6.1.7600.1638524,06414-Jul-200901:38x64
Finger.exe6.1.7600.1638511,26414-Jul-200901:39x64
Hostname.exe6.1.7600.163859,72814-Jul-200901:39x64
Mrinfo.exe6.1.7600.1638512,80014-Jul-200901:39x64
Netiohlp.dll6.1.7600.20618214,52815-Jan-201020:05x64
Netstat.exe6.1.7600.1638531,74414-Jul-200901:39x64
Route.exe6.1.7600.1638521,50414-Jul-200901:39x64
Tcpsvcs.exe6.1.7600.1638510,24014-Jul-200901:39x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Arp.exe6.1.7600.1638548,12814-Jul-200901:44IA-64
Finger.exe6.1.7600.1638522,52814-Jul-200901:44IA-64
Hostname.exe6.1.7600.1638514,33614-Jul-200901:44IA-64
Mrinfo.exe6.1.7600.1638529,18414-Jul-200901:44IA-64
Netiohlp.dll6.1.7600.20618377,85615-Jan-201009:36IA-64
Netstat.exe6.1.7600.1638566,56014-Jul-200901:44IA-64
Route.exe6.1.7600.1638545,56814-Jul-200901:44IA-64
Tcpsvcs.exe6.1.7600.1638518,94414-Jul-200901:45IA-64

↑ Back to the top

Workaround

To work around the issue, add the correct subnet mask to the configuration settings that you exported. When you import the configuration settings that you modified, the Netsh command adds the correct subnet mask.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More information

The following is a sample of the output for the netsh interface ipv4 dump command when this issue occurs: 
------------------------------------
# ----------------------------------
# IPv4 Configuration
# ----------------------------------
pushd interface ipv4

reset
set global icmpredirects=enabled
add route prefix=0.0.0.0/0 interface="Local Area Connection" nexthop=<IP>
add address name="Local Area Connection" address=<IP> 

popd
# End of IPv4 configuration
For example, assume that you have defined a subnet mask of 255.255.254.0 in your static IP v4 configuration settings. In this scenario, the following are the two possible expected results for the line that has the "add address" text in the output:
  • add address name="Local Area Connection" address=<IP Address> mask=255.255.254.0
  • add address name="Local Area Connection" address=<IP Address>/23
General information about Interface Internet Protocol version 4 (IPv4)

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
File nameUpdate.mum
File versionNot Applicable
File size51,736
Date (UTC)20-Jan-2010
Time (UTC)10:10
PlatformNot Applicable
File nameX86_microsoft-windows-tcpip-utility_31bf3856ad364e35_6.0.6002.22314_none_35303d1765268ab1.manifest
File versionNot Applicable
File size17,143
Date (UTC)20-Jan-2010
Time (UTC)00:05
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
File nameAmd64_microsoft-windows-tcpip-utility_31bf3856ad364e35_6.0.6001.22608_none_8f7737c72051f02e.manifest
File versionNot Applicable
File size17,193
Date (UTC)20-Jan-2010
Time (UTC)00:26
PlatformNot Applicable
File nameAmd64_microsoft-windows-tcpip-utility_31bf3856ad364e35_6.0.6002.22314_none_914ed89b1d83fbe7.manifest
File versionNot Applicable
File size17,193
Date (UTC)20-Jan-2010
Time (UTC)00:08
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size52,268
Date (UTC)20-Jan-2010
Time (UTC)10:10
PlatformNot Applicable
File name
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_microsoft-windows-tcpip-utility_31bf3856ad364e35_6.0.6001.22608_none_335a403967f287f4.manifest
File versionNot Applicable
File size17,168
Date (UTC)20-Jan-2010
Time (UTC)02:47
PlatformNot Applicable
File nameIa64_microsoft-windows-tcpip-utility_31bf3856ad364e35_6.0.6002.22314_none_3531e10d652493ad.manifest
File versionNot Applicable
File size17,168
Date (UTC)20-Jan-2010
Time (UTC)01:13
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size9,510
Date (UTC)20-Jan-2010
Time (UTC)10:09
PlatformNot Applicable
File name

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameUpdate.mum
File versionNot Applicable
File size1,674
Date (UTC)15-Jan-2010
Time (UTC)23:19
PlatformNot Applicable
File nameX86_0932882306b030090a9e922edb4b3ef9_31bf3856ad364e35_6.1.7600.20618_none_481e3646c46882ed.manifest
File versionNot Applicable
File size701
Date (UTC)15-Jan-2010
Time (UTC)23:19
PlatformNot Applicable
File nameX86_microsoft-windows-tcpip-utility_31bf3856ad364e35_6.1.7600.20618_none_33759ab6c913daaa.manifest
File versionNot Applicable
File size7,600
Date (UTC)15-Jan-2010
Time (UTC)23:25
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_0932882306b030090a9e922edb4b3ef9_31bf3856ad364e35_6.1.7600.20618_none_a43cd1ca7cc5f423.manifest
File versionNot Applicable
File size703
Date (UTC)15-Jan-2010
Time (UTC)23:19
PlatformNot Applicable
File nameAmd64_77c6ad43c0dfde8c1e87da9dc69c2143_31bf3856ad364e35_6.1.7600.20618_none_fcf12ab94fb9ee7a.manifest
File versionNot Applicable
File size705
Date (UTC)15-Jan-2010
Time (UTC)23:19
PlatformNot Applicable
File nameAmd64_microsoft-windows-tcpip-utility_31bf3856ad364e35_6.1.7600.20618_none_8f94363a81714be0.manifest
File versionNot Applicable
File size7,604
Date (UTC)15-Jan-2010
Time (UTC)23:30
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,328
Date (UTC)15-Jan-2010
Time (UTC)23:19
PlatformNot Applicable
File name
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_0932882306b030090a9e922edb4b3ef9_31bf3856ad364e35_6.1.7600.20618_none_481fda3cc4668be9.manifest
File versionNot Applicable
File size702
Date (UTC)15-Jan-2010
Time (UTC)23:19
PlatformNot Applicable
File nameIa64_47c648801c0fc44a474d128d8cb40a8f_31bf3856ad364e35_6.1.7600.20618_none_2681626234e4cab6.manifest
File versionNot Applicable
File size703
Date (UTC)15-Jan-2010
Time (UTC)23:19
PlatformNot Applicable
File nameIa64_microsoft-windows-tcpip-utility_31bf3856ad364e35_6.1.7600.20618_none_33773eacc911e3a6.manifest
File versionNot Applicable
File size7,602
Date (UTC)15-Jan-2010
Time (UTC)23:19
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size1,684
Date (UTC)15-Jan-2010
Time (UTC)23:19
PlatformNot Applicable
File name

↑ Back to the top

Keywords: kbqfe, kbhotfixserver, kbsurveynew, kbautohotfix, kbexpertiseinter, kbbug, kbfix, KB979101

↑ Back to the top

Article Info
Article ID : 979101
Revision : 1
Created on : 2/9/2010
Published on : 2/9/2010
Exists online : False
Views : 975