Hotfix is available that disables the function that lets users change the format of a physical smart card PIN or a VSC PIN in Windows 7, Windows 8, Windows Server 2008 R2, or Windows Server 2012

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

On This Page

Introduction

This article describes a hotfix that disables the function that lets users change the format of a Virtual Smart Card (VSC) personal identification number (PIN) by using the CTRL+ALT+DEL sequence. After you apply this hotfix, you can enable and disable this function.

By design, a VSC PIN must have a minimum of 8 digits and can contain any combination of numbers and characters. For example, Pin1234! and 12345678 are valid VSC PINs. Physical smart cards may not have this limitation.

For VSCs, you cannot use a mechanism that is built into Windows to apply a policy that enforces a specific PIN format (such as a 10 digit PIN that contains only numbers). However, for both VSCs and physical smart cards, you can enforce a PIN format by using other methods. For example, you can use a custom PIN tool to enforce the PIN format. To make sure that users do not change a specified PIN format, disable the function that lets users change the PIN format.

More information

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:
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 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:
  1. Start Registry Editor. To do this, press the Windows logo key+R, type regedit, and then click OK.
  2. Locate and then click the following registry key:
    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\
  3. On the Edit menu, point to New, and then click Key.
  4. Type SmartCardCredentialProvider, and then press Enter.
  5. On the Edit menu, point to New, and then click DWORD Value.
  6. 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.
  7. 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.
  8. On the Edit menu, point to New, and then click REG_SZ or REG_EXPAND_SZ Value.
  9. 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.
  10. 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.
  11. Exit Registry Editor.

You can set the VirtualSmartCardPinChangeAndUnlockString or SmartCardPinChangeAndUnblockString registry entry value to REG_SZorREG_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:
  1. Set the VirtualSmartCardPinChangeAndUnlockString or SmartCardPinChangeAndUnblockString registry entry value to REG_EXPAND_SZ, and then input the text that you want to display to users.
  2. Right-click the registry entry that you set in step 1, and then click Modify binary data....
  3. 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

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 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.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.1.760 1 . 22xxxWindows 7 and Windows Server 2008 R2SP1LDR
  • 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Smartcardcredentialprovider.dll6.1.7601.22298152,57613-Apr-201304:59x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Smartcardcredentialprovider.dll6.1.7601.22298190,97613-Apr-201305:24x64
Smartcardcredentialprovider.dll6.1.7601.22298152,57613-Apr-201304:59x86
For all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Smartcardcredentialprovider.dll6.1.7601.22298344,06413-Apr-201304:38IA-64
Smartcardcredentialprovider.dll6.1.7601.22298152,57613-Apr-201304:59x86
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 tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Smartcardcredentialprovider.dll6.2.9200.20685687,10411-Apr-201322:35x86
For all supported x64-based versions of Windows 8 and of Windows Server 2012
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Smartcardcredentialprovider.dll6.2.9200.20682876,03211-Apr-201323:17x64
Smartcardcredentialprovider.dll6.2.9200.20685687,10411-Apr-201322:35x86
Collapse this imageExpand this image
assets folding start collapsed
Collapse this imageExpand this image
assets folding end collapsed
Collapse this imageExpand this image
assets folding end collapsed

Status

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

