This is apparently being done to improve kernel security and reliability. It could be a PR disaster depending how it is rolled out...
People can blame things like the old generic PC-case-bling LED driver CVE people and even its original author lost patience with years ago... lol =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.
https://windowsforum.com/threads/windows-driver-signing-bala...
We won't know the actual collateral damage till the update is released. =)
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...
https://youtu.be/ETqvtZomqV8?si=-gd34UzaLNDNNDc7&t=50
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
That's been the case since Windows 7 for 64-bit drivers, hasn't it? What's changing with 11?