libwdi Windows 10 on ARM64 support

I am well aware this is probably pushing it, but I have an ARM64 based Windows 10 Pro machine sitting in front of me currently and am attempting to get it working with an RTL-SDR.

Zadig runs fine and doesn't seem to have any issues, unfortunately though when I select the usual "Bulk-In, Interface (Interface 0)" and hit Install Driver for "WinUSB", I get a "The driver installation failed" error. I have attached the log.

I have no idea if the drivers etc will work on this machine, will admit I am no major expert in Windows 10 Pro on ARM64 (simply a machine that has been handed to me for this project), but am intrigued if it would be possible to make it work. Finally, the machine itself is an HP Envy x2.

Zadig 2.3.701
Windows 10 32 bit (Build 17134)
ini file 'zadig.ini' not found - default parameters will be used
default driver set to 'WinUSB'
2 devices found.
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0BDA&PID_2838&REV_0100&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_ff&SubClass_ff&Prot_ff
libwdi:debug [wdi_create_list] Driverless USB device (0): USB\VID_0BDA&PID_2838&MI_00\6&38A180A5&0&0000
libwdi:debug [wdi_create_list] Device description: 'Bulk-In, Interface (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0BDA&PID_2838&REV_0100&MI_01
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_ff&SubClass_ff&Prot_ff
libwdi:debug [wdi_create_list] Driverless USB device (2): USB\VID_0BDA&PID_2838&MI_01\6&38A180A5&0&0001
libwdi:debug [wdi_create_list] Device description: 'Bulk-In, Interface (Interface 1)'
Checking for Zadig updates...

Checking release channel...

Using inf name: Bulk-In_Interface_(Interface_0).inf
Successfully extracted driver files.
Installing driver. Please wait...
Updates: Unable to acces version data

libwdi:info [extract_binaries] successfully extracted driver files to C:\Users\HAB\usb_driver
libwdi:info [wdi_prepare_driver] successfully created 'C:\Users\HAB\usb_driver\Bulk-In_Interface_(Interface_0).inf'
libwdi:info [wdi_prepare_driver] Creating and self-signing a .cat file...
libwdi:debug [AddFileHash] 'wdfcoinstaller01011.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\HAB\usb_driver\amd64\wdfcoinstaller01011.dll'
libwdi:debug [AddFileHash] 'winusbcoinstaller2.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\HAB\usb_driver\amd64\winusbcoinstaller2.dll'
libwdi:debug [AddFileHash] 'bulk-in_interface_(interface_0).inf': INF type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\HAB\usb_driver\bulk-in_interface_(interface_0).inf'
libwdi:debug [AddFileHash] 'wdfcoinstaller01011.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\HAB\usb_driver\x86\wdfcoinstaller01011.dll'
libwdi:debug [AddFileHash] 'winusbcoinstaller2.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\HAB\usb_driver\x86\winusbcoinstaller2.dll'
libwdi:info [CreateCat] successfully created file 'C:\Users\HAB\usb_driver\Bulk-In_Interface_(Interface_0).cat'
libwdi:info [RemoveCertFromStore] deleted existing certificate 'CN=USB\VID_0BDA&PID_2838&MI_00 (libwdi autogenerated)' from 'Root' store
libwdi:info [RemoveCertFromStore] deleted existing certificate 'CN=USB\VID_0BDA&PID_2838&MI_00 (libwdi autogenerated)' from 'TrustedPublisher' store
libwdi:debug [CreateSelfSignedCert] set Enhanced Key Usage, URL and CPS
libwdi:debug [CreateSelfSignedCert] created new key container
libwdi:debug [CreateSelfSignedCert] generated new keypair
libwdi:info [CreateSelfSignedCert] created new self-signed certificate 'CN=USB\VID_0BDA&PID_2838&MI_00 (libwdi autogenerated)'
libwdi:debug [SelfSignFile] successfully created certificate 'CN=USB\VID_0BDA&PID_2838&MI_00 (libwdi autogenerated)'
libwdi:info [SelfSignFile] added certificate 'CN=USB\VID_0BDA&PID_2838&MI_00 (libwdi autogenerated)' to 'Root' and 'TrustedPublisher' stores
libwdi:info [SelfSignFile] successfully signed file 'C:\Users\HAB\usb_driver\Bulk-In_Interface_(Interface_0).cat'
libwdi:info [SelfSignFile] successfully deleted private key
libwdi:debug [wdi_install_driver] using progress bar mode
libwdi:debug [installer process] got parameter Bulk-In_Interface_(Interface_0).inf
libwdi:debug [process_message] got request for device_id
libwdi:debug [installer process] got device_id: 'USB\VID_0BDA&PID_2838&MI_00\6&38A180A5&0&0000'
libwdi:debug [process_message] got request for hardware_id
libwdi:debug [installer process] got hardware_id: 'USB\VID_0BDA&PID_2838&REV_0100&MI_00'
libwdi:debug [installer process] got user_sid: 'S-1-5-21-4036245373-3405510498-1736261573-1003'
libwdi:debug [installer process] using syslog 'C:\WINDOWS\inf\setupapi.dev.log'
libwdi:debug [installer process] syslog reader thread started
libwdi:debug [installer process] successfully disabled the system restore point creation setting
libwdi:debug [process_message] switching timeout to infinite
libwdi:debug [installer process] Installing driver for USB\VID_0BDA&PID_2838&REV_0100&MI_00 - please wait...
libwdi:debug [process_message] switching timeout back to finite
libwdi:debug [installer process] attempted to use a 32 bit installer on a 64 bit machine
libwdi:debug [process_message] installer process completed
Driver Installation: FAILED (Attempted to use a 32 bit installer on a 64 bit machine)
2 devices found.
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0BDA&PID_2838&REV_0100&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_ff&SubClass_ff&Prot_ff
libwdi:debug [wdi_create_list] Driverless USB device (0): USB\VID_0BDA&PID_2838&MI_00\6&38A180A5&0&0000
libwdi:debug [wdi_create_list] Device description: 'Bulk-In, Interface (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0BDA&PID_2838&REV_0100&MI_01
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_ff&SubClass_ff&Prot_ff
libwdi:debug [wdi_create_list] Driverless USB device (2): USB\VID_0BDA&PID_2838&MI_01\6&38A180A5&0&0001
libwdi:debug [wdi_create_list] Device description: 'Bulk-In, Interface (Interface 1)'

Mar 24 '19 23:03 gbaman

Zadig runs fine

Wait, are you running the x86 version of Zadig that is published at https://zadig.akeo.ie? That will not work, first of all because it will run on ARM64 in x86 emulation mode (which I doubt Microsoft allows installing ARM64 drivers from) and second, because there are no ARM64 embedded in Zadig in the first place, so even if it "worked", it wouldn't be able to find the files it requires for ARM64.

Also:

Windows 10 32 bit (Build 17134)
(...)
Driver Installation: FAILED (Attempted to use a 32 bit installer on a 64 bit machine)

Zadig detects a 32-bit x86 emulation (likely because that's what Microsoft used by default) and therefore tries to run the 32-bit installer, which of course the system doesn't like.

For Zadig to work on ARM64, I'd have to recompile an ARM64 version and edit the embedded files to include ARM64 files.

I may do that eventually, but I'm afraid I'm too busy with other stuff to look into that in the short term (short term meaning 0-6 months).

Now, if somebody else wants to take a stab at it and send a patch I can review, that's a different story...

Mar 24 '19 23:03 pbatard

Haha yeah, I was installing a batch of random laptops with SDR# for use in a school next week (for use with High Altitude Ballooning STEM project) and hadn't even crossed my mind that this one was different till I hit the error (guess is what I get for doing it this time of the night), then started digging around.

What you are saying does make sense, it does only emulate x86 based apps and not x86_64 based apps full stop. If you have somewhere rough you could point me to on where to start, I don't mind taking a glance at recompiling it. No guarantees though... :)

Mar 24 '19 23:03 gbaman

If you have somewhere rough you could point me to on where to start

Oh boy...

Well, first you'll have to find if and where MS provides ARM64 versions of their CoInstaller DLLs.
Once you have that, you'll need to edit this mess to handle ARM64 (and while you're at it you may also want to add ARM).
You'll also want to edit this and this to add ARM64 support.
Then you'll need to edit the MS project files so lbwdi/Zadig can be compiled for ARM64 (and while you're at it you may also want to add ARM - btw this might help you.
There's also some more stuff that will be needed, such as updating the check for update in Zadig so that the ARM64 version doesn't try to download the x86 version, or reporting the arch on startup, but I've already done that in Rufus, so you don't really have to do it as I should be able to reuse that code.
Last but not least you will need to test, test and test again to make sure that your changes work on ARM64 machines! Adding the code is 20% of the work. Testing is 80%!

Mar 25 '19 11:03 pbatard

Thanks for writing this up - I am also trying to get Zadig running on Windows 10 on ARM64 to support a Lenovo Yoga C620 using an Adafruit USB-to-serial cable so I can talk to a Jetson Nano.

Thanks for the detailed situation report here, I'll hope to get some help to look at this.

Apr 28 '19 17:04 vielmetti

WOW64 programs - so x86 on x64 as well as on ARM64 - can't install drivers. The API exists but just returns an error.

The ARM64 SDK is supposed to be fully featured, so if you can't find the DLLs you need, let me know the SDK piece you'd expect them to be in and the path you expect the file to be at and I can talk to a friend.

libusb v1 recompiles for ARM64 by just retargeting the VS projects for Windows 10. (VS2019 has some simplifications for this.)

ARM64 should be pretty straightforward to add as a configuration under VS 2017 or VS 2019--I recommend 2019.

You may find IsWow64Process2 handy for probing architectures, but to run on Windows 7 you'll have to use GetProcAddress to see if it's available.

ARM32 support is likely not going to be useful unless you port to IoT Edition, but VS does make it easy.

I just got an RTL-SDR and would be happy to test things on my Windows 10 on ARM systems, especially if there's a decent way to make sure things are uninstalled. (Just the 'delete drivers, yes' workflow in Device Manager, I expect.)

(Hi @vielmetti ! If you to get some time to look at this, hit me up--I'd be happy to at least kibbitz. I think these machines have great potential for mobile maker scenarios.)

(Yes, I work for Microsoft. I even work on Windows 10 on ARM(64) and have ported OSS projects as part of my day job, but I am here as a hobbyist, user, and fan and not as an employee or representative of my employer.)

Oct 13 '19 21:10 jkunkee

Hi Jon,

First of all, whether in an official position or not, it's nice to know that there are some people from Microsoft looking at independent projects that relate to the installation of Windows drivers. And I'm actually glad you decided to chime in and offer to see if you can use your connections, because you may actually be able to help with the biggest roadblock I have at the moment (besides time to work on this feature) which is best illustrated by the picture below:

Namely: if you install the latest Windows 10 WDK, you still don't get any of the WDF and WinUSB coinstaller DLLs for arm64 (Still no arm64 directory). And what's more, even for ARM, there's no winusbcoinstaller2.dll provided, which means we can't support that platform either.

At the very least, libwdi requires the following 2 DLLs to be provided able to support an architecture:

WdfCoInstaller01011.dll
winusbcoinstaller2.dll

So, if possible, can you find out with your colleagues what the story is with regards to finally providing these files for ARM/ARM64 in the WDK, just like they are provided for x86 and x64?

With regards to your other points, I agree that VS2019 has made things easier for ARM64, and I'm planning to retarget libwdi for VS2019 when I get a chance (Since I'm already using VS2019 internally). My only issue here is that, whereas AppVeyor added the VS2019 target not that long ago (but still not in an official mode), they don't have MinGW support working on that target. So if I switch from VS2017 to VS2019, my MinGW libwdi builds will break, and I'd rather not have to go through what I had to do for Rufus, which is to use a mix of 2017 and 2019 (and still end up with a Coverity that doesn't work — C'mon AppVeyor, update your platforms already!!).

Apart from that, I agree that adding ARM64 support shouldn't be that difficult (as usual, it's going to be the ability to allocate time to complete that task that'll be a challenge). I'll keep in mind your recommendation to use IsWow64Process2(), as this seems more useful than IsWow64Process() indeed.

Oct 13 '19 22:10 pbatard

That's what my system shows too; I'll see what I can do.

Oct 14 '19 03:10 jkunkee

