Hardware drivers not certified by the Microsoft lab will not install. No longer can folks dismiss the nag screen to run some bespoke piece of hardware.
Again, that's been the case since Windows 7. You have to go out of your way to boot the system in "Test Mode" to install an unsigned driver. Either that, or use Zadig to self-sign the driver. (Maybe they're no longer allowing that?)
Signatures were enforced only for 64-bit drivers in Windows 7, but Windows 10 enforces them for all drivers.
There is nothing in that article saying anything about any upcoming requirements. Also it is written by a ChatGPT bot account, so it would be an invalid source even if it did.
The only update even mentioned in that article is "Windows 10, version 1607 (the Anniversary Update released in August 2016)". In case you haven't noticed, that happened 9 years ago...
If at some point I can recall the interview from earlier this year, than I will post a link. Otherwise, we will both have to wait and see. Best regards. =3
What is "it" that might break something? There is nothing that is going to happen. The AI-slop you linked doesn't mention anything that is going to happen. It's just a summary of changes that have happened in the past and a list of pros and cons of the driver signing requirement from more than a decade ago. There is nothing to "wait and see" for.
It goes well beyond strict USB-C port WHCP compliance rules if I recall correctly, and is not about just banning old WinRing 0 nuisance drivers ( https://www.youtube.com/watch?v=H_O5JtBqODA ).
I can't put any significant time into a proper search right now, but if I recall the interview I'll post a URI. Have a great day. =3
Again, that's been the case since Windows 7. You have to go out of your way to boot the system in "Test Mode" to install an unsigned driver. Either that, or use Zadig to self-sign the driver. (Maybe they're no longer allowing that?)
Signatures were enforced only for 64-bit drivers in Windows 7, but Windows 10 enforces them for all drivers.