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.

The default gateway is missing on a computer that is running Windows Server 2008 or Windows Vista after the computer restarts if the default gateway is set by using the Netsh command


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You use the netsh command to enable a network interface on a computer that is running Windows Server 2008 or Windows Vista. The computer retrieves IP addresses from a DHCP server.
  • You use the netsh command to set a default gateway for the network interface.
In this scenario, the default gateway is set successfully. You can verify it by running the ipconfig /all command. However, the default gateway of the network interface is missing after the computer restarts. If you double-click the following registry entry, you find that a null character exists in the value data of the DefaultGateway subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<GUID>\DefaultGateway
Note <GUID> is the interface value of the network card.

↑ Back to the top


Cause

The Netsh int ipv4 set address command incorrectly adds a Unicode null character before the value of the actual IP address.

↑ 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: 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 Windows operating systems:
  • Windows Vista Service Pack 1 (SP1)
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)
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 of these 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
    VersionProductSR_LevelService branch
    6.0.600 0 . 20xxxWindows VistaRTMLDR
    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 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 nameFile versionFile sizeDateTimePlatform
Cimwin32.dll6.0.6001.225641,374,72016-Nov-200914:08x86
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Cimwin32.dll6.0.6002.222681,373,69616-Nov-200913:58x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Cimwin32.dll6.0.6001.225642,104,83216-Nov-200914:45x64
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Cimwin32.dll6.0.6002.222682,104,83216-Nov-200913:57x64
For all supported IA-64-based versions of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Cimwin32.dll6.0.6001.225644,315,64816-Nov-200916:29IA-64
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Cimwin32.dll6.0.6002.222684,315,64816-Nov-200913:50IA-64

↑ Back to the top


Workaround

To work around the issue, use the following command to set the default gateway on the interface:
Netsh int ipv4 set address <Interface Name> source=dhcp

↑ 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

For more information about the Netsh commands for Interface Internet Protocol version 4 (IPv4), visit the following Microsoft Web site: http://technet.microsoft.com/en-us/library/cc731521(WS.10).aspx

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

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Package_for_kb973243_client_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,36717-Nov-200909:30Not Applicable
Package_for_kb973243_client_2~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,69317-Nov-200909:30Not Applicable
Package_for_kb973243_client~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,71317-Nov-200909:30Not Applicable
Package_for_kb973243_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42117-Nov-200909:30Not Applicable
Package_for_kb973243_sc_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,69017-Nov-200909:30Not Applicable
Package_for_kb973243_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,70117-Nov-200909:30Not Applicable
Package_for_kb973243_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42517-Nov-200909:30Not Applicable
Package_for_kb973243_server_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,69417-Nov-200909:30Not Applicable
Package_for_kb973243_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,71317-Nov-200909:30Not Applicable
X86_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_6.0.6001.22564_none_cff7b7341f5a6ced.manifestNot Applicable14,34616-Nov-200917:34Not Applicable
X86_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_6.0.6002.22268_none_d1e22a441c7d276d.manifestNot Applicable14,34616-Nov-200916:00Not Applicable
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_6.0.6001.22564_none_2c1652b7d7b7de23.manifestNot Applicable14,67916-Nov-200918:59Not Applicable
Amd64_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_6.0.6002.22268_none_2e00c5c7d4da98a3.manifestNot Applicable14,67916-Nov-200918:41Not Applicable
Package_for_kb973243_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,37517-Nov-200909:30Not Applicable
Package_for_kb973243_client_2~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,70517-Nov-200909:30Not Applicable
Package_for_kb973243_client~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,72317-Nov-200909:30Not Applicable
Package_for_kb973243_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,42917-Nov-200909:30Not Applicable
Package_for_kb973243_sc_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,70217-Nov-200909:30Not Applicable
Package_for_kb973243_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,71117-Nov-200909:30Not Applicable
Package_for_kb973243_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43317-Nov-200909:30Not Applicable
Package_for_kb973243_server_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,70617-Nov-200909:30Not Applicable
Package_for_kb973243_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,72317-Nov-200909:30Not Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ia64_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_6.0.6001.22564_none_cff95b2a1f5875e9.manifestNot Applicable14,64817-Nov-200902:12Not Applicable
Ia64_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_6.0.6002.22268_none_d1e3ce3a1c7b3069.manifestNot Applicable14,64816-Nov-200915:17Not Applicable
Package_for_kb973243_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42517-Nov-200909:30Not Applicable
Package_for_kb973243_sc_1~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,52917-Nov-200909:30Not Applicable
Package_for_kb973243_sc~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,70617-Nov-200909:30Not Applicable
Package_for_kb973243_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42917-Nov-200909:30Not Applicable
Package_for_kb973243_server_1~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,53317-Nov-200909:30Not Applicable
Package_for_kb973243_server~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,71717-Nov-200909:30Not Applicable

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 973243
Revision : 6
Created on : 2/16/2011
Published on : 2/16/2011
Exists online : False
Views : 865