More information

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 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File nameUpdate.mum
File versionNot Applicable
File size1,632
Date (UTC)17-Apr-2013
Time (UTC)06:46
PlatformNot Applicable
File nameX86_32bae813db9f91477d8c27cf15c1a74a_31bf3856ad364e35_6.1.7601.22298_none_594fc346c199fe81.manifest
File versionNot Applicable
File size730
Date (UTC)17-Apr-2013
Time (UTC)06:46
PlatformNot Applicable
File nameX86_microsoft-windows-a..dcredentialprovider_31bf3856ad364e35_6.1.7601.22298_none_44490ed83a2a7420.manifest
File versionNot Applicable
File size4,938
Date (UTC)13-Apr-2013
Time (UTC)05:30
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_32bae813db9f91477d8c27cf15c1a74a_31bf3856ad364e35_6.1.7601.22298_none_b56e5eca79f76fb7.manifest
File versionNot Applicable
File size732
Date (UTC)17-Apr-2013
Time (UTC)06:46
PlatformNot Applicable
File nameAmd64_9c17c616582678810ef0379c9cc85dcb_31bf3856ad364e35_6.1.7601.22298_none_93f7773c6d41b058.manifest
File versionNot Applicable
File size1,108
Date (UTC)17-Apr-2013
Time (UTC)06:46
PlatformNot Applicable
File nameAmd64_b8a2b28da6be6f74dc654300a9305eaf_31bf3856ad364e35_6.1.7601.22298_none_56c4d458e692d2c2.manifest
File versionNot Applicable
File size734
Date (UTC)17-Apr-2013
Time (UTC)06:46
PlatformNot Applicable
File nameAmd64_microsoft-windows-a..dcredentialprovider_31bf3856ad364e35_6.1.7601.22298_none_a067aa5bf287e556.manifest
File versionNot Applicable
File size4,942
Date (UTC)13-Apr-2013
Time (UTC)05:51
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,264
Date (UTC)17-Apr-2013
Time (UTC)06:46
PlatformNot Applicable
File nameX86_microsoft-windows-a..dcredentialprovider_31bf3856ad364e35_6.1.7601.22298_none_44490ed83a2a7420.manifest
File versionNot Applicable
File size4,938
Date (UTC)13-Apr-2013
Time (UTC)05:30
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameIa64_97f8d90090faacbab2c636d8fff65a89_31bf3856ad364e35_6.1.7601.22298_none_e3bb58264016d7ea.manifest
File versionNot Applicable
File size1,106
Date (UTC)17-Apr-2013
Time (UTC)06:46
PlatformNot Applicable
File nameIa64_microsoft-windows-a..dcredentialprovider_31bf3856ad364e35_6.1.7601.22298_none_444ab2ce3a287d1c.manifest
File versionNot Applicable
File size4,940
Date (UTC)13-Apr-2013
Time (UTC)05:15
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size1,447
Date (UTC)17-Apr-2013
Time (UTC)06:46
PlatformNot Applicable
File nameX86_microsoft-windows-a..dcredentialprovider_31bf3856ad364e35_6.1.7601.22298_none_44490ed83a2a7420.manifest
File versionNot Applicable
File size4,938
Date (UTC)13-Apr-2013
Time (UTC)05:30
PlatformNot Applicable

Additional file information for Windows 8 and Windows Server 2012

Additional files for all supported x86-based versions of Windows 8
Collapse this tableExpand this table
File nameUpdate.mum
File versionNot Applicable
File size1,793
Date (UTC)12-Apr-2013
Time (UTC)16:16
PlatformNot Applicable
File nameX86_d177b7a5feeb786a0b2f8806289a72d9_31bf3856ad364e35_6.2.9200.20686_none_776c54475aefb520.manifest
File versionNot Applicable
File size730
Date (UTC)12-Apr-2013
Time (UTC)16:16
PlatformNot Applicable
File nameX86_microsoft-windows-a..dcredentialprovider_31bf3856ad364e35_6.2.9200.20686_none_3f4151c5ad0fe2e9.manifest
File versionNot Applicable
File size7,691
Date (UTC)11-Apr-2013
Time (UTC)23:13
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
Collapse this tableExpand this table
File nameAmd64_58dc61e7b17e6b739ba360289cd43776_31bf3856ad364e35_6.2.9200.20686_none_c3271ba4699275f4.manifest
File versionNot Applicable
File size734
Date (UTC)12-Apr-2013
Time (UTC)16:17
PlatformNot Applicable
File nameAmd64_800f9ce21b81e53195b5d35c24a248a7_31bf3856ad364e35_6.2.9200.20686_none_cd01ac834c003e92.manifest
File versionNot Applicable
File size1,108
Date (UTC)12-Apr-2013
Time (UTC)16:17
PlatformNot Applicable
File nameAmd64_d177b7a5feeb786a0b2f8806289a72d9_31bf3856ad364e35_6.2.9200.20686_none_d38aefcb134d2656.manifest
File versionNot Applicable
File size732
Date (UTC)12-Apr-2013
Time (UTC)16:17
PlatformNot Applicable
File nameAmd64_microsoft-windows-a..dcredentialprovider_31bf3856ad364e35_6.2.9200.20686_none_9b5fed49656d541f.manifest
File versionNot Applicable
File size7,695
Date (UTC)12-Apr-2013
Time (UTC)01:20
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,461
Date (UTC)12-Apr-2013
Time (UTC)16:17
PlatformNot Applicable
File nameX86_microsoft-windows-a..dcredentialprovider_31bf3856ad364e35_6.2.9200.20686_none_3f4151c5ad0fe2e9.manifest
File versionNot Applicable
File size7,691
Date (UTC)11-Apr-2013
Time (UTC)23:13
PlatformNot Applicable
Collapse this imageExpand this image
assets folding end collapsed

Properties

Article ID: 2808693 - Last Review: February 12, 2014 - Revision: 9.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
  • Windows 7 Enterprise
  • Windows 7 Home Basic
  • Windows 7 Home Premium
  • Windows 7 Professional
  • Windows 7 Ultimate
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 for Itanium-Based Systems
  • Windows Server 2008 R2 Standard
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseadvanced KB2808693

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