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. You cannot apply a Wi-Fi Protected Access 2 (WPA2) pre-authentication Group Policy setting to some client computers that are running Windows 7

You cannot apply a Wi-Fi Protected Access 2 (WPA2) pre-authentication Group Policy setting to some client computers that are running Windows 7

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows 7 or Windows Server 2008 R2.
  • You use the Group Policy Management Console (GPMC) to connect to a Windows Server 2008 R2-based domain controller.
  • You configure the Wireless Network Policy for Windows Vista and Later Releases Group Policy setting for wireless networks (IEEE 802.11) that is located in the following path:
    Computer Configuration\Windows Settings\Security Settings\Wireless Network (IEEE 802.11)
  • You create a profile in the Properties dialog box of the Group Policy setting.
  • You click the Security tab of the dialog box, click the Advanced button, and then enable the This network uses pre-authentication option.
  • You apply the Group Policy setting to some client computers that are running Windows 7.
In this scenario, you experience the following issues:
  • If you generate a report by clicking the Setting tab for the Group Policy object in the GPMC, you notice that the Use Network Pre-authentication option is not enabled.
  • The Use Network Pre-authentication option is not enabled on the client computers.

↑ Back to the top

Cause

This issue occurs because the related Active Directory object is set incorrectly.

↑ 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 that is 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 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

There are no prerequisites for applying this hotfix.

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 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 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 to 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 very important to maintaining 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 7
File nameFile versionFile sizeDateTimePlatform
Wlangpui.dll6.1.7600.20783411,64818-Aug-201004:25x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Wlangpui.dll6.1.7600.20783475,13618-Aug-201005:19x64
Wlangpui.dll6.1.7600.20783411,64818-Aug-201004:25x86
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Wlangpui.dll6.1.7600.20783889,34418-Aug-201004:22IA-64
Wlangpui.dll6.1.7600.20783411,64818-Aug-201004:25x86

↑ Back to the top

Workaround

To work around the issue, edit the related Group Policy object setting manually. To do this, follow these steps: 
  1. Start the Active Directory Service Interfaces (ADSI) Edit tool in the domain, and then connect to the domain controller. To start ADSI Edit, click Start, click Run, type adsiedit.msc, and then click OK.
  2. In the ADSI Edit snap-in, expand the Domain node.
  3. Expand and then locate the CN=System\CN=Policies\CN=<GPO GUID>\CN=Machine\CN=Microsoft\CN=Windows\CN=IEEE80211 container node. Then, click Properties.
  4. Locate the ms-net-ieee-80211-GP-PolicyData attribute in the Properties Editor tab, and then click Edit.
  5. Locate the <preAuthMode> XML tag, and then change the value from disabled to enabled.
  6. Click OK to apply the setting.

↑ 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 WPA2, visit the following Microsoft website:
General information about WPA2
For more information about recommendations and best practices to deploy a wireless network, visit the following Microsoft website: 
Recommendations and best practices for deploying a wireless network
For more information about wireless networking, visit the following Microsoft website:
General information about wireless networking
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 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,642
Date (UTC)18-Aug-2010
Time (UTC)07:26
PlatformNot applicable
File nameX86_cb6b70c638ddcb36b7b5fee39fcb92a6_31bf3856ad364e35_6.1.7600.20783_none_ca8ee527d9df1fba.manifest
File versionNot applicable
File size696
Date (UTC)18-Aug-2010
Time (UTC)07:26
PlatformNot applicable
File nameX86_microsoft-windows-wlangpui_31bf3856ad364e35_6.1.7600.20783_none_40dac847850551f3.manifest
File versionNot applicable
File size11,502
Date (UTC)18-Aug-2010
Time (UTC)05:00
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_efd1b990bdb91b209fd8e7909c789f98_31bf3856ad364e35_6.1.7600.20783_none_01e4c1caf25a0722.manifest
File versionNot applicable
File size1,042
Date (UTC)18-Aug-2010
Time (UTC)07:26
PlatformNot applicable
File nameAmd64_microsoft-windows-wlangpui_31bf3856ad364e35_6.1.7600.20783_none_9cf963cb3d62c329.manifest
File versionNot applicable
File size11,506
Date (UTC)18-Aug-2010
Time (UTC)05:57
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,652
Date (UTC)18-Aug-2010
Time (UTC)07:26
PlatformNot applicable
File nameWow64_microsoft-windows-wlangpui_31bf3856ad364e35_6.1.7600.20783_none_a74e0e1d71c38524.manifest
File versionNot applicable
File size11,504
Date (UTC)18-Aug-2010
Time (UTC)04:47
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_efcc885af9c1a7b7c2b9abaf0069a5be_31bf3856ad364e35_6.1.7600.20783_none_38fc963617ec91ba.manifest
File versionNot applicable
File size1,040
Date (UTC)18-Aug-2010
Time (UTC)07:26
PlatformNot applicable
File nameIa64_microsoft-windows-wlangpui_31bf3856ad364e35_6.1.7600.20783_none_40dc6c3d85035aef.manifest
File versionNot applicable
File size11,504
Date (UTC)18-Aug-2010
Time (UTC)05:49
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,469
Date (UTC)18-Aug-2010
Time (UTC)07:26
PlatformNot applicable
File nameWow64_microsoft-windows-wlangpui_31bf3856ad364e35_6.1.7600.20783_none_a74e0e1d71c38524.manifest
File versionNot applicable
File size11,504
Date (UTC)18-Aug-2010
Time (UTC)04:47
PlatformNot applicable

↑ Back to the top

Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2382370
Revision : 2
Created on : 9/21/2018
Published on : 9/21/2018
Exists online : False
Views : 218