Microsoft responds after WireGuard, Windscribe, and VeraCrypt accounts get locked

Microsoft had locked the developer accounts used by the creators of WireGuard, VeraCrypt, and Windscribe. That prevented them from signing drivers and releasing updates for Windows.

But there is some movement now. Microsoft VP Scott Hanselman stepped in on X and said the company has been emailing people about this since October 2025. He called it basically paperwork and wrote that fixes are happening.

He followed up by adding that he personally spoke to both WireGuard creator Jason Donenfeld and VeraCrypt developer Mounir Idrassi. He also noted, “All being fixed as we speak.”

WireGuard creator Jason Donenfeld told TechCrunch he discovered the lockout when he tried to submit a major update. This was going to be the first big update for WireGuard on Windows in almost four years. The account suddenly showed as access restricted.

Donenfeld said Microsoft never sent him any warning. He checked every inbox, spam folder, and mail log. Nothing. Even after he completed the identity verification process and a third-party checker said he was verified, his account stayed locked.

He had spent the past few weeks modernizing WireGuard’s Windows code and was ready to ship it. WireGuard is open source VPN software used around the world. Its code powers many popular services, including Proton and Tailscale, because it is simple and considered very secure.

Donenfeld pointed out the risk. If there were a critical vulnerability right now, users would be totally exposed.

The same thing happened to VeraCrypt developer Mounir Idrassi. VeraCrypt is used by hundreds of thousands of people to encrypt files and whole operating systems. Being locked out means he cannot update the software before a key certificate expires, which could stop some users from booting their computers.

Windscribe also got hit. The VPN company said it had a verified account for over eight years. They have been trying to fix this for over a month with no real help from support.

This comes from a Microsoft requirement in the Windows Hardware Program. Developers must verify their identity with a government ID to keep signing drivers. From what is evident, the verification deadline passed, and accounts that didn’t complete it got suspended. So it’s not just exclusive to the developers mentioned here.

For days, the developers heard nothing from Microsoft. Hanselman’s public replies are the first real sign the company is paying attention.

In a more recent post, Hanselman wrote, “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. I’ve emailed VeraCrypt personally and we’ll get him unblocked. I’ve already talked to Jason at WireGuard. Not everything is a conspiracy sometimes it’s literally paperwork.”

It’s unclear how long it’ll take for the suspensions to lift, but it’ll likely be resolved sooner rather than later. We’ll keep an eye out for any further developments and will update the article accordingly.

Featured image generated with AI

We stand out from the tech-media crowd because we break news stories; we mainly bring you stuff that you won’t find anywhere in the mainstream tech media. Our stories have been picked up by some of the world’s most popular websites and media outlets—more info is available here.