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. Smartcard application cannot read information from some smartcards on a computer that is running Windows 7 or Windows Server 2008 R2

Smartcard application cannot read information from some smartcards on a computer that is running Windows 7 or Windows Server 2008 R2

View products that this article applies to.

Symptoms

On a computer that is running Windows Vista or Windows Server 2008, you use an application together with a smartcard reader to read information from smartcards. However, the application cannot retrieve information from the smartcards. When this issue occurs, the application does not work correctly. Additionally, the application may stop responding. For example, you may encounter this issue when you use ActivClient.

↑ Back to the top

Cause

This issue occurs because the smartcards return more information to the application than the application expects to receive. Typically, a smartcard application calls the SCardTransmit function to send a service request to a smartcard and expects to receive data back from the smartcard. As defined in Application Protocol Data Unit (APDU) protocol, a Le field is set to indicate the maximum number of data bytes for the response that is returned from the smartcard. However, some smartcards ignore the Le field and return more data than the application expects. In this situation, the Usbccid.sys driver returns a STATUS_DEVICE_PROTOCOL_ERROR error. This causes the smartcard application to stop retrieving information from the smartcards.

↑ 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 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 Web site:
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 Windows 7 or Windows Server 2008 R2.

Restart requirement

You may 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 English (United States) 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 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 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 nameFile versionFile sizeDateTimePlatform
Wudfusbcciddriver.dll6.1.7600.2070896,76806-May-201012:48x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Wudfusbcciddriver.dll6.1.7600.20708116,22406-May-201011:48x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Wudfusbcciddriver.dll6.1.7600.20708242,68806-May-201008:59IA-64

↑ 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 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,441
Date (UTC)06-May-2010
Time (UTC)17:48
PlatformNot applicable
File nameX86_wudfusbcciddriver.inf_31bf3856ad364e35_6.1.7600.20708_none_633328877be25b4f.manifest
File versionNot applicable
File size2,147
Date (UTC)06-May-2010
Time (UTC)13:24
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_wudfusbcciddriver.inf_31bf3856ad364e35_6.1.7600.20708_none_bf51c40b343fcc85.manifest
File versionNot applicable
File size2,151
Date (UTC)06-May-2010
Time (UTC)15:20
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,861
Date (UTC)06-May-2010
Time (UTC)17:48
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_wudfusbcciddriver.inf_31bf3856ad364e35_6.1.7600.20708_none_6334cc7d7be0644b.manifest
File versionNot applicable
File size2,149
Date (UTC)06-May-2010
Time (UTC)14:17
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,445
Date (UTC)06-May-2010
Time (UTC)17:48
PlatformNot applicable

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 981844
Revision : 2
Created on : 9/18/2018
Published on : 9/18/2018
Exists online : False
Views : 270