Ah, that would do it. I got a quick answer: the CoInstallers are not needed on Windows 10 on ARM because the first version to ship was 1709. You can drop the references to them for ARM64. (I'm afraid I'm currently rather behind on what the coinstallers do, so I'm probably not much more help there. :/

Oct 14 '19 18:10 jkunkee

Thanks for the info.

This is actually going to make things slightly more complex for ARM/ARM64, coz we'll need to conditionally sort out a [USB_Install.CoInstallers] section from the winusb.inf template... I'm hoping we can filter these things out with [USB_Install.CoInstallers.x86] and [USB_Install.CoInstallers.amd64] but this will require some testing. And of course I'll need to add conditional logic on whether to search for the coinstallers or not depending on the platform.

No idea when I'll have a chance to look into that, but most likely it won't be before a couple of months... I do appreciate the help however, as it solves one of the main question I had about how we might be able to proceed for ARM/ARM64.

Oct 14 '19 18:10 pbatard

This writeup from @jkunkee gives a good state-of-the-art report, if you find this issue you'll be interested in https://daskunkee.blogspot.com/2020/02/tech-esp32-programming-from-arm64.html

Feb 23 '20 03:02 vielmetti

Please pursue it we at Windows on Rasberry Pi community will be glad to extend support in testing your drivers and tools for ARM64. We have successfully booted WOA on Rasberry Pi 4 B+ and hence have Cheap ARM64 Windows On ARM device with sort of current hardware but way cheaper than a surface pro device.

Jun 06 '21 17:06 sidd-kishan

Yes, I am well aware of it. I am one of the many people who helped develop the UEFI firmware needed to run Windows on the Raspberry Pi and I also helped figure out a way to run Windows off the Pi 4 USB 3.0 ports while using more than 1 GB RAM. And the reason I was involved in this effort was precisely so that I could have access to a cheap platform to test ARM64 versions of Rufus or libwdi.

However, the downside of all this is that I find myself having to allocate time to maintain the Raspberry Pi firmware... which, outside of other prioritization matters (I'm afraid that libwdi will never be that high a priority for me) actually takes time away from tasks such as adding Windows 10 ARM64 support for libwdi...

Jun 06 '21 19:06 pbatard

One day, there will be a low-cost, supported options for developers--I get to work on one--but for now the Snapdragon Development Kit is slated to be released this summer. It won't be on a patch with the indomitable, inexpensive, and community-maintained Raspberry Pi, but Qualcomm will provide and maintain the BSP and is intended to be much less than $1000.

Jun 09 '21 19:06 jkunkee

I'd like to chime in here to say please pursue this. Getting a RTL up and running on a Pi 4 running Windows 10 ARM64 would be a real boost to a lot of people. I have two projects stalled just for lack of a driver I can install for RTL-SDR's. I'd be happy to help do any testing needed when it gets that far.

Or is there some other way to get an RTL driver loaded, maybe through pnputil?

Jul 02 '21 00:07 dougmsbbs

How many people really care about Windows on ARM? I am an ARM fan. My main computer is the Mac Mini M1 (based on ARM64). My main Linux machine is the Raspberry Pi 400 (along with some other ARM boards). But I do not really care for Windows on ARM. My work and home Windows laptops are running on Intel CPU (AMD CPU is also okay).

Ref: libusb does support ARM32/ARM64 on Windows with VS, but not MinGW. https://github.com/libusb/libusb/issues/921

Jul 06 '21 06:07 mcuee

Hi Xiaofan,

I think more people care about Windows on ARM than you give them credit for. Having worked on the effort to make Windows run on the Pi 4, I can tell you that there is genuine interest for an cheap yet powerful enough ARM64 platform that can run modern Windows, as buying into the intel/AMD framework can still be prohibitive for a lot of people for varied reasons.

And the thing is, Microsoft is perfectly placed to compete with Apple on ARM at a junction where apple will never ever go: cheap platforms.

In other words, if Microsoft embraced cheap ARM64 platforms like the Pi 4 (which we know can run Windows 10, or even 11, with "good enough" performance for every day tasks like web surfing, e-mail, document editing and so on), they would probably find a vast sway of users to follow them there, that aren't going to find their match with other options, and especially not Apple MX or Linux on ARM. And that's because the existing Windows ecosystem, with a market dominance that means that if you're looking for an application chances are that you're always going to find at least a Windows version of it, is way too attractive to pass when given the opportunity. Which eventually means that, for a lot of users with limited budget, the choice is between secondhand intel/AMD platforms that run Windows, but that come with the drawbacks of being secondhand, or modern ARM64 platforms that may actually turn out to cheaper than secondhand intel/AMD ones, and run Windows.

So, provided that Microsoft are able to read the writing on the wall (which, judging from what's happening with the Pi 4 Windows effort, they sadly don't appear to be able to do. But then again, it wouldn't be Microsoft if they were able to make decisions that actually benefit Windows users in the long run...), you should find that quite a lot of people will eventually care about Windows on ARM, and, even if Microsoft really does make the beginnings of that platform a lot less inviting that it has any rights to be (because, right now, one really has to wonder if Microsoft isn't effectively trying to kill Windows on ARM before it can gain any traction, on account of their complete disregard for all the aspects that effectively contributed to make Windows the dominant OS on x86, such as not getting into some kind of lock in with a specific vendor when it comes to platform development), I am considering that there is more than enough demand to warrant an ARM64 version of Zadig/libwdi.

Thus, I am still committed to produce such a version. But, for the foreseeable future, I still have quite a few things that take precedence over that (and the planned release of Windows 11 just added a new major one to that list) so, once again, it'll still have to be quite a few months away...

Jul 06 '21 10:07 pbatard

Thanks for the detailed explanation.

Yes it will be good if there are really cheap cheap yet powerful enough ARM64 platform that can run modern Windows. Apparently Raspberry Pi 4 is not yet powerful enough in that aspect. Qualcomm stuff is expensive. And they do not have enough native ARM apps (UWP is very much locked) so that they have to rely on x86/x64 emulation -- that will mean powerful ARM based solution from Qualcomm or similar -- not cheap stuff like Raspberry Pi. So I do not see that happen any time soon.

Windows on ARM is pretty much locked, I believe it will be more so in the future with Windows 11.

Personally I run Linux on Raspberry Pi 400 and it is really pretty smooth (forget Youtube 1080p for a moment). And you have enough apps. Then Apple has done a great job for Apple Silicon Macs that they run both native ARM apps and x64 apps very well. I use homebrew and within a few month the ARM64 forumlas are mostly working for me already. The main missing thing is Virtual Box but I have alternatives like UTM to run ARM Linux if I want (I do not need now because of Raspberry Pi 400).

Anyway, it is just my personal opinion. Sorry for the rant here. And it is great that you are planning to support ARM on Windows with libwdi.

Jul 06 '21 11:07 mcuee

There are A LOT of people out here that care about Windows on ARM. They're just getting discouraged that Microsoft got us this far, and then just seemed to lose interest in finishing it.

For a lot of people it's a matter of older software that there is no replacement for. I'm in that boat myself. But guess what, the old XP stuff works pretty darn well on a Pi 4 and Windows 10. You just need to give it the memory to run right, so get the 8GB version, and don't skimp on the SD card size . Booting Linux for the RTL stuff, then an emulator on top of that for the Windows program is not a good solution, but it's what a lot of people are trying to get by.

I have no doubt that as soon as an RTL-SDR driver that works on Windows 10 ARM64 on a Raspberry Pi 4 becomes available it'll have thousands of downloads in very short order. Maybe Microsoft is just used to thinking in terms of millions of new downloads a week, while I think in the thousand's, but still...

Jul 06 '21 13:07 dougmsbbs

Good to know that there are "There are A LOT of people out here that care about Windows on ARM". To me it seems the main interests are on Raspberry Pi 4 which somehow gets a license to run Windows on ARM. Raspberry Pi is an exception for Windows on ARM, not the norm.

If you read Microsoft document, it is all talking about Qualcomm stuff, which is more expensive than many Intel/AMD laptops. https://docs.microsoft.com/en-us/windows/uwp/porting/apps-on-arm

Anyway, Pete is committed to support libwdi on ARM and that is good.

For the projects I am involved, at least libusb already supports Windows on ARM. As for libusb-win32, no further development on the project. As for libusbK, I am not so sure if it is worth porting to Windows on ARM or not. Thanks for the changes of Microsoft on Driver signing, we are not going to update libusbk.sys any time soon but we will focus on the support of libusbk.dll which supports WinUSB.

Jul 07 '21 05:07 mcuee

@jkunkee you wrote the following

I believe Zadig relies on libusb's binary releases, so this needs to change upstream before Zadig Just Works(TM). in Re: https://daskunkee.blogspot.com/2020/02/tech-esp32-programming-from-arm64.html

I do not think this is a real issue for Pete, remember Pete is the original developer of libusb Windows, so he knows the ins and outs of libusb Windows. So there will be no issue for him to host the ARM binary for libusb Windows.

Most importantly libwdi/Zadig do not depend on libusb Windows binaries at all (it does not ship with libusb-1.0.dll). You may want to change your blog.

Jul 07 '21 05:07 mcuee

lib usb arm64 dll build made by rusb, great effort is the arm64 version of the lib usb dll

https://github.com/a1ien/rusb/issues/68

Jul 08 '21 01:07 sidd-kishan

Based on https://github.com/a1ien/rusb/issues/68, vcpkg has already libusb-1.0 Windows ARM binary if you do not want to build the binary by yourself (it is super easy to build libusb-1.0.dll for Windows ARM with VS2019). However, the issue here has nothing to do with that, as libwdi does not depend on libusb-1.0.dll binary at all.

Jul 08 '21 05:07 mcuee

I checked out some Youtube video, now it seems to be much easier to install Windows 10 or Windows 11 onto Raspberry Pi 4 and 400. So I kind of change a bit of my mind in this topic.

As for myself, I will not touch Windows on my Raspberry Pi 400 any time soon (Linux is good) and I have no intention to get an 8GB Raspberry Pi 4B. Maybe I will touch Windows 11 on next generation Raspberry Pi 5.

Sep 13 '21 08:09 mcuee

Namely: if you install the latest Windows 10 WDK, you still don't get any of the WDF and WinUSB coinstaller DLLs for arm64 (Still no arm64 directory). And what's more, even for ARM, there's no winusbcoinstaller2.dll provided, which means we can't support that platform either.

This is still true with Windows 11 WDK. I just installed Windows 11 WDK. https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk

Sep 13 '21 09:09 mcuee

I believe the way for WinUSB on ARM64 is probably different from ARM32/x86/AMD64, as per the following test and other WinUSB related tests (total 10 WinUSB related tests). Ref: https://docs.microsoft.com/en-us/windows-hardware/test/hlk/testref/e1c0c2dd-cd25-4f60-a4bc-c8544d481225

On the other hand, ARM32 is mostly dead. ARM64 is probably the future for Windows on ARM. https://community.osr.com/discussion/293059/32-bit-arm-driver-signing-a-forgotten-niche

Sep 13 '21 09:09 mcuee

As Jon mentioned:

the CoInstallers are not needed on Windows 10 on ARM because the first version to ship was 1709. You can drop the references to them for ARM64.

So the way to approach WinUSB on ARM64 should be to use a .inf that's similar to the one that was posted in this thread, updated for ARM64.

Unfortunately, it's because the .inf for ARM64 is going to be much simpler than the .inf for x64 and win32 that it makes things more complex to automate, because the .inf.in we use for WinUSB is tailored for systems where CoInstallers are needed, which means I'm going to have to add a different path and a different .inf.in for ARM64 installation.

However, this whole thing may be rendered completely moot by Windows 11, since Microsoft is no longer trusting certificates that are installed in Trusted Publishers for the signing of driver packages, and that is what we have been relying on to be able to install drivers on Windows 7 up to Windows 10 without having to ask users to enable test signing.

Which means that Zadig cannot be used on regular Windows 11 to install WinUSB (fails with Driver package failed signature validation. Error = 0x800B0100), and since it looks like the new way to get a custom driver package allowed for installation on a regular Windows 11 system is to go through a Microsoft web portal, this may very well spell the end of Zadig/libwdi altogether.

As such, unless there's a way to make libwdi/Zadig relevant for Window 11, I'm not sure spending time adding ARM64 support is that great of an investment...

Sep 13 '21 11:09 pbatard

However, this whole thing may be rendered completely moot by Windows 11, since Microsoft is no longer trusting certificates that are installed in Trusted Publishers for the signing of driver packages, and that is what we have been relying on to be able to install drivers on Windows 7 up to Windows 10 without having to ask users to enable test signing.

Which means that Zadig cannot be used on regular Windows 11 to install WinUSB (fails with Driver package failed signature validation. Error = 0x800B0100), and since it looks like the new way to get a custom driver package allowed for installation on a regular Windows 11 system is to go through a Microsoft web portal, this may very well spell the end of Zadig/libwdi altogether.

Hmm, where do you get this info that "Microsoft is no longer trusting certificates that are installed in Trusted Publishers for the signing of driver packages"?

For Windows 10, Microsoft also says that Attestation Signing (you need an EV certificate to create an account to sign in the Microsoft Partner Center Developer Dashboard and then get the signed driver package) or HLK (aka WHQL) is needed but in reality Zadig just works.

Sep 14 '21 01:09 mcuee

BTW, Zadig becomes more important now that Cross-Signing is dead. HLK is simply not practical for many drivers. https://www.osr.com/blog/2020/10/15/microsoft-driver-updates-allowed-win7-win8/

As of 1 July 2021, Microsoft is eliminating option #2, Cross-Signing. This will leave passing the HLK the only option for releasing drivers for Windows versions other than Windows 10.

Sep 14 '21 01:09 mcuee

Hmm, where do you get this info that "Microsoft is no longer trusting certificates that are installed in Trusted Publishers for the signing of driver packages"?

Testing and user reports.

I validated that even if you have the cert of your driver package installed into Trusted Publishers on Windows 11, Windows declares that your driver package's signature chain ends up with a certificate that isn't trusted.

Ergo, for Windows 11, "Microsoft is no longer trusting certificates that are installed in Trusted Publishers for the signing of driver packages".

As of 1 July 2021, Microsoft is eliminating option #2, Cross-Signing. This will leave passing the HLK the only option for releasing drivers for Windows versions other than Windows 10.

Yeah. And I'm having all the trouble in the world with this %^&*() requirement, because in parallel Microsoft have also managed to botch the web registration process that grants access to HLK, which prevents eligible folks (that is, everyone that has an EV cert) from registering.

So I have currently been sitting on a rather expensive EV certificate, issued more than a month ago, that I can't use... But that's a separate issue from what we're discussing here, and it doesn't remove the fact that Microsoft now appears to have taken a hard stance against delegating any trust to third parties, and especially end users.

So much for using a trust mechanism that is designed to be transitive and where the end user should at least always have some modicum of control over what can and cannot be installed on their system (through a process that should be achievable entirely offline)...

Sep 14 '21 07:09 pbatard

Wow, that is bad. I do not have Windows 11 installed now but I got a laptop which can upgrade to Windows 11 once it is released. I hope things can change over time.

Sep 14 '21 08:09 mcuee

As for the HLK Portal issue, you may want to ask in OSR forum at https://community.osr.com/categories/ntdev. I feel it is more useful than Microsoft sites. Experts like Peter Viscarola from OSR, Tim Roberts, and Microsoft's Doron Holan.

Ref: another issue with HLK which is different from yours. https://community.osr.com/discussion/293066/windows-hlk-signing-error

Sep 14 '21 08:09 mcuee

I do not have Windows 11 installed now but I got a laptop which can upgrade to Windows 11 once it is released

If you want, and you have a decent enough USB 3.0 drive (where random I/O speeds are good, so preferably SSD class or SSD into USB enclosure) you can test Windows 11 by creating a Windows To Go drive with Rufus. This will run Windows off the USB altogether without touching the internal disks, and this is pretty much how I am testing Windows 11.

You can of course get the latest Windows 11 ISO from the Insider program.

Even as they relinquished slightly on TPM, I don't expect Microsoft to change their stance on no longer trusting "Trusted Publishers" for driver packages, so, yeah, some folks are going to be in for some disappointment when they find that they can no longer rely on an application to automate driver installation for them.

As for the HLK Portal issue, you may want to ask in OSR forum at https://community.osr.com/categories/ntdev. I feel it is more useful than Microsoft sites. Experts like Peter Viscarola from OSR, Tim Roberts, and Microsoft's Doron Holan.

The problem is that this is a pure Microsoft issue (or most likely an issue between Microsoft and whatever subcontractor they used to design their hardware program registration web app), so, even if OSR includes Microsoft employees, I don't think they're going to be able to do much more than ask whoever is facing the problem but to create a support ticket (which we all did and are currently waiting on a slow resolution). And that's not to say I haven't also been exploring other ways to try to raise the visibility of this issue inside the Microsoft hierarchy, because there's really so much time I have for this utter bullshit of a registration process, when I need to have UEFI bootloaders Secure Boot signed for the release of Windows 11...

Sep 14 '21 10:09 pbatard

I will ask in the OSR forum about the point that "Microsoft is no longer trusting certificates that are installed in Trusted Publishers for the signing of driver packages". I think it is an important aspect which may affect quite some users using libusb related projects and potentially other projects as well.

Sep 14 '21 10:09 mcuee

Agreed. I think this is an important point to make there, especially as I still don't know exactly which of driver isolation or device guard or something else is responsible for the tightening of the rules, and I am also hopeful that the OSR experts may be able to point out to some kind of workaround to get user crafted driver packages installed on Windows 11, that doesn't involve having to seek Microsoft's formal approval...

Sep 14 '21 10:09 pbatard

Question asked in OSR forum: https://community.osr.com/discussion/293115/windows-11-and-alternative-driver-installation-method-in-libwdi

Sep 15 '21 02:09 mcuee

I got a new WIndows 10 laptop and upgraded it to WIndows 11. Zadig seems to work fine without any issues.

First test: I installed WinUSB driver for a generic HID device, no issues at all.

click for detailed log

Zadig 2.6.755
Windows 10 64-bit (Build 22000)
ini file 'zadig.ini' not found in 'C:\work\libusb' - default parameters will be used
default driver set to 'WinUSB'
0 devices found.
6 devices found.
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_8087&PID_0026&REV_0002
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_E0&SubClass_01&Prot_01
libwdi:debug [wdi_create_list] Driver version: 22.80.0.4
libwdi:debug [wdi_create_list] BTHUSB USB device (0): USB\VID_8087&PID_0026\5&586B51A&0&10
libwdi:debug [wdi_create_list] Device description: 'Intel(R) Wireless Bluetooth(R)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_1C7A&PID_0575&REV_1072
libwdi:debug [wdi_create_list] Compatible ID: USB\MS_COMP_WINUSB
libwdi:debug [wdi_create_list] Driver version: 3.7.1.1
libwdi:debug [wdi_create_list] WUDFRd USB device (2): USB\VID_1C7A&PID_0575\077E2F9A
libwdi:debug [wdi_create_list] Device description: 'EgisTec EH575'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_25A7&PID_FA23&REV_0241&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_01
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] HidUsb USB device (3): USB\VID_25A7&PID_FA23&MI_00\6&2E1AA5FE&0&0000
libwdi:debug [wdi_create_list] Device description: '2.4G Receiver (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_25A7&PID_FA23&REV_0241&MI_01
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_02
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] HidUsb USB device (5): USB\VID_25A7&PID_FA23&MI_01\6&2E1AA5FE&0&0001
libwdi:debug [wdi_create_list] Device description: '2.4G Receiver (Interface 1)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0925&PID_7001&REV_0001
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_00&Prot_00
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] HidUsb USB device (7): USB\VID_0925&PID_7001\5&586B51A&0&1
libwdi:debug [wdi_create_list] Device description: 'Generic HID'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_04F2&PID_B6DD&REV_2710&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_0e&SubClass_03&Prot_00
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.176
libwdi:debug [wdi_create_list] usbvideo USB device (8): USB\VID_04F2&PID_B6DD&MI_00\6&2F8D90E&0&0000
libwdi:debug [wdi_create_list] Device description: 'HD User Facing (Interface 0)'
Checking for Zadig updates...

