Technology VeraCrypt developer claims that Microsoft has terminated his account

[lokamoka820]

Content source

https://chipp.in/software/windows/veracrypt-developer-claims-that-microsoft-has-terminated-his-account/

VeraCrypt is a popular cross-platform encryption software that is available for Windows, Linux and macOS. It is one of the successors of TrueCrypt and can be used to encrypt hard drives, including system drives, and to create data containers on drive that are encrypted.

The developer of the application, Mounir Idrassi, published a project update on Sourceforge a few days ago. There, he explained why the project had been silent for the past few months.

According to his description, Microsoft terminated the account that he used to sign Windows drivers and the bootloader. This affects the Windows version of the encryption software, as updates can’t be signed anymore because of this. The Linux and macOS versions of the software are not affected by this.

To make matters worse, a screenshot with a message by Microsoft suggests that an appeal is not available. It is unclear what that means for the project. While a solution may be found eventually, likely through enough outside pressure to get a Microsoft representative to look at the case, it is certainly problematic when a company that operates its own encryption software — Microsoft with BitLocker — is blocking a competitor from releasing updates for his.

 

[Bot]

This is a serious issue for VeraCrypt on Windows, but the last sentence in that quote goes beyond what can be concluded from the available facts.

What appears to be confirmed

• The VeraCrypt developer publicly said that the Microsoft account used to sign Windows drivers and the bootloader was terminated.
• If that signing path is no longer available, it can disrupt or delay new Windows releases that require properly signed components.
• Linux and macOS builds would not be affected in the same way because this is specifically a Windows code-signing / driver-signing problem.

What is not safe to conclude

• It is not safe to say Microsoft blocked VeraCrypt because it is a competitor to BitLocker.
• There is no verified evidence in the quoted text showing anti-competitive intent.
• Code-signing account actions can happen for several reasons, including policy, compliance, documentation, account verification, or signing-program issues. Without an official explanation, assigning motive would be speculation.

Practical impact for users

For Windows users, the main concern is not whether VeraCrypt instantly becomes insecure, but whether future updates, driver signing, and long-term maintenance are disrupted.

That can mean:

• Delayed Windows releases
• Problems distributing updated signed drivers or boot components
• Extra uncertainty for users who depend on VeraCrypt for system encryption on current and future Windows versions

What users should do now

• Avoid panic or rushed changes if your current setup is working normally.
• Follow the official VeraCrypt project channels for confirmed updates.
• Do not download unofficial “fixed” Windows builds from random third-party sources.
• Make sure recovery media, rescue information, and backups are current before making any encryption-related changes.
• If planning a fresh deployment on Windows, it may be sensible to wait for clarification from the developer before committing to a new setup.

Bottom line

The signing problem itself looks credible based on the developer’s statement, and it is potentially disruptive for VeraCrypt on Windows. But the claim that Microsoft is blocking a competitor for competitive reasons is still speculation unless supported by verifiable evidence.

 

[cofer123]

The WireGuard creator was also locked out of his account and is unable to push any updates: VeraCrypt, WireGuard maintainers locked out by Microsoft, unable to deliver Windows updates

 

[brambedkar59]

 

[Wrecker4923]

According to a comment to the X post, and a PCMag article:

Scott Hanselman, a VP and Member of Technical Staff at Microsoft/GitHub, responded to Windscribe's tweet, saying, "Should be fixed in a bit," and added, "We've been sending everyone emails since October 2025."

Although that sounds like BS and doesn't address anything, it does post this link about Microsoft requiring all partners to reverify their accounts for the Windows Hardware Program.

Effective October 16, 2025, Microsoft will initiate mandatory account verification for all partners in the Windows Hardware Program who have not completed account verification since April 2024.

which may explain those high-profile account suspensions/revocations(!), since those developers never mentioned receiving such an email or trying to "reverify" their accounts.

So Big Bros are trying to keep all of us safe, probably with automated processes that have no appeals and messed-up communications, which in some cases leaves us less safe than before.

 

[Zero Knowledge]

The directive to ban VeraCrypt developer's account probably came from the government. Can't break the encryption? Ban the dev account so updates can't be issued. Can't ban the software? Ban the dev account for the same reason. If this is not the perfect example of shadow banning I don't know what is. And the true meaning behind this action? Eventually the people who use VeraCrypt who are probably high value targets will be vulnerable to new exploits years into the future when they become available because there will be no security fixes or updates.

The WireGuard creator was also locked out of his account and is unable to push any updates: VeraCrypt, WireGuard maintainers locked out by Microsoft, unable to deliver Windows updates

This makes perfect sense and I suspected something like this because the dev use to respond to my submitted bugs and update WG but then went silent. Can't break the encryption but can't ban the software because it's illegal under the constitution? Ban the dev account so they can't update the software.

Also has anyone noticed Signal Windows client updates have stopped being published? Same issue?

Very shifty and shady and backhanded but expected.

 

[Wrecker4923]

Also has anyone noticed Signal Windows client updates have stopped being published? Same issue?

I looked. The latest update was three hours ago, and the one before that was three weeks earlier. The Windows Store version was last updated on 2026-04-02.

Also, Signal app doesn't install kernel drivers, unlike Veracrypt & Wireguard.

 

[simmerskool]

Also has anyone noticed Signal Windows client updates have stopped being published? Same issue?

Very shifty and shady and backhanded but expected.

not sure about Signal windows, but Signal update in linux yesterday

 

[Wrecker4923]

Four hours ago, the Veracrypt developer said Scott Hanselman, the VP from Microsoft in the X post, got him in touch with some people at MS, and he was crossing his fingers that the issue would be resolved soon. He thought the media coverage did the trick.

 

[Zero Knowledge]

Four hours ago, the Veracrypt developer said Scott Hanselman, the VP from Microsoft in the X post, got him in touch with some people at MS, and he was crossing his fingers that the issue would be resolved soon. He thought the media coverage did the trick.

Yeah nothing like the public outrage machine to force MS into action, the problem with dual use tech is that it's used by both good and bad. Always has been, always will be.

Doesn't explain the whole fiasco, why they never received emails or why there was no method to appeal. It's shady stuff like this that makes you wonder who is pulling the strings.

 

[TairikuOkami]

Doesn't explain the whole fiasco, why they never received emails or why there was no method to appeal.

Everything is "reviewed" by AI these days , so it is stuck in a loop. Like I was banned on Discord by AI, I emailed for support, they told me to appeal on a banned Discord.

 

[Berny]

Also, on X :

 

[Wrecker4923]

The dev has resolved the issue.

Hello everyone,

I just wanted to let you know that I have regained access to my Microsoft Partner Center account. Mr Scott Hanselman's intervention was key to getting this issue resolved and I am very grateful to him.

A big thank you as well to the community whose support helped trigger widespread media coverage of this issue affecting me and other security projects. It feels good to see the positive power of social media in making our voices heard.

Now I can finally prepare the long-overdue upcoming release. I will share timeline updates in the coming days.

 

[Zero Knowledge]

Great news, good to see a nice outcome. I guess people power does work

 

[SeriousHoax]

The dev has resolved the issue.

Also received an update for the WireGuard app today. So MS unbanned his account also.

 

[Zero Knowledge]

Also WireGuard Windows client has been updated First time in about 3 to 5 years. *Oops didn't see the above post, beat me to it*

 

[brambedkar59]