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
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.
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.
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:
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:
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:
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.
Collapse this tableExpand this table
Version
Product
SR_Level
Service branch
6.0.600
1
.
22xxx
Windows Vista and Windows Server 2008
SP1
LDR
6.0.600
2
.
22xxx
Windows Vista and Windows Server 2008
SP2
LDR
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
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Arp.exe
6.0.6001.22608
19,968
19-Jan-2010
19:52
x86
Finger.exe
6.0.6001.22608
10,240
19-Jan-2010
19:52
x86
Hostname.exe
6.0.6001.22608
8,704
19-Jan-2010
19:52
x86
Mrinfo.exe
6.0.6001.22608
11,264
19-Jan-2010
19:52
x86
Netiohlp.dll
6.0.6001.22608
105,472
19-Jan-2010
22:02
x86
Netstat.exe
6.0.6001.22608
27,136
19-Jan-2010
19:52
x86
Route.exe
6.0.6001.22608
17,920
19-Jan-2010
19:52
x86
Tcpsvcs.exe
6.0.6001.22608
9,728
19-Jan-2010
19:52
x86
Arp.exe
6.0.6002.22314
19,968
19-Jan-2010
19:46
x86
Finger.exe
6.0.6002.22314
10,240
19-Jan-2010
19:46
x86
Hostname.exe
6.0.6002.22314
8,704
19-Jan-2010
19:46
x86
Mrinfo.exe
6.0.6002.22314
11,264
19-Jan-2010
19:46
x86
Netiohlp.dll
6.0.6002.22314
106,496
19-Jan-2010
22:00
x86
Netstat.exe
6.0.6002.22314
27,136
19-Jan-2010
19:46
x86
Route.exe
6.0.6002.22314
17,920
19-Jan-2010
19:46
x86
Tcpsvcs.exe
6.0.6002.22314
9,728
19-Jan-2010
19:46
x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Arp.exe
6.0.6001.22608
23,040
19-Jan-2010
20:18
x64
Finger.exe
6.0.6001.22608
11,264
19-Jan-2010
20:18
x64
Hostname.exe
6.0.6001.22608
10,240
19-Jan-2010
20:18
x64
Mrinfo.exe
6.0.6001.22608
12,800
19-Jan-2010
20:18
x64
Netiohlp.dll
6.0.6001.22608
141,824
19-Jan-2010
22:25
x64
Netstat.exe
6.0.6001.22608
32,256
19-Jan-2010
20:18
x64
Route.exe
6.0.6001.22608
21,504
19-Jan-2010
20:18
x64
Tcpsvcs.exe
6.0.6001.22608
10,752
19-Jan-2010
20:18
x64
Arp.exe
6.0.6002.22314
23,040
19-Jan-2010
20:11
x64
Finger.exe
6.0.6002.22314
11,264
19-Jan-2010
20:11
x64
Hostname.exe
6.0.6002.22314
10,240
19-Jan-2010
20:11
x64
Mrinfo.exe
6.0.6002.22314
12,800
19-Jan-2010
20:11
x64
Netiohlp.dll
6.0.6002.22314
144,384
19-Jan-2010
22:04
x64
Netstat.exe
6.0.6002.22314
32,256
19-Jan-2010
20:11
x64
Route.exe
6.0.6002.22314
21,504
19-Jan-2010
20:11
x64
Tcpsvcs.exe
6.0.6002.22314
10,752
19-Jan-2010
20:11
x64
For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Arp.exe
6.0.6001.22608
45,568
19-Jan-2010
11:13
IA-64
Finger.exe
6.0.6001.22608
22,528
19-Jan-2010
11:13
IA-64
Hostname.exe
6.0.6001.22608
15,872
19-Jan-2010
11:13
IA-64
Mrinfo.exe
6.0.6001.22608
25,600
19-Jan-2010
11:13
IA-64
Netiohlp.dll
6.0.6001.22608
263,168
19-Jan-2010
13:00
IA-64
Netstat.exe
6.0.6001.22608
64,000
19-Jan-2010
11:13
IA-64
Route.exe
6.0.6001.22608
45,056
19-Jan-2010
11:13
IA-64
Tcpsvcs.exe
6.0.6001.22608
20,480
19-Jan-2010
11:14
IA-64
Arp.exe
6.0.6002.22314
45,568
19-Jan-2010
11:02
IA-64
Finger.exe
6.0.6002.22314
22,528
19-Jan-2010
11:02
IA-64
Hostname.exe
6.0.6002.22314
15,872
19-Jan-2010
11:02
IA-64
Mrinfo.exe
6.0.6002.22314
25,600
19-Jan-2010
11:02
IA-64
Netiohlp.dll
6.0.6002.22314
267,776
19-Jan-2010
12:48
IA-64
Netstat.exe
6.0.6002.22314
64,000
19-Jan-2010
11:02
IA-64
Route.exe
6.0.6002.22314
45,056
19-Jan-2010
11:02
IA-64
Tcpsvcs.exe
6.0.6002.22314
20,480
19-Jan-2010
11:02
IA-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
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Arp.exe
6.1.7600.16385
20,992
14-Jul-2009
01:14
x86
Finger.exe
6.1.7600.16385
10,240
14-Jul-2009
01:14
x86
Hostname.exe
6.1.7600.16385
8,704
14-Jul-2009
01:14
x86
Mrinfo.exe
6.1.7600.16385
11,264
14-Jul-2009
01:14
x86
Netiohlp.dll
6.1.7600.20618
165,888
15-Jan-2010
20:05
x86
Netstat.exe
6.1.7600.16385
27,136
14-Jul-2009
01:14
x86
Route.exe
6.1.7600.16385
17,920
14-Jul-2009
01:14
x86
Tcpsvcs.exe
6.1.7600.16385
9,216
14-Jul-2009
01:14
x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Arp.exe
6.1.7600.16385
24,064
14-Jul-2009
01:38
x64
Finger.exe
6.1.7600.16385
11,264
14-Jul-2009
01:39
x64
Hostname.exe
6.1.7600.16385
9,728
14-Jul-2009
01:39
x64
Mrinfo.exe
6.1.7600.16385
12,800
14-Jul-2009
01:39
x64
Netiohlp.dll
6.1.7600.20618
214,528
15-Jan-2010
20:05
x64
Netstat.exe
6.1.7600.16385
31,744
14-Jul-2009
01:39
x64
Route.exe
6.1.7600.16385
21,504
14-Jul-2009
01:39
x64
Tcpsvcs.exe
6.1.7600.16385
10,240
14-Jul-2009
01:39
x64
For all supported IA-64-based versions of Windows Server 2008 R2
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.
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