Microsoft BANNED WireGuard, VeraCrypt & Windscribe With Zero Warning
Why It Matters
The shutdown jeopardizes critical encryption and VPN updates for millions, exposing users to security risks and highlighting the dangers of platform‑owner control over essential privacy tools.
Key Takeaways
- •Microsoft suspended driver‑signing accounts for WireGuard, VeraCrypt, Windscribe.
- •Developers received no notice, no explanation, and no recourse.
- •WireGuard underpins most VPN services; updates now blocked on Windows.
- •Veracrypt’s bootloader signature may expire, risking unbootable systems after July 2026.
- •Microsoft’s ecosystem lock‑in raises broader digital‑rights and security concerns.
Summary
Microsoft abruptly suspended the Windows Hardware Program accounts of three high‑profile open‑source security projects—WireGuard, VeraCrypt and Windscribe—without any prior notice or explanation. The developers discovered their driver‑signing privileges revoked after a mandatory re‑verification window closed silently, leaving them unable to push critical updates to Windows users. The Windows Hardware Program requires developers to upload government IDs to maintain signing rights. When the verification period ended, accounts that had not submitted documentation were automatically suspended, and Microsoft provided no direct communication. As a result, WireGuard, the VPN protocol powering services like NordVPN and ProtonVPN, cannot release patches; VeraCrypt cannot renew its bootloader certificate, threatening system bootability after July 2026; and Windscribe remains locked out after a month‑long appeal. WireGuard’s lead developer warned that any critical vulnerability would leave millions exposed, while VeraCrypt’s maintainer warned of a “death sentence” if the signing issue isn’t resolved before the certificate expires. Windscribe’s team publicly tweeted about the month‑long stalemate, highlighting Microsoft’s lack of support. These statements underscore the real‑world impact on users relying on encryption and VPN tools. The episode illustrates how platform gatekeeping can undermine the very security tools it claims to protect, exposing users to potential data breaches and system failures. It also raises broader digital‑rights questions about ecosystem lock‑in, prompting calls for alternative signing mechanisms and greater transparency from dominant OS vendors.
Comments
Want to join the conversation?
Loading comments...