To resolve this issue, install the following hotfix on the computer. Note
The hotfix does not support scenarios in which the cryptographic service provider (CSP) does not allow the PIN to be transferred programmatically.
Third party CSP's are also required to respond to the function call CryptGetProvParam() (s. http://msdn.microsoft.com/en-us/library/ms938119.aspx
) for PP_IMPTYPE with CRYPT_IMPL_REMOVABLE.
By default, the Certificate Trust List Filtering feature is installed and enabled after you install the hotfix. The Certificate Trust List Filtering feature filters the certificate choice UI presented to users by querying the certificate trust list from the server then filtering the client authentication certificate choice UI to only show certificates that whose issuers are in the trust list presented by the server. You can disable this behavior by setting the DWORD value of the following registry key to 0:
By default the Automatic Cert Selection feature is installed and enabled after you install the hotfix. The Automatic Cert selection feature automatically selects the appropriate client authentication certificate from the certificate store if there is only a single client authentication certificate in the store. You can disable this behavior by setting the DWORD value of the following registry entry to 0:
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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
- 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:
Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
To apply 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 7 and Windows Server 2008 R2 file information notesImportant
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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
| Version||Product||SR_Level||Service branch|
|6.1.760 0. 21xxx||Windows 7 and Windows Server 2008 R2||RTM||LDR|
|6.1.760 1. 21xxx||Windows 7 and Windows Server 2008 R2||SP1||LDR|
- 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 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 7
|File name||File version||File size||Date||Time|
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
|File name||File version||File size||Date||Time||Platform|
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.