Why CDC Serial Device installation fails on Windows Vista and 7 Because of Microchips INF file bug, you may succeed or fail on installation of CDC device driver to. SYSWindowsSYS. SYS. Get the latest Windows Hardware Development Kit Windows HDK for Windows 10 and start developing Universal Windows drivers, and testing and deploying Windows 10. For certain Universal Serial Bus USB devices, such as devices that are accessed by only a single application, you can install WinUSB Winusb. Win. USB Winusb. Installation Windows DriversFor certain Universal Serial Bus USB devices, such as devices that are accessed by only a single application, you can install Win. USB Winusb. sys in the devices kernel mode stack as the USB devices function driver instead of implementing a driver. This topic contains these sections Automatic installation of Win. USB without an INF file. As an OEM or independent hardware vendor IHV, you can build your device so that the Winusb. Windows 8 and later versions of the operating system. Such a device is called a Win. USB device and does not require you to write a custom INF file that references in box Winusb. When you connect a Win. Winusb Sys Windows Xp' title='Winusb Sys Windows Xp' />USB device, the system reads device information and loads Winusb. For more information, see Win. USB Device. Installing Win. USB by specifying the system provided device class. When you connect your device, you might notice that Windows loads Winusb. IHV has defined the device as a Win. USB Device. Otherwise follow these instructions to load the driver Plug in your device to the host system. Open Device Manager and locate the device. Right click the device and select Update driver software. In the wizard, select Browse my computer for driver software. Select Let me pick from a list of device drivers on my computer. From the list of device classes, select Universal Serial Bus devices. The wizard displays Win. Usb Device. Select it to load the driver. If Universal Serial Bus devices does not appear in the list of device classes, then you need to install the driver by using a custom INF. The preceding procedure does not add a device interface GUID for an app Windows Store app or Windows desktop app to access the device. You must add the GUID manually by following this procedure. Load the driver as described in the preceding procedure. The Windows System Assessment Tool WinSAT is a module of Microsoft Windows Vista, Windows 7, Windows 8 and Windows 10 that is available in the Control Panel under. Generate a device interface GUID for your device, by using a tool such as guidgen. Find the registry key for the device under this key HKEYLOCALMACHINESYSTEMCurrent. Control. SetEnumUSBlt VIDvvvv PIDpppp Under the Device Parameters key, add a String registry entry named Device. Interface. GUID or a Multi String entry named Device. Interface. GUIDs. Set the value to the GUID you generated in step 2. Disconnect the device from the system and reconnect it to the same physical port. Note  If you change the physical port then you must repeat steps 1 through 4. Writing a custom INF for Win. USB installation As part of the driver package, you provide an. Winusb. sys as the function driver for the USB device. The following example. Win. USB installation for most USB devices with some modifications, such as changing USBInstall in section names to an appropriate DDInstall value. You should also change the version, manufacturer, and model sections as necessary. For example, provide an appropriate manufactures name, the name of your signed catalog file, the correct device class, and the vendor identifier VID and product identifier PID for the device. Also notice that the setup class is set to USBDevice. Vendors can use the USBDevice setup class for devices that do not belong to another class and are not USB host controllers or hubs. If you are installing Win. USB as the function driver for one of the functions in a USB composite device, you must provide the hardware ID that is associated with the function, in the INF. You can obtain the hardware ID for the function from the properties of the devnode in Device Manager. The hardware ID string format is USBVIDvvvv PIDpppp. The following INF installs Win. USB as the OSR USB FX2 boards function driver on a x. Installs Win. Usb. Signature Windows NT. Class USBDevice. Class. GUID 8. BAE0. 32 5. A8. 1 4. BC3. D A4. FF1. 38. D6. Provider Manufacturer. Name. Catalog. File Win. Winusb Sys Windows Xp' title='Winusb Sys Windows Xp' />USBInstallation. Driver. Ver0. 90. ManufacturerModels sections. Manufacturer. Name Standard,NTamd. Standard. NTamd. 64. Device. Name USBInstall, USBVID0. PID1. 00. 2. Class definition. Class. Install. 32. Add. Reg Class. InstallAdd. Reg. Class. InstallAdd. Reg. HKR,Class. Name. HKR,No. Install. Class,1. HKR,Icon. Path,REGMULTISZ,systemrootsystem. HKR,Lower. Logo. Version,5. Installation. Include winusb. Needs WINUSB. NT. USBInstall. Services. Include winusb. inf. Needs WINUSB. NT. Services. USBInstall. HW. Add. RegDevAdd. Reg. HKR,Device. Interface. GUIDs,0x. Destination. Dirs. If your INF needs to copy files, you must not use the Default. Dest. Dir directive here. You must explicitly reference all file list section names in this section. Strings. Manufacturer. Name. Class. NameUniversal Serial Bus devices. Device. NameFx. Learning Kit Device. REGMULTISZ 0x. Except for device specific values and several issues that are noted in the following list, you can use these sections and directives to install Win. Sound Blaster X-Fi Surround 5.1 Pro Asio Drivers here. USB for any USB device. These list items describe the Includes and Directives in the preceding. USBInstall The Include and Needs directives in the USBInstall section are required for installing Win. USB. You should not modify these directives. USBInstall. Services The Include directive in the USBInstall. Services section includes the system supplied. Win. USB Win. USB. This. inf file is installed by the Win. USB co installer if it isnt already on the target system. The Needs directive specifies the section within Win. USB. inf that contains information required to install Winusb. You should not modify these directives. Note  Because Windows XP doesnt provide Win. USB. inf, the file must either be copied to Windows XP systems by the co installer, or you should provide a separate decorated section for Windows XP. USBInstall. HW This section is the key in the. It specifies the device interface globally unique identifier GUID for your device. The Add. Reg directive sets the specified interface GUID in a standard registry value. When Winusb. sys is loaded as the devices function driver, it reads the registry value Device. Interface. GUIDs key and uses the specified GUID to represent the device interface. You should replace the GUID in this example with one that you create specifically for your device. If the protocols for the device change, create a new device interface GUID. Note  User mode software must call Setup. Di. Get. Class. Devs to enumerate the registered device interfaces that are associated with one of the device interface classes specified under the Device. Interface. GUIDs key. Setup. Di. Get. Class. Devs returns the device handle for the device that the user mode software must then pass to the Win. UsbInitialize routine to obtain a Win. USB handle for the device interface. For more info about these routines, see How to Access a USB Device by Using Win. USB Functions. The following INF installs Win. USB as the OSR USB FX2 boards function driver on a x. The example shows INF with WDF coinstallers. Installs Win. Usb. Signature Windows NT. Class USBDevice. Class. GUID 8. BAE0. 32 5. A8. 1 4. BC3. D A4. FF1. 38. D6. Provider Manufacturer. Name. Catalog. File Win. USBInstallation. cat. Driver. Ver0. 90. ManufacturerModels sections. Manufacturer. Name Standard,NTamd. Standard. NTamd. 64. Device. Name USBInstall, USBVID0. PID1. 00. 2. Class definition. Class. Install. 32. Add. Reg Class. InstallAdd. Reg. Class. InstallAdd.