Microsoft just locked three of the most important open source security projects—WireGuard, VeraCrypt, and Windscribe—out of their Windows developer accounts with zero warning, zero explanation, and basically zero recourse. In this video I break down what happened: Microsoft’s Windows Hardware Program requires driver signing for a lot of security software, and they ran a mandatory re-verification process that required government ID uploads. The infuriating part is the verification window quietly closed, accounts were suspended, and multiple developers say they never got notified—no email, no spam, nothing. The practical fallout is not theoretical. WireGuard’s developer pointed out that if a critical vulnerability ever needed a Windows-side patch, they’d be unable to ship it—leaving users exposed. VeraCrypt is even more alarming: if you’re using full system encryption, you may not be able to boot after July 2026 because Microsoft is revoking the certificate authority used to sign the VeraCrypt bootloader, and without account access the developer can’t apply new signatures. My bigger takeaway is this: this isn’t just a support failure, it’s ecosystem gatekeeping failing in real time. Big Tech sells lock-in as “security,” but when the gatekeeper breaks, it can break your security model too. This is a digital rights issue, and we shouldn’t accept a world where critical security tools are one bureaucratic mistake away from being cut off from users.