Certificate error on Windows 11

[synapp009]

When I tried to install the dshidmini.inf I got following error on Windows 11:

dshidmini.inf: Failed to add driver to the system. Error 0x800B0110: The certificate is not valid for the requested usage.

[nefarius]

Have you recently applied a Windows update? We had another user on the Discord where a recent update ruined the included root certificate chains. This is a Microsoft issue, nothing I can do about. The certificate on the driver is perfectly fine and works throughout all Windows 10 builds as expected.

[synapp009]

It happens with the new Windows 11 build 22454.
So it might only be somemthing to worry in the future.
Thanks for your fast response.

[nefarius]

I don't really consider Windows 11 "stable" and "mainstream" yet, Microsoft is constantly changing the rules and break things in a subtle way, independent developers can't keep up with this nonsense. I will keep it on my radar but for now I consider DsHidMini stable and Windows 11 beta, not the other way around 😛

Cheers

[nefarius]

Alright, it has been confirmed this is an issue with a certain Windows 11 update. Unfortunately we haven't taken note of which specific one, if someone knows, please chime in as it seems a folluw-up update has fixed the issue.

Cheers

[nefarius]

Got notice from a user that it is back in the currently most recent build 🤣

Maybe Microsoft shouldn't have fired the entire QA department... Always nice to see OS basics break randomly.

[Jjagg]

I worked around this by temporarily disabling driver signature checking.

I had a working installation of the driver before the Windows update that broke this, so I think the update might've even removed/disabled the driver.

[nefarius]

I'd love if for a change Microsoft would swiftly fix core components they casually break all the time though 🤣

[chrisdlees]

I think @Jjagg is right, the updates are actually going out of their way to break the bluetooth driver. Might be Win11's BTH radio management, because mine has been behaving quite bizarrely. The past month, I've seen 5 updates cause my bluetooth connectivity to magically disable/re-enable.
Right now, my wireless is working, but I've had the latest update standing by for over a week. I'm avoiding it at all costs, even going so far as to switch to working in a WSL2 dev environment or RDPing into an AWS EC2 instance, instead of rebooting into my normal linux installation... lol

[nefarius]

Isn't that exactly what one wants for a productive machine? Stuff randomly breaking? 🤣 I'll stay on 10 for as long as possible, public Beta products aren't my thing 😉

[nefarius]

There's news on this topic, apparently Windows 11 will start to mandate Microsoft signed UMDF drivers as well, so future releases will be made "Windows 11-ready" accordingly.