Checking release channel...

No new release version found.

Using inf name: Generic_HID.inf
Successfully extracted driver files.
libwdi:info [extract_binaries] Successfully extracted driver files to 'C:\Users\xiaof\usb_driver'
libwdi:info [wdi_prepare_driver] Successfully created 'C:\Users\xiaof\usb_driver\Generic_HID.inf'
libwdi:info [wdi_prepare_driver] Creating and self-signing a .cat file...
libwdi:debug [AddFileHash] 'wdfcoinstaller01011.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\xiaof\usb_driver\amd64\wdfcoinstaller01011.dll'
libwdi:debug [AddFileHash] 'winusbcoinstaller2.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\xiaof\usb_driver\amd64\winusbcoinstaller2.dll'
libwdi:debug [AddFileHash] 'generic_hid.inf': INF type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\xiaof\usb_driver\generic_hid.inf'
libwdi:debug [AddFileHash] 'wdfcoinstaller01011.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\xiaof\usb_driver\x86\wdfcoinstaller01011.dll'
libwdi:debug [AddFileHash] 'winusbcoinstaller2.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\xiaof\usb_driver\x86\winusbcoinstaller2.dll'
libwdi:info [CreateCat] Successfully created file 'C:\Users\xiaof\usb_driver\Generic_HID.cat'
libwdi:debug [CreateSelfSignedCert] Set Enhanced Key Usage, URL and CPS
libwdi:debug [CreateSelfSignedCert] Created new key container
libwdi:debug [CreateSelfSignedCert] Generated new keypair...
libwdi:info [CreateSelfSignedCert] Created new self-signed certificate 'CN=USB\VID_0925&PID_7001 (libwdi autogenerated)'
libwdi:debug [SelfSignFile] Successfully created certificate 'CN=USB\VID_0925&PID_7001 (libwdi autogenerated)'
libwdi:info [SelfSignFile] Added certificate 'CN=USB\VID_0925&PID_7001 (libwdi autogenerated)' to 'Root' and 'TrustedPublisher' stores
libwdi:info [SelfSignFile] Successfully signed file 'C:\Users\xiaof\usb_driver\Generic_HID.cat'
libwdi:info [SelfSignFile] Successfully deleted private key
Installing driver. Please wait...
libwdi:debug [wdi_install_driver] Using progress bar mode
libwdi:debug [installer process] got parameter Generic_HID.inf
libwdi:debug [process_message] Got request for device_id
libwdi:debug [installer process] got device_id: 'USB\VID_0925&PID_7001\5&586B51A&0&1'
libwdi:debug [process_message] Got request for hardware_id
libwdi:debug [installer process] got hardware_id: 'USB\VID_0925&PID_7001&REV_0001'
libwdi:debug [installer process] got user_sid: 'S-1-5-21-2158618874-4192503731-4025798455-1001'
libwdi:debug [installer process] using syslog 'C:\WINDOWS\inf\setupapi.dev.log'
libwdi:debug [installer process] syslog reader thread started
libwdi:debug [installer process] successfully disabled the system restore point creation setting
libwdi:debug [process_message] Switching timeout to infinite
libwdi:debug [installer process] Installing driver for USB\VID_0925&PID_7001&REV_0001 - please wait...
libwdi:debug [syslog] <Garbled data>
libwdi:debug [syslog] >>>  [Device Install (UpdateDriverForPlugAndPlayDevices) - USB\VID_0925&PID_7001&REV_0001]
libwdi:debug [syslog] >>>  Section start 2021/10/06 19:59:39.281
libwdi:debug [syslog]       cmd: "C:\Users\xiaof\usb_driver\installer_x64.exe" "Generic_HID.inf"
libwdi:debug [syslog]      ndv: INF path: C:\Users\xiaof\usb_driver\Generic_HID.inf
libwdi:debug [syslog]      ndv: Install flags: 0x00000001
libwdi:debug [syslog]      ndv: {Update Device Driver - USB\VID_0925&PID_7001\5&586B51A&0&1}
libwdi:debug [syslog]      ndv:      Search options: 0x00000080
libwdi:debug [syslog]      ndv:      Searching single INF 'C:\Users\xiaof\usb_driver\Generic_HID.inf'
libwdi:debug [syslog]      dvi:      {Build Driver List} 19:59:39.323
libwdi:debug [syslog]      dvi:           Searching for hardware ID(s):
libwdi:debug [syslog]      dvi:                usb\vid_0925&pid_7001&rev_0001
libwdi:debug [syslog]      dvi:                usb\vid_0925&pid_7001
libwdi:debug [syslog]      dvi:           Searching for compatible ID(s):
libwdi:debug [syslog]      dvi:                usb\class_03&subclass_00&prot_00
libwdi:debug [syslog]      dvi:                usb\class_03&subclass_00
libwdi:debug [syslog]      dvi:                usb\class_03
libwdi:debug [syslog]      sig:           {_VERIFY_FILE_SIGNATURE} 19:59:39.404
libwdi:debug [syslog]      sig:                Key      = generic_hid.inf
libwdi:debug [syslog]      sig:                FilePath = c:\users\xiaof\usb_driver\generic_hid.inf
libwdi:debug [syslog]      sig:                Catalog  = c:\users\xiaof\usb_driver\Generic_HID.cat
libwdi:debug [syslog] !    sig:                Verifying file against specific (valid) catalog failed.
libwdi:debug [syslog] !    sig:                Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
libwdi:debug [syslog]      sig:           {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 19:59:39.454
libwdi:debug [syslog]      sig:           {_VERIFY_FILE_SIGNATURE} 19:59:39.465
libwdi:debug [syslog]      sig:                Key      = generic_hid.inf
libwdi:debug [syslog]      sig:                FilePath = c:\users\xiaof\usb_driver\generic_hid.inf
libwdi:debug [syslog]      sig:                Catalog  = c:\users\xiaof\usb_driver\Generic_HID.cat
libwdi:debug [syslog]      sig:                Success: File is signed in Authenticode(tm) catalog.
libwdi:debug [syslog]      sig:                Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
libwdi:debug [syslog]      sig:           {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 19:59:39.493
libwdi:debug [syslog]      dvi:           Created Driver Node:
libwdi:debug [syslog]      dvi:                HardwareID   - USB\VID_0925&PID_7001
libwdi:debug [syslog]      dvi:                InfName      - c:\users\xiaof\usb_driver\generic_hid.inf
libwdi:debug [syslog]      dvi:                DevDesc      - Generic HID
libwdi:debug [syslog]      dvi:                Section      - USB_Install
libwdi:debug [syslog]      dvi:                Rank         - 0x00ff0001
libwdi:debug [syslog]      dvi:                Signer Score - Authenticode
libwdi:debug [syslog]      dvi:                DrvDate      - 06/02/2012
libwdi:debug [syslog]      dvi:                Version      - 6.1.7600.16385
libwdi:debug [syslog]      dvi:      {Build Driver List - exit(0x00000000)} 19:59:39.556
libwdi:debug [syslog]      dvi:      {DIF_SELECTBESTCOMPATDRV} 19:59:39.572
libwdi:debug [syslog]      dvi:           Default installer: Enter 19:59:39.581
libwdi:debug [syslog]      dvi:                {Select Best Driver}
libwdi:debug [syslog]      dvi:                     Class GUID of device changed to: {88bae032-5a81-49f0-bc3d-a4ff138216d6}.
libwdi:debug [syslog]      dvi:                     Selected Driver:
libwdi:debug [syslog]      dvi:                          Description - Generic HID
libwdi:debug [syslog]      dvi:                          InfFile     - c:\users\xiaof\usb_driver\generic_hid.inf
libwdi:debug [syslog]      dvi:                          Section     - USB_Install
libwdi:debug [syslog]      dvi:                {Select Best Driver - exit(0x00000000)}
libwdi:debug [syslog]      dvi:           Default installer: Exit
libwdi:debug [syslog]      dvi:      {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 19:59:39.631
libwdi:debug [syslog]      ndv:      Force Installing Driver:
libwdi:debug [syslog]      ndv:           Inf Name       - generic_hid.inf
libwdi:debug [syslog]      ndv:           Driver Date    - 06/02/2012
libwdi:debug [syslog]      ndv:           Driver Version - 6.1.7600.16385
libwdi:debug [syslog]      sto:      {Setup Import Driver Package: c:\users\xiaof\usb_driver\generic_hid.inf} 19:59:39.662
libwdi:debug [syslog]      inf:           Provider: libwdi
libwdi:debug [syslog]      inf:           Class GUID: {88bae032-5a81-49f0-bc3d-a4ff138216d6}
libwdi:debug [syslog]      inf:           Driver Version: 06/02/2012,6.1.7600.16385
libwdi:debug [syslog]      inf:           Catalog File: Generic_HID.cat
libwdi:debug [syslog]      sto:           {Copy Driver Package: c:\users\xiaof\usb_driver\generic_hid.inf} 19:59:39.711
libwdi:debug [syslog]      sto:                Driver Package = c:\users\xiaof\usb_driver\generic_hid.inf
libwdi:debug [syslog]      sto:                Flags          = 0x00000007
libwdi:debug [syslog]      sto:                Destination    = C:\Users\xiaof\AppData\Local\Temp\{a9aeb791-c89b-d04f-a97f-8247faae40b3}
libwdi:debug [syslog]      sto:                Copying driver package files to 'C:\Users\xiaof\AppData\Local\Temp\{a9aeb791-c89b-d04f-a97f-8247faae40b3}'.
libwdi:debug [syslog]      flq:                {FILE_QUEUE_COMMIT} 19:59:39.742
libwdi:debug [syslog]      flq:                     Copying 'c:\users\xiaof\usb_driver\amd64\WdfCoInstaller01011.dll' to 'C:\Users\xiaof\AppData\Local\Temp\{a9aeb791-c89b-d04f-a97f-8247faae40b3}\amd64\WdfCoInstaller01011.dll'.
libwdi:debug [syslog]      flq:                     Copying 'c:\users\xiaof\usb_driver\amd64\WinUSBCoInstaller2.dll' to 'C:\Users\xiaof\AppData\Local\Temp\{a9aeb791-c89b-d04f-a97f-8247faae40b3}\amd64\WinUSBCoInstaller2.dll'.
libwdi:debug [syslog]      flq:                     Copying 'c:\users\xiaof\usb_driver\Generic_HID.cat' to 'C:\Users\xiaof\AppData\Local\Temp\{a9aeb791-c89b-d04f-a97f-8247faae40b3}\Generic_HID.cat'.
libwdi:debug [syslog]      flq:                     Copying 'c:\users\xiaof\usb_driver\generic_hid.inf' to 'C:\Users\xiaof\AppData\Local\Temp\{a9aeb791-c89b-d04f-a97f-8247faae40b3}\generic_hid.inf'.
libwdi:debug [syslog]      flq:                {FILE_QUEUE_COMMIT - exit(0x00000000)} 19:59:39.801
libwdi:debug [syslog]      sto:           {Copy Driver Package: exit(0x00000000)} 19:59:39.801
libwdi:debug [syslog]      ump:           Import flags: 0x00000000
libwdi:debug [syslog]      pol:           {Driver package policy check} 19:59:39.823
libwdi:debug [syslog]      pol:           {Driver package policy check - exit(0x00000000)} 19:59:39.823
libwdi:debug [syslog]      sto:           {Stage Driver Package: C:\Users\xiaof\AppData\Local\Temp\{a9aeb791-c89b-d04f-a97f-8247faae40b3}\generic_hid.inf} 19:59:39.823
libwdi:debug [syslog]      inf:                {Query Configurability: C:\Users\xiaof\AppData\Local\Temp\{a9aeb791-c89b-d04f-a97f-8247faae40b3}\generic_hid.inf} 19:59:39.823
libwdi:debug [syslog]      inf:                     Driver package uses WDF.
libwdi:debug [syslog]      inf:                     Driver package 'generic_hid.inf' is configurable.
libwdi:debug [syslog]      inf:                {Query Configurability: exit(0x00000000)} 19:59:39.823
libwdi:debug [syslog]      flq:                {FILE_QUEUE_COMMIT} 19:59:39.823
libwdi:debug [syslog]      flq:                     Copying 'C:\Users\xiaof\AppData\Local\Temp\{a9aeb791-c89b-d04f-a97f-8247faae40b3}\amd64\WdfCoInstaller01011.dll' to 'C:\WINDOWS\System32\DriverStore\Temp\{a9f26a25-705e-c84d-a55f-8fa613b759a6}\amd64\WdfCoInstaller01011.dll'.
libwdi:debug [syslog]      flq:                     Copying 'C:\Users\xiaof\AppData\Local\Temp\{a9aeb791-c89b-d04f-a97f-8247faae40b3}\amd64\WinUSBCoInstaller2.dll' to 'C:\WINDOWS\System32\DriverStore\Temp\{a9f26a25-705e-c84d-a55f-8fa613b759a6}\amd64\WinUSBCoInstaller2.dll'.
libwdi:debug [syslog]      flq:                     Copying 'C:\Users\xiaof\AppData\Local\Temp\{a9aeb791-c89b-d04f-a97f-8247faae40b3}\Generic_HID.cat' to 'C:\WINDOWS\System32\DriverStore\Temp\{a9f26a25-705e-c84d-a55f-8fa613b759a6}\Generic_HID.cat'.
libwdi:debug [syslog]      flq:                     Copying 'C:\Users\xiaof\AppData\Local\Temp\{a9aeb791-c89b-d04f-a97f-8247faae40b3}\generic_hid.inf' to 'C:\WINDOWS\System32\DriverStore\Temp\{a9f26a25-705e-c84d-a55f-8fa613b759a6}\generic_hid.inf'.
libwdi:debug [syslog]      flq:                {FILE_QUEUE_COMMIT - exit(0x00000000)} 19:59:39.881
libwdi:debug [syslog]      sto:                {DRIVERSTORE IMPORT VALIDATE} 19:59:39.881
libwdi:debug [syslog]      sig:                     Driver package catalog is valid.
libwdi:debug [syslog]      sig:                     {_VERIFY_FILE_SIGNATURE} 19:59:39.897
libwdi:debug [syslog]      sig:                          Key      = generic_hid.inf
libwdi:debug [syslog]      sig:                          FilePath = C:\WINDOWS\System32\DriverStore\Temp\{a9f26a25-705e-c84d-a55f-8fa613b759a6}\generic_hid.inf
libwdi:debug [syslog]      sig:                          Catalog  = C:\WINDOWS\System32\DriverStore\Temp\{a9f26a25-705e-c84d-a55f-8fa613b759a6}\Generic_HID.cat
libwdi:debug [syslog] !    sig:                          Verifying file against specific (valid) catalog failed.
libwdi:debug [syslog] !    sig:                          Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
libwdi:debug [syslog]      sig:                     {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 19:59:39.897
libwdi:debug [syslog]      sig:                     {_VERIFY_FILE_SIGNATURE} 19:59:39.897
libwdi:debug [syslog]      sig:                          Key      = generic_hid.inf
libwdi:debug [syslog]      sig:                          FilePath = C:\WINDOWS\System32\DriverStore\Temp\{a9f26a25-705e-c84d-a55f-8fa613b759a6}\generic_hid.inf
libwdi:debug [syslog]      sig:                          Catalog  = C:\WINDOWS\System32\DriverStore\Temp\{a9f26a25-705e-c84d-a55f-8fa613b759a6}\Generic_HID.cat
libwdi:debug [syslog]      sig:                          Success: File is signed in Authenticode(tm) catalog.
libwdi:debug [syslog]      sig:                          Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
libwdi:debug [syslog]      sig:                     {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 19:59:39.915
libwdi:debug [syslog]      sto:                {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 19:59:39.934
libwdi:debug [syslog]      sig:                Signer Score  = 0x0F000000 (Authenticode)
libwdi:debug [syslog]      sig:                Signer Name   = USB\VID_0925&PID_7001 (libwdi autogenerated)
libwdi:debug [syslog]      sto:                {Core Driver Package Import: generic_hid.inf_amd64_372bef0213623d3d} 19:59:39.934
libwdi:debug [syslog]      sto:                     {DRIVERSTORE IMPORT BEGIN} 19:59:39.934
libwdi:debug [syslog]      sto:                     {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 19:59:39.934
libwdi:debug [syslog]      cpy:                     {Copy Directory: C:\WINDOWS\System32\DriverStore\Temp\{a9f26a25-705e-c84d-a55f-8fa613b759a6}} 19:59:39.934
libwdi:debug [syslog]      cpy:                          Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\generic_hid.inf_amd64_372bef0213623d3d
libwdi:debug [syslog]      cpy:                          {Copy Directory: C:\WINDOWS\System32\DriverStore\Temp\{a9f26a25-705e-c84d-a55f-8fa613b759a6}\amd64} 19:59:39.934
libwdi:debug [syslog]      cpy:                               Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\generic_hid.inf_amd64_372bef0213623d3d\amd64
libwdi:debug [syslog]      cpy:                          {Copy Directory: exit(0x00000000)} 19:59:39.934
libwdi:debug [syslog]      cpy:                     {Copy Directory: exit(0x00000000)} 19:59:39.946
libwdi:debug [syslog]      idb:                     {Register Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\generic_hid.inf_amd64_372bef0213623d3d\generic_hid.inf} 19:59:39.946
libwdi:debug [syslog]      idb:                          Created driver package object 'generic_hid.inf_amd64_372bef0213623d3d' in SYSTEM database node.
libwdi:debug [syslog]      idb:                          Created driver INF file object 'oem108.inf' in SYSTEM database node.
libwdi:debug [syslog]      idb:                          Registered driver package 'generic_hid.inf_amd64_372bef0213623d3d' with 'oem108.inf'.
libwdi:debug [syslog]      idb:                     {Register Driver Package: exit(0x00000000)} 19:59:39.946
libwdi:debug [syslog]      idb:                     {Publish Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\generic_hid.inf_amd64_372bef0213623d3d\generic_hid.inf} 19:59:39.946
libwdi:debug [syslog]      idb:                          Activating driver package 'generic_hid.inf_amd64_372bef0213623d3d'.
libwdi:debug [syslog]      cpy:                          Published 'generic_hid.inf_amd64_372bef0213623d3d\generic_hid.inf' to 'oem108.inf'.
libwdi:debug [syslog]      idb:                          Indexed 2 device IDs for 'generic_hid.inf_amd64_372bef0213623d3d'.
libwdi:debug [syslog] !    sto:                          Ignoring changes to inbox device class {88bae032-5a81-49f0-bc3d-a4ff138216d6} through ClassInstall32 section.
libwdi:debug [syslog]      sto:                          Flushed driver database node 'SYSTEM'. Time = 0 ms
libwdi:debug [syslog]      idb:                     {Publish Driver Package: exit(0x00000000)} 19:59:39.953
libwdi:debug [syslog]      sto:                     {DRIVERSTORE IMPORT END} 19:59:39.953
libwdi:debug [syslog]      dvi:                          Flushed all driver package files to disk. Time = 0 ms
libwdi:debug [syslog]      sig:                          Installed catalog 'Generic_HID.cat' as 'oem108.cat'.
libwdi:debug [syslog]      sto:                     {DRIVERSTORE IMPORT END: exit(0x00000000)} 19:59:39.967
libwdi:debug [syslog]      sto:                {Core Driver Package Import: exit(0x00000000)} 19:59:39.967
libwdi:debug [syslog]      sto:           {Stage Driver Package: exit(0x00000000)} 19:59:39.967
libwdi:debug [syslog]      sto:      {Setup Import Driver Package - exit (0x00000000)} 19:59:39.999
libwdi:debug [syslog]      dvi:      Searching for hardware ID(s):
libwdi:debug [syslog]      dvi:           usb\vid_0925&pid_7001&rev_0001
libwdi:debug [syslog]      dvi:           usb\vid_0925&pid_7001
libwdi:debug [syslog]      dvi:      Searching for compatible ID(s):
libwdi:debug [syslog]      dvi:           usb\class_03&subclass_00&prot_00
libwdi:debug [syslog]      dvi:           usb\class_03&subclass_00
libwdi:debug [syslog]      dvi:           usb\class_03
libwdi:debug [syslog]      dvi:      Class GUID of device changed to: {88bae032-5a81-49f0-bc3d-a4ff138216d6}.
libwdi:debug [syslog]      ump:      {Plug and Play Service: Device Install for USB\VID_0925&PID_7001\5&586B51A&0&1}
libwdi:debug [syslog]      dvi:           {Core Device Install} 19:59:40.077
libwdi:debug [syslog]      dvi:                {Configure Device - USB\VID_0925&PID_7001\5&586B51A&0&1} 19:59:40.077
libwdi:debug [syslog]      dvi:                     Device Status: 0x0180600a
libwdi:debug [syslog]      dvi:                     Config Flags: 0x00000000
libwdi:debug [syslog]      dvi:                     Parent Device: USB\ROOT_HUB30\4&12c539f&0&0
libwdi:debug [syslog]      sto:                     {Configure Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\generic_hid.inf_amd64_372bef0213623d3d\generic_hid.inf}
libwdi:debug [syslog]      sto:                          Source Filter  = usb\vid_0925&pid_7001
libwdi:debug [syslog]      inf:                          Class GUID     = {88bae032-5a81-49f0-bc3d-a4ff138216d6}
libwdi:debug [syslog]      inf:                          Class Options  = Configurable BootCritical
libwdi:debug [syslog]      idb:                          {Configure Device Setup Class: {88bae032-5a81-49f0-bc3d-a4ff138216d6}}
libwdi:debug [syslog] !    idb:                               Skipping update of existing inbox class {88bae032-5a81-49f0-bc3d-a4ff138216d6}.
libwdi:debug [syslog]      idb:                          {Configure Device Setup Class: exit(0x00000000)}
libwdi:debug [syslog]      inf:                          {Configure Driver: Generic HID}
libwdi:debug [syslog]      inf:                               Section Name = USB_Install
libwdi:debug [syslog]      inf:                               {Add Service: WinUSB}
libwdi:debug [syslog]      inf:                                    Start Type    = 3
libwdi:debug [syslog]      inf:                                    Service Type  = 1
libwdi:debug [syslog]      inf:                                    Error Control = 1
libwdi:debug [syslog]      inf:                                    Image Path    = \SystemRoot\System32\drivers\WinUSB.sys
libwdi:debug [syslog]      inf:                                    Display Name  = WinUSB - Kernel Driver 06/02/2012 6.1.7600.16385
libwdi:debug [syslog]      inf:                                    Updated service 'WinUSB'.
libwdi:debug [syslog]      inf:                               {Add Service: exit(0x00000000)}
libwdi:debug [syslog]      inf:                               Hardware Id  = USB\VID_0925&PID_7001
libwdi:debug [syslog]      inf:                               {Configure Driver Configuration: USB_Install}
libwdi:debug [syslog]      inf:                                    Service Name  = WinUSB
libwdi:debug [syslog]      inf:                                    Included INFs = winusb.inf
libwdi:debug [syslog]      inf:                                    Config Flags  = 0x00000000
libwdi:debug [syslog]      inf:                               {Configure Driver Configuration: exit(0x00000000)}
libwdi:debug [syslog]      inf:                          {Configure Driver: exit(0x00000000)}
libwdi:debug [syslog]      flq:                          {FILE_QUEUE_COMMIT} 19:59:40.105
libwdi:debug [syslog]      flq:                               Hardlinking 'C:\WINDOWS\System32\DriverStore\FileRepository\winusb.inf_amd64_d1861060a4b1a6d4\winusb.sys' to 'C:\WINDOWS\System32\drivers\winusb.sys'.
libwdi:debug [syslog]      cpy:                               Existing file 'C:\WINDOWS\System32\drivers\winusb.sys' remains unchanged.
libwdi:debug [syslog]      flq:                               Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\generic_hid.inf_amd64_372bef0213623d3d\amd64\WinUSBCoInstaller2.dll' to 'C:\WINDOWS\System32\WinUSBCoInstaller2.dll'.
libwdi:debug [syslog]      flq:                               Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\generic_hid.inf_amd64_372bef0213623d3d\amd64\WdfCoInstaller01011.dll' to 'C:\WINDOWS\System32\WdfCoInstaller01011.dll'.
libwdi:debug [syslog]      flq:                          {FILE_QUEUE_COMMIT - exit(0x00000000)} 19:59:40.123
libwdi:debug [syslog]      dvi:                          Existing files modified, may need to restart related services.
libwdi:debug [syslog]      sto:                     {Configure Driver Package: exit(0x00000bc3)}
libwdi:debug [syslog]      dvi:                     Restart required for any devices using this driver.
libwdi:debug [syslog]      dvi:                     Install Device: Configuring device. 19:59:40.123
libwdi:debug [syslog]      dvi:                          Configuration: oem108.inf:usb\vid_0925&pid_7001,USB_Install
libwdi:debug [syslog]      dvi:                     Install Device: Configuring device completed. 19:59:40.130
libwdi:debug [syslog]      dvi:                     Device Status: 0x0180600a
libwdi:debug [syslog]      dvi:                     {Restarting Devices} 19:59:40.132
libwdi:debug [syslog]      dvi:                          Query-remove: USB\VID_0925&PID_7001\5&586B51A&0&1
libwdi:debug [syslog]      dvi:                          Query-remove: USB\VID_1C7A&PID_0575\077E2F9A
libwdi:debug [syslog]      dvi:                          Start: USB\VID_0925&PID_7001\5&586B51A&0&1
libwdi:debug [syslog]      dvi:                          Start: USB\VID_1C7A&PID_0575\077E2F9A
libwdi:debug [syslog]      dvi:                          Restart verified: USB\VID_0925&PID_7001\5&586B51A&0&1
libwdi:debug [syslog]      dvi:                          Restart verified: USB\VID_1C7A&PID_0575\077E2F9A
libwdi:debug [syslog]      dvi:                     {Restarting Devices exit} 19:59:40.786
libwdi:debug [syslog]      dvi:                {Configure Device - exit(0x00000000)} 19:59:40.788
libwdi:debug [syslog]      dvi:           {Core Device Install - exit(0x00000000)} 19:59:40.790
libwdi:debug [syslog]      ump:      {Plug and Play Service: Device Install exit(00000000)}
libwdi:debug [syslog]      ndv: {Update Device Driver - exit(00000000)}
libwdi:debug [syslog]      ndv: {Install Related Drivers} 19:59:40.814
libwdi:debug [syslog]      ndv: {Install Related Drivers: exit(0x00000000)} 19:59:40.824
libwdi:debug [process_message] Switching timeout back to finite
libwdi:debug [installer process] driver update completed
libwdi:debug [installer process] re-enumerating driver node USB\VID_0925&PID_7001\5&586B51A&0&1...
libwdi:debug [installer process] re-enumeration succeeded...
libwdi:debug [process_message] Installer process completed
libwdi:debug [installer process] successfully restored the system restore point creation setting
Driver Installation: SUCCESS
6 devices found.
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_8087&PID_0026&REV_0002
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_E0&SubClass_01&Prot_01
libwdi:debug [wdi_create_list] Driver version: 22.80.0.4
libwdi:debug [wdi_create_list] BTHUSB USB device (0): USB\VID_8087&PID_0026\5&586B51A&0&10
libwdi:debug [wdi_create_list] Device description: 'Intel(R) Wireless Bluetooth(R)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_1C7A&PID_0575&REV_1072
libwdi:debug [wdi_create_list] Compatible ID: USB\MS_COMP_WINUSB
libwdi:debug [wdi_create_list] Driver version: 3.7.1.1
libwdi:debug [wdi_create_list] WUDFRd USB device (2): USB\VID_1C7A&PID_0575\077E2F9A
libwdi:debug [wdi_create_list] Device description: 'EgisTec EH575'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_25A7&PID_FA23&REV_0241&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_01
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] HidUsb USB device (3): USB\VID_25A7&PID_FA23&MI_00\6&2E1AA5FE&0&0000
libwdi:debug [wdi_create_list] Device description: '2.4G Receiver (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_25A7&PID_FA23&REV_0241&MI_01
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_02
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] HidUsb USB device (5): USB\VID_25A7&PID_FA23&MI_01\6&2E1AA5FE&0&0001
libwdi:debug [wdi_create_list] Device description: '2.4G Receiver (Interface 1)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0925&PID_7001&REV_0001
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_00&Prot_00
libwdi:debug [wdi_create_list] Driver version: 6.1.7600.16385
libwdi:debug [wdi_create_list] WinUSB USB device (7): USB\VID_0925&PID_7001\5&586B51A&0&1
libwdi:debug [wdi_create_list] Device description: 'Generic HID'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_04F2&PID_B6DD&REV_2710&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_0e&SubClass_03&Prot_00
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.176
libwdi:debug [wdi_create_list] usbvideo USB device (8): USB\VID_04F2&PID_B6DD&MI_00\6&2F8D90E&0&0000
libwdi:debug [wdi_create_list] Device description: 'HD User Facing (Interface 0)'
6 devices found.
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_8087&PID_0026&REV_0002
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_E0&SubClass_01&Prot_01
libwdi:debug [wdi_create_list] Driver version: 22.80.0.4
libwdi:debug [wdi_create_list] BTHUSB USB device (0): USB\VID_8087&PID_0026\5&586B51A&0&10
libwdi:debug [wdi_create_list] Device description: 'Intel(R) Wireless Bluetooth(R)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_1C7A&PID_0575&REV_1072
libwdi:debug [wdi_create_list] Compatible ID: USB\MS_COMP_WINUSB
libwdi:debug [wdi_create_list] Driver version: 3.7.1.1
libwdi:debug [wdi_create_list] WUDFRd USB device (2): USB\VID_1C7A&PID_0575\077E2F9A
libwdi:debug [wdi_create_list] Device description: 'EgisTec EH575'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_25A7&PID_FA23&REV_0241&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_01
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] HidUsb USB device (3): USB\VID_25A7&PID_FA23&MI_00\6&2E1AA5FE&0&0000
libwdi:debug [wdi_create_list] Device description: '2.4G Receiver (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_25A7&PID_FA23&REV_0241&MI_01
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_02
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] HidUsb USB device (5): USB\VID_25A7&PID_FA23&MI_01\6&2E1AA5FE&0&0001
libwdi:debug [wdi_create_list] Device description: '2.4G Receiver (Interface 1)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0925&PID_7001&REV_0001
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_00&Prot_00
libwdi:debug [wdi_create_list] Driver version: 6.1.7600.16385
libwdi:debug [wdi_create_list] WinUSB USB device (7): USB\VID_0925&PID_7001\5&586B51A&0&1
libwdi:debug [wdi_create_list] Device description: 'Generic HID'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_04F2&PID_B6DD&REV_2710&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_0e&SubClass_03&Prot_00
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.176
libwdi:debug [wdi_create_list] usbvideo USB device (8): USB\VID_04F2&PID_B6DD&MI_00\6&2F8D90E&0&0000
libwdi:debug [wdi_create_list] Device description: 'HD User Facing (Interface 0)'

Oct 06 '21 12:10 mcuee

Second test: replace FT2232H (0403:6010) USB Composite Parent driver with WinUSB, no issues as well.

click for the debug log

Zadig 2.6.755
Windows 10 64-bit (Build 22000)
ini file 'zadig.ini' not found in 'C:\work\libusb' - default parameters will be used
default driver set to 'WinUSB'
0 devices found.
7 devices found.
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_8087&PID_0026&REV_0002
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_E0&SubClass_01&Prot_01
libwdi:debug [wdi_create_list] Driver version: 22.80.0.4
libwdi:debug [wdi_create_list] BTHUSB USB device (1): USB\VID_8087&PID_0026\5&586B51A&0&10
libwdi:debug [wdi_create_list] Device description: 'Intel(R) Wireless Bluetooth(R)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_1C7A&PID_0575&REV_1072
libwdi:debug [wdi_create_list] Compatible ID: USB\MS_COMP_WINUSB
libwdi:debug [wdi_create_list] Driver version: 3.7.1.1
libwdi:debug [wdi_create_list] WUDFRd USB device (3): USB\VID_1C7A&PID_0575\077E2F9A
libwdi:debug [wdi_create_list] Device description: 'EgisTec EH575'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_25A7&PID_FA23&REV_0241&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_01
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] HidUsb USB device (4): USB\VID_25A7&PID_FA23&MI_00\6&2E1AA5FE&0&0000
libwdi:debug [wdi_create_list] Device description: '2.4G Receiver (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_25A7&PID_FA23&REV_0241&MI_01
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_02
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] HidUsb USB device (6): USB\VID_25A7&PID_FA23&MI_01\6&2E1AA5FE&0&0001
libwdi:debug [wdi_create_list] Device description: '2.4G Receiver (Interface 1)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0403&PID_6010&REV_0700&MI_01
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_ff&SubClass_ff&Prot_ff
libwdi:debug [wdi_create_list] Driver version: 2.12.36.4
libwdi:debug [wdi_create_list] FTDIBUS USB device (8): USB\VID_0403&PID_6010&MI_01\6&C7EA758&0&0001
libwdi:debug [wdi_create_list] Device description: 'Lattice FTUSB Interface Cable (Interface 1)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0403&PID_6010&REV_0700&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_ff&SubClass_ff&Prot_ff
libwdi:debug [wdi_create_list] Driver version: 2.12.36.4
libwdi:debug [wdi_create_list] FTDIBUS USB device (9): USB\VID_0403&PID_6010&MI_00\6&C7EA758&0&0000
libwdi:debug [wdi_create_list] Device description: 'Lattice FTUSB Interface Cable (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_04F2&PID_B6DD&REV_2710&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_0e&SubClass_03&Prot_00
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.176
libwdi:debug [wdi_create_list] usbvideo USB device (10): USB\VID_04F2&PID_B6DD&MI_00\6&2F8D90E&0&0000
libwdi:debug [wdi_create_list] Device description: 'HD User Facing (Interface 0)'
10 devices found.
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0403&PID_6010&REV_0700
libwdi:debug [wdi_create_list] Compatible ID: USB\DevClass_00&SubClass_00&Prot_00
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] usbccgp USB device (0): USB\VID_0403&PID_6010\5&586B51A&0&1
libwdi:debug [wdi_create_list] Device description: 'Lattice FTUSB Interface Cable (Composite Parent)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_8087&PID_0026&REV_0002
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_E0&SubClass_01&Prot_01
libwdi:debug [wdi_create_list] Driver version: 22.80.0.4
libwdi:debug [wdi_create_list] BTHUSB USB device (1): USB\VID_8087&PID_0026\5&586B51A&0&10
libwdi:debug [wdi_create_list] Device description: 'Intel(R) Wireless Bluetooth(R)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_04F2&PID_B6DD&REV_2710
libwdi:debug [wdi_create_list] Compatible ID: USB\DevClass_00&SubClass_00&Prot_00
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] usbccgp USB device (2): USB\VID_04F2&PID_B6DD\0001
libwdi:debug [wdi_create_list] Device description: 'HD User Facing (Composite Parent)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_1C7A&PID_0575&REV_1072
libwdi:debug [wdi_create_list] Compatible ID: USB\MS_COMP_WINUSB
libwdi:debug [wdi_create_list] Driver version: 3.7.1.1
libwdi:debug [wdi_create_list] WUDFRd USB device (3): USB\VID_1C7A&PID_0575\077E2F9A
libwdi:debug [wdi_create_list] Device description: 'EgisTec EH575'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_25A7&PID_FA23&REV_0241&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_01
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] HidUsb USB device (4): USB\VID_25A7&PID_FA23&MI_00\6&2E1AA5FE&0&0000
libwdi:debug [wdi_create_list] Device description: '2.4G Receiver (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_25A7&PID_FA23&REV_0241
libwdi:debug [wdi_create_list] Compatible ID: USB\DevClass_00&SubClass_00&Prot_00
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] usbccgp USB device (5): USB\VID_25A7&PID_FA23\5&586B51A&0&3
libwdi:debug [wdi_create_list] Device description: '2.4G Receiver (Composite Parent)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_25A7&PID_FA23&REV_0241&MI_01
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_02
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] HidUsb USB device (6): USB\VID_25A7&PID_FA23&MI_01\6&2E1AA5FE&0&0001
libwdi:debug [wdi_create_list] Device description: '2.4G Receiver (Interface 1)'
libwdi:debug [wdi_create_list] Hardware ID: USB\ROOT_HUB30&VID8086&PIDA0ED&REV0020
libwdi:debug [wdi_create_list] Compatible ID: 
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.65
libwdi:debug [wdi_create_list] USBHUB3 USB device (7): USB\ROOT_HUB30\4&12C539F&0&0
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0403&PID_6010&REV_0700&MI_01
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_ff&SubClass_ff&Prot_ff
libwdi:debug [wdi_create_list] Driver version: 2.12.36.4
libwdi:debug [wdi_create_list] FTDIBUS USB device (8): USB\VID_0403&PID_6010&MI_01\6&C7EA758&0&0001
libwdi:debug [wdi_create_list] Device description: 'Lattice FTUSB Interface Cable (Interface 1)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0403&PID_6010&REV_0700&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_ff&SubClass_ff&Prot_ff
libwdi:debug [wdi_create_list] Driver version: 2.12.36.4
libwdi:debug [wdi_create_list] FTDIBUS USB device (9): USB\VID_0403&PID_6010&MI_00\6&C7EA758&0&0000
libwdi:debug [wdi_create_list] Device description: 'Lattice FTUSB Interface Cable (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_04F2&PID_B6DD&REV_2710&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_0e&SubClass_03&Prot_00
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.176
libwdi:debug [wdi_create_list] usbvideo USB device (10): USB\VID_04F2&PID_B6DD&MI_00\6&2F8D90E&0&0000
libwdi:debug [wdi_create_list] Device description: 'HD User Facing (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\ROOT_HUB30&VID8086&PID9A13&REV0001
libwdi:debug [wdi_create_list] Compatible ID: 
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.65
libwdi:debug [wdi_create_list] USBHUB3 USB device (11): USB\ROOT_HUB30\4&1A63DC7C&0&0
Using inf name: Lattice_FTUSB_Interface_Cable_(Composite_Parent).inf
Successfully extracted driver files.
libwdi:info [extract_binaries] Successfully extracted driver files to 'C:\Users\xiaof\usb_driver'
libwdi:info [wdi_prepare_driver] Successfully created 'C:\Users\xiaof\usb_driver\Lattice_FTUSB_Interface_Cable_(Composite_Parent).inf'
libwdi:info [wdi_prepare_driver] Creating and self-signing a .cat file...
libwdi:debug [AddFileHash] 'wdfcoinstaller01011.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\xiaof\usb_driver\amd64\wdfcoinstaller01011.dll'
libwdi:debug [AddFileHash] 'winusbcoinstaller2.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\xiaof\usb_driver\amd64\winusbcoinstaller2.dll'
libwdi:debug [AddFileHash] 'lattice_ftusb_interface_cable_(composite_parent).inf': INF type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\xiaof\usb_driver\lattice_ftusb_interface_cable_(composite_parent).inf'
libwdi:debug [AddFileHash] 'wdfcoinstaller01011.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\xiaof\usb_driver\x86\wdfcoinstaller01011.dll'
libwdi:debug [AddFileHash] 'winusbcoinstaller2.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\xiaof\usb_driver\x86\winusbcoinstaller2.dll'
libwdi:info [CreateCat] Successfully created file 'C:\Users\xiaof\usb_driver\Lattice_FTUSB_Interface_Cable_(Composite_Parent).cat'
libwdi:debug [CreateSelfSignedCert] Set Enhanced Key Usage, URL and CPS
libwdi:debug [CreateSelfSignedCert] Created new key container
libwdi:debug [CreateSelfSignedCert] Generated new keypair...
libwdi:info [CreateSelfSignedCert] Created new self-signed certificate 'CN=USB\VID_0403&PID_6010 (libwdi autogenerated)'
libwdi:debug [SelfSignFile] Successfully created certificate 'CN=USB\VID_0403&PID_6010 (libwdi autogenerated)'
libwdi:info [SelfSignFile] Added certificate 'CN=USB\VID_0403&PID_6010 (libwdi autogenerated)' to 'Root' and 'TrustedPublisher' stores
libwdi:info [SelfSignFile] Successfully signed file 'C:\Users\xiaof\usb_driver\Lattice_FTUSB_Interface_Cable_(Composite_Parent).cat'
libwdi:info [SelfSignFile] Successfully deleted private key
Installing driver. Please wait...
libwdi:debug [wdi_install_driver] Using progress bar mode
libwdi:debug [installer process] got parameter Lattice_FTUSB_Interface_Cable_(Composite_Parent).inf
libwdi:debug [process_message] Got request for device_id
libwdi:debug [installer process] got device_id: 'USB\VID_0403&PID_6010\5&586B51A&0&1'
libwdi:debug [process_message] Got request for hardware_id
libwdi:debug [installer process] got hardware_id: 'USB\VID_0403&PID_6010&REV_0700'
libwdi:debug [installer process] got user_sid: 'S-1-5-21-2158618874-4192503731-4025798455-1001'
libwdi:debug [installer process] using syslog 'C:\WINDOWS\inf\setupapi.dev.log'
libwdi:debug [installer process] syslog reader thread started
libwdi:debug [installer process] successfully disabled the system restore point creation setting
libwdi:debug [process_message] Switching timeout to infinite
libwdi:debug [installer process] Installing driver for USB\VID_0403&PID_6010&REV_0700 - please wait...
libwdi:debug [syslog] ll (UpdateDriverForPlugAndPlayDevices) - USB\VID_0403&PID_6010&REV_0700]
libwdi:debug [syslog] >>>  Section start 2021/10/06 20:09:00.284
libwdi:debug [syslog]       cmd: "C:\Users\xiaof\usb_driver\installer_x64.exe" "Lattice_FTUSB_Interface_Cable_(Composite_Parent).inf"
libwdi:debug [syslog]      ndv: INF path: C:\Users\xiaof\usb_driver\Lattice_FTUSB_Interface_Cable_(Composite_Parent).inf
libwdi:debug [syslog]      ndv: Install flags: 0x00000001
libwdi:debug [syslog]      ndv: {Update Device Driver - USB\VID_0403&PID_6010\5&586B51A&0&1}
libwdi:debug [syslog]      ndv:      Search options: 0x00000080
libwdi:debug [syslog]      ndv:      Searching single INF 'C:\Users\xiaof\usb_driver\Lattice_FTUSB_Interface_Cable_(Composite_Parent).inf'
libwdi:debug [syslog]      dvi:      {Build Driver List} 20:09:00.390
libwdi:debug [syslog]      dvi:           Searching for hardware ID(s):
libwdi:debug [syslog]      dvi:                usb\vid_0403&pid_6010&rev_0700
libwdi:debug [syslog]      dvi:                usb\vid_0403&pid_6010
libwdi:debug [syslog]      dvi:           Searching for compatible ID(s):
libwdi:debug [syslog]      dvi:                usb\devclass_00&subclass_00&prot_00
libwdi:debug [syslog]      dvi:                usb\devclass_00&subclass_00
libwdi:debug [syslog]      dvi:                usb\devclass_00
libwdi:debug [syslog]      dvi:                usb\composite
libwdi:debug [syslog]      sig:           {_VERIFY_FILE_SIGNATURE} 20:09:00.479
libwdi:debug [syslog]      sig:                Key      = lattice_ftusb_interface_cable_(composite_parent).inf
libwdi:debug [syslog]      sig:                FilePath = c:\users\xiaof\usb_driver\lattice_ftusb_interface_cable_(composite_parent).inf
libwdi:debug [syslog]      sig:                Catalog  = c:\users\xiaof\usb_driver\Lattice_FTUSB_Interface_Cable_(Composite_Parent).cat
libwdi:debug [syslog] !    sig:                Verifying file against specific (valid) catalog failed.
libwdi:debug [syslog] !    sig:                Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
libwdi:debug [syslog]      sig:           {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 20:09:00.539
libwdi:debug [syslog]      sig:           {_VERIFY_FILE_SIGNATURE} 20:09:00.539
libwdi:debug [syslog]      sig:                Key      = lattice_ftusb_interface_cable_(composite_parent).inf
libwdi:debug [syslog]      sig:                FilePath = c:\users\xiaof\usb_driver\lattice_ftusb_interface_cable_(composite_parent).inf
libwdi:debug [syslog]      sig:                Catalog  = c:\users\xiaof\usb_driver\Lattice_FTUSB_Interface_Cable_(Composite_Parent).cat
libwdi:debug [syslog]      sig:                Success: File is signed in Authenticode(tm) catalog.
libwdi:debug [syslog]      sig:                Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
libwdi:debug [syslog]      sig:           {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 20:09:00.602
libwdi:debug [syslog]      dvi:           Created Driver Node:
libwdi:debug [syslog]      dvi:                HardwareID   - USB\VID_0403&PID_6010
libwdi:debug [syslog]      dvi:                InfName      - c:\users\xiaof\usb_driver\lattice_ftusb_interface_cable_(composite_parent).inf
libwdi:debug [syslog]      dvi:                DevDesc      - Lattice FTUSB Interface Cable (Composite Parent)
libwdi:debug [syslog]      dvi:                Section      - USB_Install
libwdi:debug [syslog]      dvi:                Rank         - 0x00ff0001
libwdi:debug [syslog]      dvi:                Signer Score - Authenticode
libwdi:debug [syslog]      dvi:                DrvDate      - 06/02/2012
libwdi:debug [syslog]      dvi:                Version      - 6.1.7600.16385
libwdi:debug [syslog]      dvi:      {Build Driver List - exit(0x00000000)} 20:09:00.688
libwdi:debug [syslog]      dvi:      {DIF_SELECTBESTCOMPATDRV} 20:09:00.697
libwdi:debug [syslog]      dvi:           Default installer: Enter 20:09:00.706
libwdi:debug [syslog]      dvi:                {Select Best Driver}
libwdi:debug [syslog]      dvi:                     Class GUID of device changed to: {88bae032-5a81-49f0-bc3d-a4ff138216d6}.
libwdi:debug [syslog]      dvi:                     Selected Driver:
libwdi:debug [syslog]      dvi:                          Description - Lattice FTUSB Interface Cable (Composite Parent)
libwdi:debug [syslog]      dvi:                          InfFile     - c:\users\xiaof\usb_driver\lattice_ftusb_interface_cable_(composite_parent).inf
libwdi:debug [syslog]      dvi:                          Section     - USB_Install
libwdi:debug [syslog]      dvi:                {Select Best Driver - exit(0x00000000)}
libwdi:debug [syslog]      dvi:           Default installer: Exit
libwdi:debug [syslog]      dvi:      {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 20:09:00.784
libwdi:debug [syslog]      ndv:      Force Installing Driver:
libwdi:debug [syslog]      ndv:           Inf Name       - lattice_ftusb_interface_cable_(composite_parent).inf
libwdi:debug [syslog]      ndv:           Driver Date    - 06/02/2012
libwdi:debug [syslog]      ndv:           Driver Version - 6.1.7600.16385
libwdi:debug [syslog]      sto:      {Setup Import Driver Package: c:\users\xiaof\usb_driver\lattice_ftusb_interface_cable_(composite_parent).inf} 20:09:00.817
libwdi:debug [syslog]      inf:           Provider: libwdi
libwdi:debug [syslog]      inf:           Class GUID: {88bae032-5a81-49f0-bc3d-a4ff138216d6}
libwdi:debug [syslog]      inf:           Driver Version: 06/02/2012,6.1.7600.16385
libwdi:debug [syslog]      inf:           Catalog File: Lattice_FTUSB_Interface_Cable_(Composite_Parent).cat
libwdi:debug [syslog]      sto:           {Copy Driver Package: c:\users\xiaof\usb_driver\lattice_ftusb_interface_cable_(composite_parent).inf} 20:09:00.861
libwdi:debug [syslog]      sto:                Driver Package = c:\users\xiaof\usb_driver\lattice_ftusb_interface_cable_(composite_parent).inf
libwdi:debug [syslog]      sto:                Flags          = 0x00000007
libwdi:debug [syslog]      sto:                Destination    = C:\Users\xiaof\AppData\Local\Temp\{ceb54774-5cde-6345-82c8-7032e7241339}
libwdi:debug [syslog]      sto:                Copying driver package files to 'C:\Users\xiaof\AppData\Local\Temp\{ceb54774-5cde-6345-82c8-7032e7241339}'.
libwdi:debug [syslog]      flq:                {FILE_QUEUE_COMMIT} 20:09:00.898
libwdi:debug [syslog]      flq:                     Copying 'c:\users\xiaof\usb_driver\amd64\WdfCoInstaller01011.dll' to 'C:\Users\xiaof\AppData\Local\Temp\{ceb54774-5cde-6345-82c8-7032e7241339}\amd64\WdfCoInstaller01011.dll'.
libwdi:debug [syslog]      flq:                     Copying 'c:\users\xiaof\usb_driver\amd64\WinUSBCoInstaller2.dll' to 'C:\Users\xiaof\AppData\Local\Temp\{ceb54774-5cde-6345-82c8-7032e7241339}\amd64\WinUSBCoInstaller2.dll'.
libwdi:debug [syslog]      flq:                     Copying 'c:\users\xiaof\usb_driver\Lattice_FTUSB_Interface_Cable_(Composite_Parent).cat' to 'C:\Users\xiaof\AppData\Local\Temp\{ceb54774-5cde-6345-82c8-7032e7241339}\Lattice_FTUSB_Interface_Cable_(Composite_Parent).cat'.
libwdi:debug [syslog]      flq:                     Copying 'c:\users\xiaof\usb_driver\lattice_ftusb_interface_cable_(composite_parent).inf' to 'C:\Users\xiaof\AppData\Local\Temp\{ceb54774-5cde-6345-82c8-7032e7241339}\lattice_ftusb_interface_cable_(composite_parent).inf'.
libwdi:debug [syslog]      flq:                {FILE_QUEUE_COMMIT - exit(0x00000000)} 20:09:00.947
libwdi:debug [syslog]      sto:           {Copy Driver Package: exit(0x00000000)} 20:09:00.962
libwdi:debug [syslog]      ump:           Import flags: 0x00000000
libwdi:debug [syslog]      pol:           {Driver package policy check} 20:09:00.969
libwdi:debug [syslog]      pol:           {Driver package policy check - exit(0x00000000)} 20:09:00.969
libwdi:debug [syslog]      sto:           {Stage Driver Package: C:\Users\xiaof\AppData\Local\Temp\{ceb54774-5cde-6345-82c8-7032e7241339}\lattice_ftusb_interface_cable_(composite_parent).inf} 20:09:00.969
libwdi:debug [syslog]      inf:                {Query Configurability: C:\Users\xiaof\AppData\Local\Temp\{ceb54774-5cde-6345-82c8-7032e7241339}\lattice_ftusb_interface_cable_(composite_parent).inf} 20:09:00.969
libwdi:debug [syslog]      inf:                     Driver package uses WDF.
libwdi:debug [syslog]      inf:                     Driver package 'lattice_ftusb_interface_cable_(composite_parent).inf' is configurable.
libwdi:debug [syslog]      inf:                {Query Configurability: exit(0x00000000)} 20:09:00.969
libwdi:debug [syslog]      flq:                {FILE_QUEUE_COMMIT} 20:09:00.985
libwdi:debug [syslog]      flq:                     Copying 'C:\Users\xiaof\AppData\Local\Temp\{ceb54774-5cde-6345-82c8-7032e7241339}\amd64\WdfCoInstaller01011.dll' to 'C:\WINDOWS\System32\DriverStore\Temp\{50d0ac39-6316-8a49-8483-dd01f49e7e6c}\amd64\WdfCoInstaller01011.dll'.
libwdi:debug [syslog]      flq:                     Copying 'C:\Users\xiaof\AppData\Local\Temp\{ceb54774-5cde-6345-82c8-7032e7241339}\amd64\WinUSBCoInstaller2.dll' to 'C:\WINDOWS\System32\DriverStore\Temp\{50d0ac39-6316-8a49-8483-dd01f49e7e6c}\amd64\WinUSBCoInstaller2.dll'.
libwdi:debug [syslog]      flq:                     Copying 'C:\Users\xiaof\AppData\Local\Temp\{ceb54774-5cde-6345-82c8-7032e7241339}\Lattice_FTUSB_Interface_Cable_(Composite_Parent).cat' to 'C:\WINDOWS\System32\DriverStore\Temp\{50d0ac39-6316-8a49-8483-dd01f49e7e6c}\Lattice_FTUSB_Interface_Cable_(Composite_Parent).cat'.
libwdi:debug [syslog]      flq:                     Copying 'C:\Users\xiaof\AppData\Local\Temp\{ceb54774-5cde-6345-82c8-7032e7241339}\lattice_ftusb_interface_cable_(composite_parent).inf' to 'C:\WINDOWS\System32\DriverStore\Temp\{50d0ac39-6316-8a49-8483-dd01f49e7e6c}\lattice_ftusb_interface_cable_(composite_parent).inf'.
libwdi:debug [syslog]      flq:                {FILE_QUEUE_COMMIT - exit(0x00000000)} 20:09:01.031
libwdi:debug [syslog]      sto:                {DRIVERSTORE IMPORT VALIDATE} 20:09:01.031
libwdi:debug [syslog]      sig:                     Driver package catalog is valid.
libwdi:debug [syslog]      sig:                     {_VERIFY_FILE_SIGNATURE} 20:09:01.063
libwdi:debug [syslog]      sig:                          Key      = lattice_ftusb_interface_cable_(composite_parent).inf
libwdi:debug [syslog]      sig:                          FilePath = C:\WINDOWS\System32\DriverStore\Temp\{50d0ac39-6316-8a49-8483-dd01f49e7e6c}\lattice_ftusb_interface_cable_(composite_parent).inf
libwdi:debug [syslog]      sig:                          Catalog  = C:\WINDOWS\System32\DriverStore\Temp\{50d0ac39-6316-8a49-8483-dd01f49e7e6c}\Lattice_FTUSB_Interface_Cable_(Composite_Parent).cat
libwdi:debug [syslog] !    sig:                          Verifying file against specific (valid) catalog failed.
libwdi:debug [syslog] !    sig:                          Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
libwdi:debug [syslog]      sig:                     {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 20:09:01.063
libwdi:debug [syslog]      sig:                     {_VERIFY_FILE_SIGNATURE} 20:09:01.063
libwdi:debug [syslog]      sig:                          Key      = lattice_ftusb_interface_cable_(composite_parent).inf
libwdi:debug [syslog]      sig:                          FilePath = C:\WINDOWS\System32\DriverStore\Temp\{50d0ac39-6316-8a49-8483-dd01f49e7e6c}\lattice_ftusb_interface_cable_(composite_parent).inf
libwdi:debug [syslog]      sig:                          Catalog  = C:\WINDOWS\System32\DriverStore\Temp\{50d0ac39-6316-8a49-8483-dd01f49e7e6c}\Lattice_FTUSB_Interface_Cable_(Composite_Parent).cat
libwdi:debug [syslog]      sig:                          Success: File is signed in Authenticode(tm) catalog.
libwdi:debug [syslog]      sig:                          Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
libwdi:debug [syslog]      sig:                     {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 20:09:01.078
libwdi:debug [syslog]      sto:                {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 20:09:01.106
libwdi:debug [syslog]      sig:                Signer Score  = 0x0F000000 (Authenticode)
libwdi:debug [syslog]      sig:                Signer Name   = USB\VID_0403&PID_6010 (libwdi autogenerated)
libwdi:debug [syslog]      sto:                {Core Driver Package Import: lattice_ftusb_interface_cable_(composite_parent).inf_amd64_49274b49499329a7} 20:09:01.106
libwdi:debug [syslog]      sto:                     {DRIVERSTORE IMPORT BEGIN} 20:09:01.106
libwdi:debug [syslog]      sto:                     {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 20:09:01.106
libwdi:debug [syslog]      cpy:                     {Copy Directory: C:\WINDOWS\System32\DriverStore\Temp\{50d0ac39-6316-8a49-8483-dd01f49e7e6c}} 20:09:01.106
libwdi:debug [syslog]      cpy:                          Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\lattice_ftusb_interface_cable_(composite_parent).inf_amd64_49274b49499329a7
libwdi:debug [syslog]      cpy:                          {Copy Directory: C:\WINDOWS\System32\DriverStore\Temp\{50d0ac39-6316-8a49-8483-dd01f49e7e6c}\amd64} 20:09:01.113
libwdi:debug [syslog]      cpy:                               Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\lattice_ftusb_interface_cable_(composite_parent).inf_amd64_49274b49499329a7\amd64
libwdi:debug [syslog]      cpy:                          {Copy Directory: exit(0x00000000)} 20:09:01.116
libwdi:debug [syslog]      cpy:                     {Copy Directory: exit(0x00000000)} 20:09:01.117
libwdi:debug [syslog]      idb:                     {Register Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\lattice_ftusb_interface_cable_(composite_parent).inf_amd64_49274b49499329a7\lattice_ftusb_interface_cable_(composite_parent).inf} 20:09:01.117
libwdi:debug [syslog]      idb:                          Created driver package object 'lattice_ftusb_interface_cable_(composite_parent).inf_amd64_49274b49499329a7' in SYSTEM database node.
libwdi:debug [syslog]      idb:                          Created driver INF file object 'oem111.inf' in SYSTEM database node.
libwdi:debug [syslog]      idb:                          Registered driver package 'lattice_ftusb_interface_cable_(composite_parent).inf_amd64_49274b49499329a7' with 'oem111.inf'.
libwdi:debug [syslog]      idb:                     {Register Driver Package: exit(0x00000000)} 20:09:01.117
libwdi:debug [syslog]      idb:                     {Publish Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\lattice_ftusb_interface_cable_(composite_parent).inf_amd64_49274b49499329a7\lattice_ftusb_interface_cable_(composite_parent).inf} 20:09:01.117
libwdi:debug [syslog]      idb:                          Activating driver package 'lattice_ftusb_interface_cable_(composite_parent).inf_amd64_49274b49499329a7'.
libwdi:debug [syslog]      cpy:                          Published 'lattice_ftusb_interface_cable_(composite_parent).inf_amd64_49274b49499329a7\lattice_ftusb_interface_cable_(composite_parent).inf' to 'oem111.inf'.
libwdi:debug [syslog]      idb:                          Indexed 2 device IDs for 'lattice_ftusb_interface_cable_(composite_parent).inf_amd64_49274b49499329a7'.
libwdi:debug [syslog] !    sto:                          Ignoring changes to inbox device class {88bae032-5a81-49f0-bc3d-a4ff138216d6} through ClassInstall32 section.
libwdi:debug [syslog]      sto:                          Flushed driver database node 'SYSTEM'. Time = 0 ms
libwdi:debug [syslog]      idb:                     {Publish Driver Package: exit(0x00000000)} 20:09:01.125
libwdi:debug [syslog]      sto:                     {DRIVERSTORE IMPORT END} 20:09:01.125
libwdi:debug [syslog]      dvi:                          Flushed all driver package files to disk. Time = 0 ms
libwdi:debug [syslog]      sig:                          Installed catalog 'Lattice_FTUSB_Interface_Cable_(Composite_Parent).cat' as 'oem111.cat'.
libwdi:debug [syslog]      sto:                     {DRIVERSTORE IMPORT END: exit(0x00000000)} 20:09:01.142
libwdi:debug [syslog]      sto:                {Core Driver Package Import: exit(0x00000000)} 20:09:01.142
libwdi:debug [syslog]      sto:           {Stage Driver Package: exit(0x00000000)} 20:09:01.144
libwdi:debug [syslog]      sto:      {Setup Import Driver Package - exit (0x00000000)} 20:09:01.186
libwdi:debug [syslog]      dvi:      Searching for hardware ID(s):
libwdi:debug [syslog]      dvi:           usb\vid_0403&pid_6010&rev_0700
libwdi:debug [syslog]      dvi:           usb\vid_0403&pid_6010
libwdi:debug [syslog]      dvi:      Searching for compatible ID(s):
libwdi:debug [syslog]      dvi:           usb\devclass_00&subclass_00&prot_00
libwdi:debug [syslog]      dvi:           usb\devclass_00&subclass_00
libwdi:debug [syslog]      dvi:           usb\devclass_00
libwdi:debug [syslog]      dvi:           usb\composite
libwdi:debug [syslog]      dvi:      Class GUID of device changed to: {88bae032-5a81-49f0-bc3d-a4ff138216d6}.
libwdi:debug [syslog]      ump:      {Plug and Play Service: Device Install for USB\VID_0403&PID_6010\5&586B51A&0&1}
libwdi:debug [syslog]      dvi:           {Core Device Install} 20:09:01.273
libwdi:debug [syslog]      dvi:                {Configure Device - USB\VID_0403&PID_6010\5&586B51A&0&1} 20:09:01.278
libwdi:debug [syslog]      dvi:                     Device Status: 0x0180600a
libwdi:debug [syslog]      dvi:                     Config Flags: 0x00000000
libwdi:debug [syslog]      dvi:                     Parent Device: USB\ROOT_HUB30\4&12c539f&0&0
libwdi:debug [syslog]      sto:                     {Configure Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\lattice_ftusb_interface_cable_(composite_parent).inf_amd64_49274b49499329a7\lattice_ftusb_interface_cable_(composite_parent).inf}
libwdi:debug [syslog]      sto:                          Source Filter  = usb\vid_0403&pid_6010
libwdi:debug [syslog]      inf:                          Class GUID     = {88bae032-5a81-49f0-bc3d-a4ff138216d6}
libwdi:debug [syslog]      inf:                          Class Options  = Configurable BootCritical
libwdi:debug [syslog]      idb:                          {Configure Device Setup Class: {88bae032-5a81-49f0-bc3d-a4ff138216d6}}
libwdi:debug [syslog] !    idb:                               Skipping update of existing inbox class {88bae032-5a81-49f0-bc3d-a4ff138216d6}.
libwdi:debug [syslog]      idb:                          {Configure Device Setup Class: exit(0x00000000)}
libwdi:debug [syslog]      inf:                          {Configure Driver: Lattice FTUSB Interface Cable (Composite Parent)}
libwdi:debug [syslog]      inf:                               Section Name = USB_Install
libwdi:debug [syslog]      inf:                               {Add Service: WinUSB}
libwdi:debug [syslog]      inf:                                    Start Type    = 3
libwdi:debug [syslog]      inf:                                    Service Type  = 1
libwdi:debug [syslog]      inf:                                    Error Control = 1
libwdi:debug [syslog]      inf:                                    Image Path    = \SystemRoot\System32\drivers\WinUSB.sys
libwdi:debug [syslog]      inf:                                    Display Name  = WinUSB - Kernel Driver 06/02/2012 6.1.7600.16385
libwdi:debug [syslog]      inf:                                    Updated service 'WinUSB'.
libwdi:debug [syslog]      inf:                               {Add Service: exit(0x00000000)}
libwdi:debug [syslog]      inf:                               Hardware Id  = USB\VID_0403&PID_6010
libwdi:debug [syslog]      inf:                               {Configure Driver Configuration: USB_Install}
libwdi:debug [syslog]      inf:                                    Service Name  = WinUSB
libwdi:debug [syslog]      inf:                                    Included INFs = winusb.inf
libwdi:debug [syslog]      inf:                                    Config Flags  = 0x00000000
libwdi:debug [syslog]      inf:                               {Configure Driver Configuration: exit(0x00000000)}
libwdi:debug [syslog]      inf:                          {Configure Driver: exit(0x00000000)}
libwdi:debug [syslog]      flq:                          {FILE_QUEUE_COMMIT} 20:09:01.298
libwdi:debug [syslog]      flq:                               Hardlinking 'C:\WINDOWS\System32\DriverStore\FileRepository\winusb.inf_amd64_d1861060a4b1a6d4\winusb.sys' to 'C:\WINDOWS\System32\drivers\winusb.sys'.
libwdi:debug [syslog]      cpy:                               Existing file 'C:\WINDOWS\System32\drivers\winusb.sys' remains unchanged.
libwdi:debug [syslog]      flq:                               Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\lattice_ftusb_interface_cable_(composite_parent).inf_amd64_49274b49499329a7\amd64\WinUSBCoInstaller2.dll' to 'C:\WINDOWS\System32\WinUSBCoInstaller2.dll'.
libwdi:debug [syslog]      cpy:                               Existing file 'C:\WINDOWS\System32\WinUSBCoInstaller2.dll' remains unchanged.
libwdi:debug [syslog]      flq:                               Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\lattice_ftusb_interface_cable_(composite_parent).inf_amd64_49274b49499329a7\amd64\WdfCoInstaller01011.dll' to 'C:\WINDOWS\System32\WdfCoInstaller01011.dll'.
libwdi:debug [syslog]      cpy:                               Existing file 'C:\WINDOWS\System32\WdfCoInstaller01011.dll' remains unchanged.
libwdi:debug [syslog]      flq:                          {FILE_QUEUE_COMMIT - exit(0x00000000)} 20:09:01.333
libwdi:debug [syslog]      sto:                     {Configure Driver Package: exit(0x00000000)}
libwdi:debug [syslog]      dvi:                     Install Device: Configuring device. 20:09:01.333
libwdi:debug [syslog]      dvi:                          Configuration: oem111.inf:usb\vid_0403&pid_6010,USB_Install
libwdi:debug [syslog]      dvi:                     Install Device: Configuring device completed. 20:09:01.348
libwdi:debug [syslog]      dvi:                     Device Status: 0x0180600a
libwdi:debug [syslog]      dvi:                     Install Device: Removing device 'USB\VID_0403&PID_6010\5&586B51A&0&1' and sub-tree. 20:09:01.350
libwdi:debug [syslog]      dvi:                     Install Device: Removing device sub-tree completed. 20:09:01.462
libwdi:debug [syslog]      dvi:                     Install Device: Restarting device. 20:09:01.463
libwdi:debug [syslog]      dvi:                     Install Device: Restarting device completed. 20:09:01.659
libwdi:debug [syslog]      dvi:                {Configure Device - exit(0x00000000)} 20:09:01.660
libwdi:debug [syslog]      dvi:           {Core Device Install - exit(0x00000000)} 20:09:01.662
libwdi:debug [syslog]      ump:      {Plug and Play Service: Device Install exit(00000000)}
libwdi:debug [syslog]      ndv: {Update Device Driver - exit(00000000)}
libwdi:debug [syslog]      ndv: {Install Related Drivers} 20:09:01.684
libwdi:debug [syslog]      ndv: {Install Related Drivers: exit(0x00000000)} 20:09:01.689
libwdi:debug [process_message] Switching timeout back to finite
libwdi:debug [installer process] driver update completed
libwdi:debug [installer process] re-enumerating driver node USB\VID_0403&PID_6010\5&586B51A&0&1...
libwdi:debug [installer process] re-enumeration succeeded...
libwdi:debug [process_message] Installer process completed
libwdi:debug [installer process] successfully restored the system restore point creation setting
Driver Installation: SUCCESS
8 devices found.
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0403&PID_6010&REV_0700
libwdi:debug [wdi_create_list] Compatible ID: USB\DevClass_00&SubClass_00&Prot_00
libwdi:debug [wdi_create_list] Driver version: 6.1.7600.16385
libwdi:debug [wdi_create_list] WinUSB USB device (0): USB\VID_0403&PID_6010\5&586B51A&0&1
libwdi:debug [wdi_create_list] Device description: 'Lattice FTUSB Interface Cable'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_8087&PID_0026&REV_0002
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_E0&SubClass_01&Prot_01
libwdi:debug [wdi_create_list] Driver version: 22.80.0.4
libwdi:debug [wdi_create_list] BTHUSB USB device (1): USB\VID_8087&PID_0026\5&586B51A&0&10
libwdi:debug [wdi_create_list] Device description: 'Intel(R) Wireless Bluetooth(R)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_04F2&PID_B6DD&REV_2710
libwdi:debug [wdi_create_list] Compatible ID: USB\DevClass_00&SubClass_00&Prot_00
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] usbccgp USB device (2): USB\VID_04F2&PID_B6DD\0001
libwdi:debug [wdi_create_list] Device description: 'HD User Facing (Composite Parent)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_1C7A&PID_0575&REV_1072
libwdi:debug [wdi_create_list] Compatible ID: USB\MS_COMP_WINUSB
libwdi:debug [wdi_create_list] Driver version: 3.7.1.1
libwdi:debug [wdi_create_list] WUDFRd USB device (3): USB\VID_1C7A&PID_0575\077E2F9A
libwdi:debug [wdi_create_list] Device description: 'EgisTec EH575'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_25A7&PID_FA23&REV_0241&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_01
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] HidUsb USB device (4): USB\VID_25A7&PID_FA23&MI_00\6&2E1AA5FE&0&0000
libwdi:debug [wdi_create_list] Device description: '2.4G Receiver (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_25A7&PID_FA23&REV_0241
libwdi:debug [wdi_create_list] Compatible ID: USB\DevClass_00&SubClass_00&Prot_00
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] usbccgp USB device (5): USB\VID_25A7&PID_FA23\5&586B51A&0&3
libwdi:debug [wdi_create_list] Device description: '2.4G Receiver (Composite Parent)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_25A7&PID_FA23&REV_0241&MI_01
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_02
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.1
libwdi:debug [wdi_create_list] HidUsb USB device (6): USB\VID_25A7&PID_FA23&MI_01\6&2E1AA5FE&0&0001
libwdi:debug [wdi_create_list] Device description: '2.4G Receiver (Interface 1)'
libwdi:debug [wdi_create_list] Hardware ID: USB\ROOT_HUB30&VID8086&PIDA0ED&REV0020
libwdi:debug [wdi_create_list] Compatible ID: 
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.65
libwdi:debug [wdi_create_list] USBHUB3 USB device (7): USB\ROOT_HUB30\4&12C539F&0&0
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_04F2&PID_B6DD&REV_2710&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_0e&SubClass_03&Prot_00
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.176
libwdi:debug [wdi_create_list] usbvideo USB device (8): USB\VID_04F2&PID_B6DD&MI_00\6&2F8D90E&0&0000
libwdi:debug [wdi_create_list] Device description: 'HD User Facing (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\ROOT_HUB30&VID8086&PID9A13&REV0001
libwdi:debug [wdi_create_list] Compatible ID: 
libwdi:debug [wdi_create_list] Driver version: 10.0.22000.65
libwdi:debug [wdi_create_list] USBHUB3 USB device (9): USB\ROOT_HUB30\4&1A63DC7C&0&0

Oct 06 '21 12:10 mcuee

Yup, I am confirming the same results with the official release.

It looks like Microsoft may have been using the Insider builds to test features, that they didn't carry into the release, though I'm a bit worried they might not try to bring them up again in a future feature release.

Oct 06 '21 15:10 pbatard

Looks like this test was not removed in the insider builds as, on the latest build (22478), I get an error about the certificate being not trusted

Edit: With further testing, it looks like disabling the secure boot is enough to allow installation

Oct 17 '21 14:10 KodWhat

@WIGASTY, either you're trying to use libwdi/Zadig on ARM64, which is not supported, or you are trying to piggyback on an unrelated issue (and also you have truncated the log so we can't even tell what version of Zadig and the exact version of Windows you are using, including the build number).

At any rate, I have deleted your comment, because it is out of scope.

Nov 01 '21 17:11 pbatard

https://github.com/edk2-porting/edk2-sdm845 I have a Xiaomi-Mi8(dipper) old 845 device and run Win11 arm64 with no issues. I want use usb2ttl ( ch341, pl2302, ft232, etc..) to connect mcu, and I also play rtl-sdr. These old cell phone really cheap and maybe you have one or more :-)

Nov 10 '21 15:11 radiolee

Ref:

https://github.com/mcuee/libusb-win32/issues/29
https://github.com/mcuee/libusbk/issues/35

Nov 17 '21 00:11 mcuee

Sorry but we need some testers for Windows on ARM for the upcoming libusb-1.0.25 release. If would be greatly appreciated someone can help to test libusb-1.0.25rc1 and report the success or failure here.

https://github.com/libusb/libusb/issues/1046

Jan 22 '22 09:01 mcuee

libwdi libwdi copied to clipboard

Windows 10 on ARM64 support

libwdi
libwdi copied to clipboard