Microsoft Class Drivers for USB CCID Smart Cards. This article addresses issues related to the development of the Microsoft CCID class driver for Windows, including a list of the features in the USB CCID ChipSmart Card Interface Devices specification that the driver will support. This article provides USB smart card class driver Usbccid. USB ChipSmart Card Interface Devices CCID Specification revision 1. Usbccid. sys is compliant with all supported versions of Microsoft Windows operating systems, and is available on Windows Update. For additional details on the class driver architecture as well as the guidelines associated with USB CCID device development and testing requirements, read this article and see Smart Card Technology. Introduction. The USB CCID class driver reduces the need for hardware vendors to create a device specific driver for smart card readers. Eliminating the need for a device specific driver will potentially reduce the driver development cost, improve driver and system stability, reduce time to market, and lead to a simplified plug and play experience for customers using devices compliant with the USB ChipSmart Card Interface Devices CCID Specification revision 1. The USB CCID class driver is compatible with all SKUs and locales that are associated with Windows. The USB CCID class driver is currently available on Windows Update and also through the Windows Update Catalog. This article provides details on Windows support for USB CCID devices. The USB CCID Architecture section later in this article describes the structure of the USB CCID stack. The USB CCID Class Driver Details section later in this article describes the features that are explicitly supported by this release of the USB CCID driver. The features planned for future releases are also discussed in the USB CCID Class Driver Details section. The last section provides references to related information and action items to enhance your USB CCID device experience. USB CCID Architecture. Figure 1 illustrates the functionality of the USB CCID class driver and the associated smart card subsystem. The USB CCID class driver Usbccid. Windows development cycle, to support USB CCID compliant devices. The balance of the class driver infrastructure is already in box in Windows. Figure 1 USB CCID Architecture Stack. To confirm that you have the latest USB CCID driver, the following components must be included in your system. Prior to Windows 7. INF this INF will be an OEN. Windows Update Driver. Ver 0. 40. 12. ID match USBClass0. B Sub. Class0. Driver file Usbccid. For Windows 7 and later INF Driver. Ver 0. 62. 12. ID match USBClass0. B Sub. Class0. Driver file WUDFUsbccid. Driver. dll File Version 6. Driver or INF version information that is newer later date or higher version number than the information listed above is acceptable. To ensure compatibility with the USB CCID class driver, the Windows USB Team encourages all CCID compliant devices to be qualified by the latest compatibility tests found on the WHDC Web site. Windows 10 does not except my Polar Infrared USB Interface driver Any suggestions Motherboard ASUS Sabertooth 990FX R2. BIOS version 2104 x64 Processor AMD FX. USB CCID Class Driver Details. The Microsoft CCID class driver is compatible with the USB ChipSmart Card Interface Devices CCID Specification revision 1. CCID class devices or interface on a composite device. Neither the mechanics of the smart card interface or the content of the data are described in the CCID specification. DSonubqpnOQgxRTtsmiTgL3yFwE=/http%3A%2F%2Fi.imgur.com%2FSMOfC9H.png' alt='Usb Driver For Windows 10' title='Usb Driver For Windows 10' />The most downloaded USB Drivers, including USB Driver Update Utility, JMicron JMB38X MS Host Controller and Linux File Stor Gadget USB Device. However, the CCID specification does provide detailed information with respect to the USB related configuration and communication channels. Microsoft Deployment Toolkit Lite Touch Lighting. The current release of the Microsoft CCID class driver implements a majority of the features defined in the USB CCID specification. The Microsoft CCID class driver will support the following items that are based on the USB CCID Class specification. V, 3. 0. V, and 1. V cards. Both T0 and T1 protocols. Variable clock frequencies and data rates. All features in the dw. Features field, including Character, TPDU, APDU, and extended APDU levels, although TPDU is the preferred exchange level. In order to send or receive an Escape command to a reader, the DWORD registry value Escape. Command. Enable must be added and set to a non zero value under one of the following keys. HKLMSYSTEMCCSEnumUSBVididDevice Parameters prior to Windows 7. HKLMSYSTEMCCSEnumUSBVididDevice ParametersWUDFUsbccid. Driver Windows 7 and later. Then the vendor IOCTL for the Escape command is defined as follows define IOCTLCCIDESCAPE SCARDCTLCODE3. With the enabled Escape command, security against malicious escape commands becomes the readers responsibility. USB CCID readers should implement the GETCLOCKFREQUENCIES and GETDATARATES properties, even if bit 2. Features is set. The values of the b. Num. Data. Rates. Supported and b. Num. Clock. Supported functions should also be non zero accordingly. This is due to a problem with the USB CCID Class specification where the driver is supposed to send a PPS request however, if bit 2. PPS request are zero, the driver does not know what values to set in the PPS request. If b. Num. Data. Rates. Supported andor b. Num. Clock. Supported are set to zero, the driver will make a guess as to what baud rates the reader supports, which may or may not be correct. The following features are not currently supported in this initial release of the Microsoft CCID class driver. These features may be supported in future releases of the driver on future operating systems, and will be prioritized based on customer demand. Keypad or LCD display support. If these features need to be provided on a smart card, a different interface generally HID must be defined. Vendordevice specific string name support in the device manager. Since the INF to load USBCCID is not included with Windows, the INF will be renamed as OEM INF. Vendors can not refer to this INF through IncludeNeeds. This feature may be supported in future Windows operating systems. Support for multiple slots on readers. If the reader has multiple slots, only slot 0 will be used. Devices that wish to expose multiple readers may develop a composite device a CCID compliant interface would then be required for each reader. Driver support for system wake from suspendhibernate state on card insertion even if the reader sets the remote wake bit. This feature may be made available as more smart card readers provide remote wake functionality. Selective suspend support. The Windows team did not have selective suspend capable hardware at the time of driver RTM to test this feature. This feature will be supported depending on the availability of readers that support selective suspend and errata that are appended to the USB CCID specification to support selective suspend. Support for issuing multiple commands to a reader that implements queuing capabilities. Support for any of the mechanical driver features. Future support plans will be determined when the driver features are standardized. For more information, see section 4. USB ChipSmart Card Interface Devices CCID Specification. Windows Logo Program. Future requirements for the Designed for Windows logo program, which pertain to USB CCID class devices, may include the following USB smart card CCID reader complies with USB Device Class Specification for USB ChipSmart Card Interface Devices.