You cannot configure DHCPv6 stateless mode to be used by a Windows 8-based or Windows Server 2012-based computer

Article translations Article translations
Article ID: 2822311 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • 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.

Cause

This issue occurs because the settings that specify the stateful mode are cached. Therefore, the new configuration is not applied.

Resolution

This hotfix is also available at Microsoft Update Catalog.

Hotfix information

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:
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, you must be running Windows 8 or Windows Server 2012.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

Collapse this imageExpand this image
assets folding start collapsed
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:
    Collapse this tableExpand this table
    VersionProductMilestoneService branch
    6.2.920 0.20 xxxWindows 8 and Windows Server 2012RTMLDR
  • 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
Collapse this imageExpand this image
assets folding start collapsed
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.2.9200.16548271,08002-Mar-201309:21x86
Tcpip.sys6.2.9200.165811,802,50411-Apr-201304:20x86
Fwpkclnt.sys6.2.9200.16384271,08826-Jul-201203:30x86
Tcpip.sys6.2.9200.206851,817,35211-Apr-201304:52x86
Collapse this imageExpand this image
assets folding end collapsed
For all supported x64-based versions of Windows 8 and of Windows Server 2012
Collapse this imageExpand this image
assets folding start collapsed
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.2.9200.16547411,88002-Mar-201309:59x64
Tcpip.sys6.2.9200.165812,231,56010-Apr-201322:45x64
Fwpkclnt.sys6.2.9200.16384411,88826-Jul-201204:43x64
Tcpip.sys6.2.9200.206852,225,92811-Apr-201306:41x64
Collapse this imageExpand this image
assets folding end collapsed
Collapse this imageExpand this image
assets folding end collapsed


Workaround

To work around the issue, reset the IPv6 configuration state by using the following command:
netsh interface ipv6 reset

Status

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

More information

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

Collapse this imageExpand this image
assets folding start collapsed

Additional file information for Windows 8, and Windows Server 2012

Additional files for all supported x86-based versions of Windows 8
Collapse this imageExpand this image
assets folding start collapsed
Collapse this tableExpand this table
File nameX86_1ae067ae2a407a9490c02b1021791c92_31bf3856ad364e35_6.2.9200.16581_none_c5d35dd581bf43a6.manifest
File versionNot applicable
File size702
Date (UTC)11-Apr-2013
Time (UTC)15:45
PlatformNot applicable
File nameX86_60fa689f2502da573d6065599bd89fdb_31bf3856ad364e35_6.2.9200.20685_none_de7a25a4d10e5dc5.manifest
File versionNot applicable
File size702
Date (UTC)11-Apr-2013
Time (UTC)15:45
PlatformNot applicable
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.16581_none_afc6212137cfb400.manifest
File versionNot applicable
File size3,883
Date (UTC)11-Apr-2013
Time (UTC)15:45
PlatformNot applicable
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.20685_none_b053bf1450e9b926.manifest
File versionNot applicable
File size3,883
Date (UTC)11-Apr-2013
Time (UTC)15:45
PlatformNot applicable
Collapse this imageExpand this image
assets folding end collapsed
Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
Collapse this imageExpand this image
assets folding start collapsed
Collapse this tableExpand this table
File nameAmd64_68843deba67747344af3c6306fee0b5a_31bf3856ad364e35_6.2.9200.20685_none_234a37892ce3503c.manifest
File versionNot applicable
File size706
Date (UTC)11-Apr-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_dd5b9beea0b8e16af2f8298e386ec379_31bf3856ad364e35_6.2.9200.16581_none_7875693241490e1d.manifest
File versionNot applicable
File size706
Date (UTC)11-Apr-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.16581_none_0be4bca4f02d2536.manifest
File versionNot applicable
File size3,887
Date (UTC)11-Apr-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.20685_none_0c725a9809472a5c.manifest
File versionNot applicable
File size3,887
Date (UTC)11-Apr-2013
Time (UTC)15:46
PlatformNot applicable
Collapse this imageExpand this image
assets folding end collapsed
Collapse this imageExpand this image
assets folding end collapsed

Properties

Article ID: 2822311 - Last Review: July 5, 2013 - Revision: 3.0
Applies to
  • Windows 8
  • Windows 8 Enterprise
  • Windows 8 Pro
  • Windows Server 2012 Datacenter
  • Windows Server 2012 Essentials
  • Windows Server 2012 Foundation
  • Windows Server 2012 Standard
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseadvanced KB2822311

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com