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 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.Prerequisites
To apply this hotfix, you must be running running one of the following operating systems:
- Windows 7 Service Pack 1 (SP1)
- Windows Server 2008 R2 Service Pack 1 (SP1)
- Windows 8
- Windows Server 2012
For more information about how to obtain a Windows 7 or a 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
Registry information
After you apply this hotfix, follow these steps to enable or disable the function that lets users change the smart card PIN:
- Start Registry Editor. To do this, press the Windows logo key+R, type regedit, and then click OK.
- Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\ - On the Edit menu, point to New, and then click Key.
- Type SmartCardCredentialProvider, and then press Enter.
- On the Edit menu, point to New, and then click DWORD Value.
- Perform one of the following actions, based on the kind of smart card on which you want to restrict functionality:
- For VSCs, type AllowVirtualSmartCardPinChangeAndUnlock, and then click Modify.
- For physical smart cards, type AllowSmartCardPinChangeAndUnblock, and then click Modify.
- Type 1 in the value data box, and then click OK.
Note If you set either the AllowVirtualSmartCardPinChangeAndUnlock or AllowSmartCardPinChangeAndUnblock value to 1, users can change the format of the PIN. If you set the value to 0, users cannot change the format of the PIN. - On the Edit menu, point to New, and then click REG_SZ or REG_EXPAND_SZ Value.
- Perform one of the following actions, based on the kind of smart card on which you want to restrict functionality:
- For VSCs, type VirtualSmartCardPinChangeAndUnlockString, and then click Modify.
- For physical smart cards, type SmartCardPinChangeAndUnblockString, and then click Modify.
- You can use the VirtualSmartCardPinChangeAndUnlockString and SmartCardPinChangeAndUnblockString registry values to display information on the user's computer. Type any information that you want to provide to the user, and then click OK.
- Exit Registry Editor.
You can set the
VirtualSmartCardPinChangeAndUnlockString or
SmartCardPinChangeAndUnblockString registry entry value to REG_SZ
or
REG_EXPAND_SZ. If you want the text on the Secure Desktop screen to contain carriage returns, follow these steps to change the binary data of the registry entry:
- Set the VirtualSmartCardPinChangeAndUnlockString or SmartCardPinChangeAndUnblockString registry entry value to REG_EXPAND_SZ, and then input the text that you want to display to users.
- Right-click the registry entry that you set in step 1, and then click Modify binary data....
- Add "0D 00 0A 00" in each location that you want a line break to appear.
Note You can use Group Policy to set the registry entry to REG_EXPAND_SZ for a string that does not contain line breaks in the binary data. However, if you want the string to contain line breaks, edit the string, export the "0D 00 0A 00" values as an .REG file, and then deploy the .REG file. To do this, use Group Policy to run a startup, shutdown, logon, and logoff script.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 How to back up and restore the registry in Windows
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
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, 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
1.
22xxx | 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 | Platform |
|---|
| Smartcardcredentialprovider.dll | 6.1.7601.22298 | 152,576 | 13-Apr-2013 | 04:59 | x86 |
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
| File name | File version | File size | Date | Time | Platform |
|---|
| Smartcardcredentialprovider.dll | 6.1.7601.22298 | 190,976 | 13-Apr-2013 | 05:24 | x64 |
| Smartcardcredentialprovider.dll | 6.1.7601.22298 | 152,576 | 13-Apr-2013 | 04:59 | x86 |
For all supported IA-64-based versions of Windows Server 2008 R2
| File name | File version | File size | Date | Time | Platform |
|---|
| Smartcardcredentialprovider.dll | 6.1.7601.22298 | 344,064 | 13-Apr-2013 | 04:38 | IA-64 |
| Smartcardcredentialprovider.dll | 6.1.7601.22298 | 152,576 | 13-Apr-2013 | 04:59 | x86 |
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:
| Version | Product | Milestone | Service branch |
|---|
| 6.2.920 0.20 xxx | Windows 8 and Windows Server 2012 | RTM | 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 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
| File name | File version | File size | Date | Time | Platform |
|---|
| Smartcardcredentialprovider.dll | 6.2.9200.20685 | 687,104 | 11-Apr-2013 | 22:35 | x86 |
For all supported x64-based versions of Windows 8 and of Windows Server 2012
| File name | File version | File size | Date | Time | Platform |
|---|
| Smartcardcredentialprovider.dll | 6.2.9200.20682 | 876,032 | 11-Apr-2013 | 23:17 | x64 |
| Smartcardcredentialprovider.dll | 6.2.9200.20685 | 687,104 | 11-Apr-2013 | 22:35 | x86 |