VeraCrypt Developer Says Windows Users Could Face Boot Problems
The developer of VeraCrypt says Microsoft blocked access to the account used to sign Windows drivers and the bootloader. He said the account had been used for years and that it was terminated without an explanation or a way to appeal the decision.
He also said he tried to contact Microsoft but could not reach a human. Because Microsoft requires developer accounts like his to re-verify software security, he warned that many devices running VeraCrypt may soon run into boot-related problems if the issue is not fixed.
A Microsoft spokesperson did not immediately comment.
How the Microsoft Account Block Affects VeraCrypt on Windows
Why driver and bootloader signing matters
VeraCrypt relies on digitally signed Windows drivers and bootloader components. That signing process helps show that the software has not been altered by attackers. The developer said Microsoft will soon revoke the certificate authority currently used to digitally sign VeraCrypt software.
Without access to the account previously used to send software updates, he said he will not be able to apply the new required signature to VeraCrypt. In his words, that would make booting impossible.
Why Windows users are the main group at risk
He said he can still push updates to Linux and macOS users without disruption. But Windows users, who make up the majority of his user base, cannot currently receive updates in the same way.
That leaves Windows systems in a more fragile position, especially where VeraCrypt is tied directly to the startup process of the machine.
VeraCrypt System Encryption May Trigger Boot-Up Issues
What system encryption changes
VeraCrypt is an open-source encryption tool that lets users protect files with password-based encryption. It can also encrypt an entire operating system, shielding user data from pre-boot attacks.
That deeper level of protection is also where the biggest risk now appears. Users who have enabled system encryption may begin facing startup issues in the coming months, around late June.
What users should expect for now
For now, the developer said VeraCrypt will continue to work and that no current security issues have been identified. He said affected users do not need to do anything special at this stage.
That said, the warning is specific: the current setup may keep working for the moment, but systems using full system encryption could run into trouble once the existing signing path is no longer valid.
VeraCrypt Download Reach Shows the Scale of the Risk
The latest Windows version of VeraCrypt, published in May 2025, shows the installer at nearly one million downloads since release. That gives some sense of how many users could be affected if the signing issue remains unresolved.
Because VeraCrypt is widely used for file and system encryption, any disruption tied to software signing and boot access carries broader consequences than a normal app update delay. This is not just about missing a feature release. For some users, it could affect whether their computers start properly at all.
Platform Control and the Risks of Account Dependence
This situation also shows how much control large platform companies still have over software distributed through their ecosystems. When a developer depends on a platform account to maintain software delivery or trust mechanisms, that account becomes a single point of failure.
The risk is not only that an account can be revoked. It is that rules can change, decisions may come without explanation, and developers may struggle to reach a person who can resolve the issue. In this case, the result could extend beyond delayed updates and into basic device access for some Windows users.
The VeraCrypt developer said that if the issue is not resolved, it could amount to a death sentence for the project.
What This Means for VeraCrypt Users
Users on Linux and macOS
The developer said updates for Linux and macOS can still be delivered without interruption. Based on that, the current problem is centered on the Windows update and signing path.
Users on Windows
Windows users are in a different position. They are currently unable to receive updates through the affected account path, and those using system encryption face the most serious possible impact. If the signing issue remains unresolved, boot-up problems may begin appearing in a few months.