802.1X authentication fails on a Windows 7-based or Windows 2008 R2-based computer that has multiple certificates
Content provided by Microsoft
Applies to: Windows 7 Service Pack 1Windows 7 EnterpriseWindows 7 Home BasicWindows 7 Home PremiumWindows 7 ProfessionalWindows 7 StarterWindows 7 UltimateWindows Server 2008 R2 Service Pack 1Windows Server 2008 R2 DatacenterWindows Server 2008 R2 EnterpriseWindows Server 2008 R2 StandardWindows Server 2008 R2 for Itanium-Based SystemsWindows Server 2008 R2 FoundationWindows Web Server 2008 R2More
You have two Active Directory forests (forest A and forest B) that require 802.1X authentication for both wired and wireless connections.
You establish a forest trust between the two forests.
You have a Windows 7-based or Windows Server 2008 R2-based computer in forest A. The certificate store of the computer contains the following certificates:
An 802.1X authentication certificate that contains a Subject Alternative Name (SAN) field and complies with the Extensible Authentication Protocol-Transport Layer Security (EAP -TLS) requirement.
A certificate that has a different usage and does not contain a SAN field. For example, a CA-HIPS certificate for a Host-based Intrusion Prevention System (HIPS) application.
You migrate the computer from forest A to forest B.
In this scenario, 802.1X authentication for the computer fails.
This issue occurs because the computer certificate selection logic is incorrect.
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 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 one of the following operating systems:
Windows 7 Service Pack 1 (SP1)
Windows Server 2008 R2
Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
To apply this hotfix, 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 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 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:
Windows 7 and Windows Server 2008 R2
Windows 7 and Windows Server 2008 R2
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 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical 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
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the certificate requirements for PEAP and EAP, go to the following Microsoft website: