[Windows 10] Controller experiences device timeout (Code 10)

[AFriendlyIrin]

ETA: Literally as soon as I posted this, Nefarius HID Devices reappeared. Investigating the controller gets the following error message:

This device cannot start. (Code 10)
{Device Timeout}
The specified I/O operation on %hs was not completed before the time-out period expired.

Bug description

Everything was working perfectly, but all of a sudden my controller can no longer be detected by Device Manager or DSHMC, whether by USB or wireless. The Nefarius HID Devices category in Device Manager has completely disappeared seems erratic and displays the controller with a warning sign; investigating produces the above error. I can still find the drivers with Driver Store Explorer, and attempting to remove dshidmini.inf produces an error stating that it is still in use. Windows can recognize the controller in the device list, but displays it with a "Driver Error" message. I attempted to delete and reinstall the drivers as well as restart my computer several times, but the problem persists.

The Bluetooth drivers are also installed.

The controller LED is a solid light at position 4. Plugging/unplugging through USB doesn't reset this.

Steps to reproduce

I am not certain how to reproduce the issue, as I can't get DsHidMini working again to test it.

Screenshots

Machine info

CPU-Architecture: x64
Windows version: Windows 10.0.19045
Software/driver version(s): 2.2.282

Additional information

My controller is a legitimate PS3 Sixaxis controller.

I had SCP Toolkit installed, but removed it with Legacinator. I don't have any of the other drivers listed as compatibility issues.

[nefarius]

This error is covered in the FAQ.

[AFriendlyIrin]

It was working just a few minutes earlier, though, and I've been using this controller for years without issue. How did the hardware suddenly break?

[nefarius]

It was working just a few minutes earlier, though, and I've been using this controller for years without issue. How did the hardware suddenly break?

IDK, I never could reproduce this myself, I have no solution for you.

[nefarius]

We could add some retry logic and see if that fixes it, I have no other solution or workaround to think of as of now. I can do that whenever I have time again for this project, so mid 2025 or so 😉

[AFriendlyIrin]

I switched back to ScpToolkit and it works fine again, so it's definitely a software problem.

You might want to revise that bit in your FAQ about how DsHidMini is so much better than your old decrepit version.

[nefarius]

I switched back to ScpToolkit and it works fine again, so it's definitely a software problem.

You might want to revise that bit in your FAQ about how DsHidMini is so much better than your old decrepit version.

Or, how about, people start contributing fixes and solutions instead of waiting for me to do all the work? 😉

Figure out what the issue is, contribute a PR, and you'll get a new version in no time. Until then; it is what it is.

[nefarius]

You might want to revise that bit in your FAQ about how DsHidMini is so much better than your old decrepit version.

As I said; I do not have any issues. Come up with the solution, the code is open, expecting a fix next week! It's easy, it's just software, after all!

[nefarius]

I switched back to ScpToolkit and it works fine again

NVM then, glad to see it resolved! ♥