windows-driver-docs

I thought ChangeDisplaySettingsEx and EnumDisplaySettings are superseded by SetDisplayConfig and QueryDisplayConfig, respectively? https://github.com/MicrosoftDocs/windows-driver-docs/blob/st... calls ChangeDisplaySettingsEx "legacy API". From my experience, changing topology using SetDisplayConfig is straightforward.

The biggest thing with digital signatures is that getting one trusted by Windows means entertaining a racket enabled by Microsoft. There are two types of code signing certificates: regular, and EV. With regular certificates, all you get is effectively a way to carry your antivirus-based reputation with you as you continue to sign new binaries with it. At first sight, Windows will still throw up smartscreen warnings about it being potentially dangerous, until it's seen the certificate enough to trust it for new binaries. With EV certificates, everything is smooth sailing - only if actual malware is reported does your certificate get slammed by antivirus reputation, otherwise you can sign anything and it'll instantly bypass all AV software and Windows smartscreen prompts. The issue with getting either of these is that absolute cheapest one

In addition, Windows 10 requires that Microsoft approve and sign each kernel driver that's loaded, actually. https://github.com/MicrosoftDocs/windows-driver-docs/blob/HE...