Install grinds entire system to a halt about usbdk HOT 7 OPEN

@anthonyjr2
First recommendation is to try 1.00.21, the flow that on some devices may cause DRIVER_POWER_STATE_FAILURE was introduced in 1.00.22

from usbdk.

Ah okay, I didn't see an issue that described the problem on 1.00.22 so didn't try the earlier versions. If I end up trying again I will attempt 1.00.21 but it was such a headache the last time I am going to wait a while, lol. Is there any plan to release a new version fixing the regression?

from usbdk.

@anthonyjr2

• Does 1.00.22 cause any issue when said specific device is not connected? If so, I wouldn't recommend also 1.00.21.
• Possible problem with this specific device is that it is constantly in low power mode and the UsbDk can't attach to it. 1.0.22 tries to move the device to working mode but it appears that on some devices this causes problems. Possible alternative is manually turn off the 'USB selective suspend', on laptops this increases power consumption
• At the moment we do not have plans for next release until we have resources for that
• The project is open-source, can be built by anyone with Visual studio and WDK, some simple intervention in build scripts might be required, packaging into MSI is not mandatory, the problematic commit is this one

from usbdk.

It did not seem to be device-dependent. Simply having UsbDk installed would cause the slowdown, even after unplugging all USB devices completely. Every USB port would have issues as well, for example if I tried to plug something in, it wouldn't be recognized at all until I did a reboot. Which wasn't a very good fix because half the time the system would refuse to start with the BSOD I mentioned. The computer would also refuse to reboot from within Windows. It would hang for 5-10 minutes on the "Restarting" screen then crash with the same BSOD.

I don't plan to use it again for the time being but just figured it would be helpful to put this issue out there.

from usbdk.

@anthonyjr2 UsbDk is not expected to make any negative impact at all until really used for device redirection or hiding. Just as an example, I have it installed for many years on main development machines over several Win10 upgrages, currently with 19041. If you have some %windir%\memory.dmp from 1.0.21 of attempt to reboot, it would be good to zip it and share with us somehow for study.

from usbdk.