libwdi
libwdi copied to clipboard
pbatard
`drvinst` hung in the exit stage
Windows 10. Bit of a mess here…
Installing libust-win32 on 05C6:900E results in drvinst being hung in the exit stage. Impossible to kill.
Naturally, the GUI times out, but installer_x64 never quits. Possible to kill.
The main GUI becomes disabled, while still visible — can't even save the log. But using external window manipulation I enable it back to be able to interact with it.
This basically breaks the session with Device Manager and its dependencies being hung and I have to reboot.
Can't tell if the driver is installed fully or partially.
Zadig.log
After you reboot, did you see your device in Windows Device Manager with the WinUSB driver installed?
Oh, BTW, when I said "have to reboot" — I meant hard-reset, because the OS session becomes very broken and won't terminate itself orderly anymore.
But yes, the driver does get installed and assigned.
Interesting.
Can you try libusbK-inf-Wizard from libusbK project? It was based on an older version of libwdi. https://github.com/mcuee/libusbk/releases/tag/V3.1.0.0 (download libusbK-3.1.0.0-setup.exe and install).
I'm sorry, but I'd prefer not to at this time. I have given up on the project I needed Zadig for and have shelved it all away. If the log and my observations aren't enough, then perhaps more meticulous debug logging would be a good suggestion for future cases.
Since nobody else is reporting this issue, and it looks environmental, I will close it, as there isn't much more we can do.
