Microsoft Locked Out VeraCrypt, WireGuard, and Windscribe from Pushing Windows Updates

Microsoft’s relationship with the open source community has always been a tapestry of contrasts, woven with threads of innovation and tension. The tech giant has birthed notable projects like VSCode, TypeScript, and .NET, and its acquisition of GitHub positioned it at the helm of the largest code hosting platform globally. However, this narrative is complicated by Microsoft’s default telemetry integration in Windows and its assertive promotion of Copilot AI across its software suite. These actions have prompted a segment of developers to explore open source alternatives more fervently.

What’s happening?

Recently, a wave of developer account suspensions has surfaced, creating new challenges for open source developers. Microsoft implemented a mandatory account verification process for all partners in the Windows Hardware Program who had not completed verification since April 2024. This requirement, which took effect on October 16, 2025, mandated that partners verify their identities using a government-issued ID that matched the name of the primary contact in the Partner Center. Failing to meet this deadline or passing verification resulted in account suspension, barring further submissions.

This situation is particularly critical because signing Windows kernel drivers requires one of these accounts. Without it, developers are unable to push updates for driver-signed Windows applications, leading to Windows flagging unsigned drivers and preventing them from loading at the kernel level. Three prominent open source projects—VeraCrypt, WireGuard, and Windscribe—experienced this disruption firsthand when their developer accounts were suspended, halting their ability to deliver updates on Windows.

Mounir Idrassi, the developer behind VeraCrypt, was the first to publicly address the issue. He shared his experience on a SourceForge forum, revealing that Microsoft had terminated his account without prior notice or explanation, leaving him with no option to appeal. His attempts to contact Microsoft through official channels yielded only automated responses. This suspension not only impacted his work on VeraCrypt but also affected his day job.

WireGuard’s creator, Jason Donenfeld, encountered a similar predicament a few weeks later when he attempted to certify a new WireGuard kernel driver for Windows, only to find his account access restricted. Although he eventually discovered a Microsoft appeals process, it came with a daunting 60-day response window.

Windscribe’s situation proved to be the most convoluted. The company reported that it had maintained a verified Partner Center account for over eight years and spent more than a month trying to resolve the issue before going public. Compounding their frustration, once an account is suspended, the Partner Center prevents users from opening a support ticket directly.

What now?

This series of events eventually caught Microsoft’s attention, prompting Scott Hanselman, VP and Member of Technical Staff at Microsoft and GitHub, to intervene. He took to X to announce that the accounts would be reinstated, referencing the October 2025 blog post and asserting that the company had been communicating with affected partners since then. Scott confirmed that he had personally reached out to both Mounir and Jason to expedite the unblocking of their accounts, and that corrective measures were already underway.

Despite these efforts, the situation raises significant concerns. The lack of immediate recourse for developers of critical security software can erode trust and goodwill. However, it remains to be seen how much this incident will impact Microsoft, a titan with an unwavering grip on the operating system market.

Suggested Read 📖: Proton Workspace and Meet launched as alternatives to Big Tech offerings