What <i>really</i> pisses me off is code signing for drivers. To install an unsigned driver in 64-bit Windows 10, you need to reboot your computer into a special menu that can only be navigated with a USB keyboard (which I have to lug out of the closet, since I normally use Bluetooth). That in itself wouldn't be so bad, except the setting persists <i>only until the next reboot!</i> †<p>This is all in stark contrast to macOS's System Integrity Protection, which I can turn off once to never be bothered again.<p>I understand why Microsoft would enforce higher standards on drivers which can touch the kernel. But, the same fundamental problem applies: it isn't reasonable for non-profit, open source developers—many of whom <i>I</i> consider perfectly trustworthy—to pay hundreds of dollars for a certificate! Let me make the final decision about who I trust. It's my machine—I even built it myself!<p>The primary place I run into this problem is with drivers to support weird video game controllers.<p>---<p>† You can enable a "testsigning" mode via the command line which persists across reboots, but this only seems to work for certain drivers. If anyone can explain why it <i>sometimes</i> works, I'd appreciate it, as my research has never turned up anything.