2020. 2. 23. 12:04ㆍ카테고리 없음
MS-official 'WinUSB class' driver for XP, Vista and 7 ajs410: What's really nice with Windows 8 is that you can supply a Microsoft descriptor that allows the system to automatically bind your vendor-defined interface to WinUSB without any INF file at all. It will be plug-and-play exactly like HID - but only on Windows 8 or higher. The MS-official 'WinUSB class' driver extends this method back to XP, Vista and 7 (x86/x64). As I noticed that this information is not popular even for USB experts like ajs410 yet, I post a brief summary, here. Distribution The driver file is distributed as 'Windows Phone driver' The detailed download instruction of this driver is described in this KB, 'Windows Phone 8 is not detected by your computer' - Things to Try -3. Update your Windows Phone 8 driver -To manually download and install the Windows Phone driver: -a. Go to -b.
Search for 'windows phone winusb' The direct link is (works just on IE), This CAB file is downloaded from above link, AMD64X86-en-204842205f2718fc6d44c5ae61d4275d679bbf1ededf58e5.cab Extract winusbcompat.inf/.cat files from this CAB file. For your convenience, I attached winusbcompat.zip to this post.
Installation At plugin of a 'WinUSB Device' (.1) to a PC (.2), specify the folder which contains winusbcompat.inf/.cat as its driver. Once the winusbcompat.inf/.cat would be installed on the PC, another 'WinUSB Devices' should be automatically recognized without any driver installation. (.1) A device which returns MS OS descriptors for WinUSB, like Microchip 'Device - WinUSB - Generic Driver Demo' example (.2) Windows XP-SP3, Vista-SP2 (x86/x64), 7-SP1 (x86/x64) Tsuneo. That is pretty awesome, thanks for the links.
Windows Xp Usb Driver Download
One thing I would note about this approach. Windows 8 is supported by what is called an 'in-box driver' - that is, you can install a fresh copy of Windows 8 on a PC with no Internet connection, plug in a WCID Device, and WinUSB will be installed correctly and automatically for your device. For Windows Vista and Windows 7, the driver is not in-box; you can think of it as an 'out-box driver', since it requires contact with Windows Update, but the OS will still automatically install the driver without you having to sign one. This is not a problem if your customers have guaranteed Internet access on the machine in question, but if you must handle the use case of an air-gapped machine, your software installation will still need a driver package. What is really new to me, here, is that you can install this winusbcompat driver package once, and then every WCID device after that gets the benefit. That is awesome, especially since it works back to XP (even though XP officially dies tomorrow). Even better than that, you don't need an Authenticode signature to install your driver package if you use winusbcompat!
And it can be included in your installer in the event that you target air-gapped systems. Salazar: However, it doesn't look like this.inf file provides any device interface GUIDs. Without that, it seems impossible to open the device and use it with WinUSB functions? The fact you aren’t aware of is, the target 'WinUSB class' (or 'WCID') device provides every information in INF file over MS OS descriptors, including interface GUID. And then, any specific INF file is not required any more for the target device. Since WinXP SP2, MS have integrated the protocol to detect 'WinUSB class' device, by asking MS OS descriptors to every USB device at the first plugin enumeration. When the target device correctly responds to this protocol, Windows assigns MSCOMPWINUSB to the device interface.
But it doesn’t go any further, unless MSCOMPWINUSB class driver is installed. Above class driver binds MSCOMPWINUSB device to WinUSB driver. That is, it is the missing link;-) You may refer to these topics.
Free Windows Xp Usb Download
How to install WinUSB.sys without a custom INF? Building USB devices for Windows Microsoft OS Descriptors Is there another way to open a WinUSB device without using SetupDiEnumDeviceInterfaces? The procedure around SetupDiEnumDeviceInterfaces is stereotype. Once you’ve written (or copied) it, you may reuse it without touching its contents.
Of course, you may apply 'WinUSB libraries' on the web, to hide SetupDiEnumDeviceInterfaces call. A couple follow-up questions: 1. Under Windows XP, it does not seem possible to use this winusbcompat.inf file.
The reason is that WinXP needs a coinstaller to get winusb.sys and winusb.dll, since those binaries did not ship with WinXP. But this winusbcompat.inf file does not mention a coinstaller. Does winusbcompat.inf actually work on WinXP? Or do you need a custom.inf anyways?
On my development computer (Windows 7 64-bit) I do not get a DeviceInterfaceGUID. I have tried numerous times uninstalling the device, deleting it from the registry, etc. Every time it reinstalls but does not give me a DeviceInterfaceGUID with which to open the device. I have not seen this problem on any other computer I have tested on. Is it possible that during development (adding the MS OS descriptors), that it corrupted something in the registry that I am not aware of, that is causing it not to list the DeviceInterfaceGUID? A) Name of WinUsb Device The device 'name' on the Device Manager depends on the OS version (.1).
A) Windows 8/8.1 The device name comes from the device - the iProduct string descriptor b) Windows XP, Vista, 7 The name is always 'WinUsb Device', which comes from winusb.inf (.1) WinUSB Device - on MSDN site Described in 'How to change the device description for a WinUSB device' section These names are stored on this registry entry for each device HKEYLOCALMACHINE SYSTEM CurrentControlSet Enum USB VIDvvvv&PIDpppp DeviceDesc At the first plug-in installation, this registry entry is made by the OS. As this registry entry is protected, we can’t change the value of this entry. That is, to change this entry from the default, a custom INF file is required, as described in above MSDN document. But when 'FriendlyName' entry is placed under the same key, Device Manager shows this 'name' primarily instead of 'DeviceDesc'. FriendlyName entry is assigned manually, or by PC application (using SetupDiSetDeviceRegistryProperty(SPDRPFRIENDLYNAME) under administrator privilege), as discussed on this topic.
B) XP installation If the target WinXP PC wouldn’t have been installed WinUSB before, 'WinUSB Device' plug-in installation using winusbcompat.inf should fail. It’s because winusbcompat.inf refers to winusb.inf. WinUSB is able to be pre-installed together with winusbcompat.inf. If you would like to customize the 'name' of the device, however, ordinary INF-file installation of WinUSB is better. There is one more issue that eludes me: On my development computer (Windows 7 64-bit) I do not get a DeviceInterfaceGUID.
I have tried numerous times uninstalling the device, deleting it from the registry, etc. Every time it reinstalls but does not give me a DeviceInterfaceGUID with which to open the device. I have not seen this problem on any other computer I have tested on.
Download Driver For Windows Xp
Is it possible that during development (adding the MS OS descriptors), that it corrupted something in the registry that I am not aware of, that is causing it not to list the DeviceInterfaceGUID? This computer is running Windows 7 64-bit SP1 (Build 7601). I have tried changing the USB product id to something new, but that also does not seem to solve the problem for me.
No matter what I do, the inbox WinUSB drivers plus this winusbcompat.inf file do not register the DeviceInterfaceGUID on this one specific computer. Are there any WinUSB registry settings I could check? Any ideas what is happening here?