Microsoft terminated accounts tied to VeraCrypt, WireGuard, and Windscribe — developers push back

Abstract fractured shield with generic security icons representing VeraCrypt, WireGuard, and Windscribe losing access.
Microsoft terminated developer accounts tied to VeraCrypt, WireGuard, and Windscribe, raising concerns among security and open‑source communities. (Image credit: Future | Edited with Gemini)

Several well‑known security and privacy developers say Microsoft abruptly terminated their developer accounts, cutting off access to essential publishing and verification tools.

The affected projects include VeraCrypt, WireGuard, and Windscribe — names that Windows users rely on for encryption, networking, and privacy. Microsoft has acknowledged the actions but has not fully explained why these trusted developers were swept up in its enforcement process. The situation highlights ongoing tension between automated security controls and the realities of open‑source development. It also raises questions about how Microsoft plans to prevent similar disruptions in the future.

Article continues below

WindScribe was in the same situation, indicating that their Microsoft developer account was also suspended. "We've been trying to resolve this for over a month, and getting nowhere. Support is non-existent," Windscribe added. "Anyone know a human with a brain that still works at Microsoft and can help?"

But thanks to the social backlash — and, surprisingly, Epic Games CEO and founder Tim Sweeney — the issue was flagged to Microsoft's EVP for Windows and Devices, Pavan Davuluri, who said the company was working to resolve the issue. Davuluri claimed that Microsoft had also reached out VeraCrypt and WireGuard, promising to have their suspended accounts reinstated.

Ultimately, it appears Microsoft didn’t intentionally block any partner accounts. Instead, the company introduced mandatory account verification in the Windows Hardware Program for those who hadn’t completed the process since April 2024. The requirement took effect on October 16, 2025, giving partners 30 days to verify their identity with a government-issued ID, as Davuluri pointed out.

We worked hard to make sure partners understood this was coming, from emails, banners, reminders. And we know that sometimes things still get missed. We're taking this as an opportunity to review how we communicate changes like this and make sure we're doing it better.

Microsoft EVP for WIndows + Devices, Pavan Davuluri

Scott Hanselman, VP and member of technical staff at Microsoft, addressed the issue on X, indicating that, "Hey, I love dumping on my company as much as the next guy, because Microsoft does some dumb stuff, but sometimes it's just check emails and verify your accounts."

"Not every 'WTF micro$oft' moment is a slam dunk," Hanselman added. He indicated that not everything is a conspiracy, and sometimes it could be literally paperwork. Either way, Microsoft should've already resolved the suspended developer accounts by now, or it'll be close to resolved.

Should Microsoft change how it verifies and enforces rules for open‑source developers? Share your thoughts in the comments.


Click to join us on r/WindowsCentral

Join us on Reddit at r/WindowsCentral to share your insights and discuss our latest news, reviews, and more.


Kevin Okemwa
Contributor

Kevin Okemwa is a seasoned tech journalist based in Nairobi, Kenya with lots of experience covering the latest trends and developments in the industry at Windows Central. With a passion for innovation and a keen eye for detail, he has written for leading publications such as OnMSFT, MakeUseOf, and Windows Report, providing insightful analysis and breaking news on everything revolving around the Microsoft ecosystem. While AFK and not busy following the ever-emerging trends in tech, you can find him exploring the world or listening to music.

You must confirm your public display name before commenting

Please logout and then login again, you will then be prompted to enter your display name.