You have a computer that is running Windows 8 or Windows Server 2012 in a network environment.
You have an IP version 6 (IPv6) router in the network environment.
The router sends a Router Advertisement message to the computer. The Router Advertisement sets the DHCPv6 mode to stateless mode.
In this scenario, the computer does not change to DHCPv6 stateless mode, and instead remains in stateful mode. Therefore, the computer cannot obtain some additional network configuration parameters from a DHCPv6 server, such as the DNS server address.
This issue occurs because the settings that specify the stateful mode are cached. Therefore, the new configuration is not applied.
After you install this hotfix, the "Managed Address Configuration" setting and the "Other Stateful Configuration" settings are set to their default values (M=0/O=0) when you configure a device to behave as a router by turning on the Router Advertisement. The administrator has to reconfigure the settings by using the netsh command according to preference.
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 this specific problem.
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, submit a request to 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 website:
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.
To apply this hotfix, you must be running Windows 8 or Windows Server 2012.
To use the hotfix in this package, you do not have to make any changes to the registry.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global 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 8 and Windows Server 2012 file information notes
Important Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" 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 8" 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
6.2.920 0.20 xxx
Windows 8 and Windows Server 2012
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 8, and Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. 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 8
For all supported x64-based versions of Windows 8 and of Windows Server 2012
To work around the issue, reset the IPv6 configuration state by using the following command:
netsh interface ipv6 reset
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
When you use the DHCPv6 stateless mode in a network environment, an IPv6 router sends a Router Advertisement message to set the managed flag (M) to 0 and the other flag (O) to 1 (in other words, M=0/O=1). When a DHCPv6 client computer receives the Router Advertisement message, the client computer sets the DHCPv6 mode to stateless mode (M=0/O=1).
When you have a Windows 8-based client computer in a network environment that does not have an IPv6 router, no Router Advertisement message will be sent. In this situation, the DHCPv6 client computer sets the DHCPv6 mode to stateful mode (M=1/O=1). This status is cached on the client computer. When the client computer is moved to a network environment that uses DHCPv6 stateless mode, the status cannot be changed from stateful mode (M=1/O=1) to stateless mode (M=0/O=1). Therefore, the client computer cannot obtain some additional network configuration parameters such as the DNS server address.
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 8, and Windows Server 2012
Additional files for all supported x86-based versions of Windows 8