USB SuperSpeed error code 43

Caledon Ken said:

When you say they would not install did you go down the path of browsing my computer for drivers, then let me pick from a list of drivers on my computer.

No, I did not try that install method. I can do it, though. I have the original Win 7 drivers on the ASRock DVD + I can download Win 7 drivers from Intel - actually, I think already have them.

Will try this afternoon (Wed).

BTW, regarding "... signed by Win-RAID CA." I am not fully understanding "Import of the Certificate to your personal system." Where is the certificate? A separate file or part of a driver package?

Thanks,
Terry

PolarNettles said:

I came across a potential workaround, if the issue is indeed with the BOS descriptor as I suspect. From Why does my USB device work on Windows 8.0 but fail on Windows 8.1 with code 43? Microsoft Windows USB Core Team Blog

1. Run regedit
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags\
3. Create a new key called "174C30740100" (taken from your USBTree logs)
4. Create a DWORD called "SkipBOSDescriptorQuery" and set it to 1.

Attachment 188884

I did it but no success. Good try, though. :) I'm going to try the Win 7 driver "have disc" method this afternoon.

Thanks,
Terry

Caledon Ken said:

When you say they would not install did you go down the path of browsing my computer for drivers, then let me pick from a list of drivers on my computer.

I tried this method but no install. Seems that Windows "knows" the driver is for another system.

Caledon Ken said:

Hmmm, I'm stumped.

I've installed Win 7 drivers on my Windows 10 machines but they must be compatible.

Hopefully another member will have answer.

Fooling around with the drivers inspired (?) me to try Fernando's modded driver. So I pretty much followed the instructions and BOOM the drivers installed and the Dev Mgr USB error is gone!!!!

Fernando's drivers did away with the "Generic SuperSpeed USB Hub" item in Dev Mgr. There are some other minor changes under USB controllers but everything is working normally. :)

I include a couple snips for everyone's viewing pleasure.

Thanks to everyone for sticking with me on this puzzle. Bottom line - Win 10 caused the problem.

This snip is the one I intended to include in the earlier message.

EdTittel said:

For modded, reliable and up-to-date USB drivers, there's no better source than Fernando/Dieter's excellent Win-RAID.com website. Here's the USB 3.0/3.1 Drivers (original and modded) page. Make an image backup, then try them out. If you don't like what they do for your system just restore the pre-update image backup.
HTH,

--Ed--

Ed, these drivers fixed it. I should have done this a week ago. Sorry for being a dumb-ass.

Caledon Ken said:

Save those instructions, you will need them in the Fall, LOL

Win 10 fixed me up with a couple downloads the last two days or so. Caused the trouble triangle under USB Controllers again. Reinstalled the Win-RAID drivers again. Problem solved.

Ha, ha.