Microsoft attributes blocking of VeraCrypt, WireGuard and Windscribe accounts to pending verification
Microsoft has been forced to explain itself after several privacy and cybersecurity projects reported the sudden suspension of their developer accounts. Among those affected were VeraCrypt, WireGuard and Windscribethree well-known names in security software who, during that period, were left without access to key tools for publishing updates to Windows.
The most delicate consequence was not only administrative. In the case of WireGuard, its creator explained that he could not sign drivers, something essential for distributing new versions of the client for Windows. In projects of this type, where updates fix bugs, tighten security or cover vulnerabilities, such a block can result in delays with real impact for users.
The first public reaction pointed directly at Microsoft, especially since several developers They claimed they had not received a clear explanation nor have I managed to speak to a person within the company. VeraCrypt even reported automatic responses and ineffective support, while Windscribe stated that it had been trying to resolve the problem for more than a month without results. That mix of silence and suspension triggered outrage in the community.
Microsoft denies a deliberate veto and points to a change in its hardware program
As the hours passed, the case began to take a different turn. Pavan Davuluri, executive vice president of Windows and Devices, said that Microsoft was working to restore the affected accounts and explained that the origin of the problem would not have been an intentional blocking of these developers, but rather the entry into force of a mandatory verification within the Windows Hardware Program.
According to this explanation, the company demanded from the October 16, 2025 that members who had not completed the process since April 2024 would verify their identity with an official document within 30 days. Davuluri defended that Microsoft had warned with emails, notices and reminders, although at the same time he recognized that the incident served to review how these types of internal changes are communicated.
This nuance changes the focus of the news, but does not erase the underlying problem. If the suspension was a consequence of an unfulfilled procedure, the episode also leaves Microsoft in a bad light for the way in which such a sensitive infrastructure is managed for third parties. When a supplier centralizes the signing of drivers and access to distribution, a bureaucratic incident can become a bottleneck for critical tools.
The problem was not a conspiracy, but a serious communication failure
Within Microsoft there were also voices asking to lower the most explosive reading of the case. Scott Hanselman, vice president of the company, publicly defended that Not every controversial episode responds to a dark maneuver and that, sometimes, the origin is as simple as checking the mail and completing pending documentation. Your message was intended to provide context, although it does not eliminate the fact that support failed when the developers attempted to escalate the issue.
The resolution, therefore, seems to move away from the idea of an offensive against privacy or encryption software. But the story is still relevant because it exposes the fragility of many projects when they depend on closed platforms to distribute essential components in Windows. There was no political veto or purge of accounts, but there was a system that was not very transparent for those who needed a quick response.
Ultimately, Microsoft gains some leeway by proving that the origin was in a pending check and not an arbitrary block. Even so, the company is affected because the episode affected precisely tools that live by transmitting trust. When security applications remain weeks without being able to be updated due to a poorly communicated process, the problem is no longer just administrative and also becomes one of credibility.
