Microsoft locks WireGuard dev account, blocks critical updates

Microsoft locked the WireGuard developer's account without notice, blocking software updates to Windows users

This marks the second major developer in recent weeks to face unexplained account lockouts from Microsoft's platform

The incident exposes critical vulnerabilities in Microsoft's developer account management and raises supply chain security concerns

Open-source maintainers warn these lockouts create dangerous gaps in security patch distribution

The developer behind WireGuard , one of the most widely used open-source VPN protocols, can't push critical security updates to Windows users after Microsoft abruptly locked his developer account without warning. It's the second high-profile case in recent weeks of Microsoft's automated systems freezing developer access, raising urgent questions the tech giant's platform governance and the security implications for millions of users relying on these tools.

Microsoft just created a supply chain security nightmare. The developer maintaining WireGuard for Windows - a VPN protocol used by millions globally for secure communications - woke up to find his Microsoft developer account locked with zero explanation. No email, no warning, no recourse. Just a silent freeze that's now preventing critical security patches from reaching users.

The timing couldn't be worse. WireGuard has become the gold standard for VPN technology, praised by security researchers for its lean codebase and robust encryption. Major VPN providers from Mullvad to ProtonVPN have adopted it. Corporate networks rely on it. Privacy advocates swear by it. And now, Windows users are stuck on outdated versions because Microsoft's automated systems decided to pull the plug.

This isn't an isolated incident - it's becoming a pattern. Just weeks ago, another prominent developer reported the same treatment, sparking a wave of concern across the developer community. Microsoft's silence on these cases is deafening. The company hasn't explained what triggers these lockouts, how developers can appeal them, or how long resolution takes. For maintainers of security-critical software, that uncertainty is unacceptable.

The WireGuard developer, who maintains the Windows implementation of the protocol, told TechCrunch he received no notification before the lockout. One day he could sign and distribute updates through Microsoft's ecosystem, the he was completely locked out. The account freeze doesn't just block new releases - it prevents him from addressing security vulnerabilities, fixing bugs, or even communicating with users through official channels.