VeraCrypt and WireGuard: Driver Signing Troubles, Solution in Sight
Microsoft accounts for VeraCrypt and WireGuard developers were suspended. This prevented updates – a solution is in sight.
(Image: Dirk Knop / heise medien)
The developers of the disk encryption software VeraCrypt and the VPN software WireGuard have recently been confronted with the fact that Microsoft has suspended their developer accounts. This made it impossible to sign Windows drivers, ultimately preventing software updates. Current Windows versions only accept signed drivers.
VeraCrypt developer Mounir Idrassi already addressed this in the VeraCrypt forum at the end of March. He complained that he received no notification or explanation for the suspension of his Microsoft account, which he uses to sign bootloaders and Windows drivers. Idrassi further laments that he tried to reach Microsoft through various channels but was always met with bots and automated responses, making human contact impossible.
The emerging reports prompted the WireGuard developer to post about his similar experience on X. WireGuard has planned major updates for its Windows version after four years – modernizations and improvements, bug fixes, new features, and more. However, the release is blocked by the account suspension from Microsoft, as the WireGuardNT driver cannot be signed. "It seems like they instituted an identity verification policy, didn't notify me about it, and then I guess they suspended accounts who didn't do the verification," he wrote there.
Lengthy Appeal Process
The programmer explains that he immediately completed the verification using his ID card, but this required an appeal process. This involves filling out a support ticket – which is only possible with an unsuspended account. However, a workaround through Azure and redirection to the correct department made it solvable in this case. This was two weeks ago. Microsoft informed him that the appeal process can take up to 60 days.
This could be problematic, at least in the case of critical zero-day code-injection vulnerabilities, he points out: "Sorry, you have to wait 60 days." However, he believes this is merely a case of excessive bureaucracy, which can happen.
Videos by heise
Microsoft Responds, Developers Soon Operational Again
In response to an inquiry from heise online, Microsoft replied with a link to a statement on X. The company stated that it has seen these reports and wants to resolve the issues as quickly as possible. Pavan Davuluri, President of Microsoft's Windows and Devices division, explained that they have contacted the VeraCrypt developer and spoken with a developer named Jason from WireGuard. They should be operational again soon. Mounir Idrassi confirmed this in the VeraCrypt forum in the early morning hours of Thursday.
As background information, Microsoft refers to a blog post from October 2025. There, the company explains that account verification for the Windows Hardware Program begins on October 16, 2025, and specifically requires action from partners who have not performed verification since April 2024. Pavan Davuluri states that Microsoft sent emails, displayed banners, and showed reminders. However, Microsoft wants to work on improving communication.
One problem might be that pure software developers may not necessarily consider themselves part of the Windows Hardware Program and might have viewed the corresponding emails as misdirected.
(dmk)