VeraCrypt developer warns of Windows boot issues after Microsoft account lock

The developer behind VeraCrypt has raised concerns after losing access to a Microsoft account used to distribute critical Windows updates, warning that the situation could eventually prevent some users from accessing their own computers.

Mounir Idrassi said in a post on March 30 that Microsoft had terminated the account he had relied on for years to sign Windows drivers and the VeraCrypt bootloader. According to Idrassi, the action came without explanation and without any apparent option to appeal.

Based in Japan, Idrassi explained that he has tried to contact Microsoft regarding the issue but has not been able to reach a representative. The situation poses a significant problem because Microsoft requires developers to periodically re-verify their software using valid credentials. Without this verification, updates cannot be properly signed and distributed.

VeraCrypt is a widely used open-source encryption tool that allows users to secure files with password-protected encryption or to encrypt entire operating systems to protect against unauthorised access before boot. The latest Windows version of the software, released in May 2025, has seen nearly a million downloads, reflecting its broad user base.

The current issue affects only Windows users. Idrassi noted that he can still deliver updates to Linux and macOS systems without disruption. However, for the large number of users running VeraCrypt on Windows, updates are currently blocked due to the revoked account access.

For now, users are not required to take immediate action, as the software continues to function and no active security vulnerabilities have been identified. However, the longer-term implications could be more serious.

Idrassi warned that users who have enabled full system encryption — a feature that locks the entire operating system until the correct password is entered — could encounter boot failures in the coming months, potentially starting around late June.

The issue stems from Microsoft’s plan to revoke the certificate authority that digitally signs the VeraCrypt bootloader. This certificate ensures that the software has not been altered or compromised. Without a valid certificate, the system may refuse to load the encrypted operating system.

According to Idrassi, a new Microsoft-issued certificate authority will be required to keep VeraCrypt functioning properly on Windows systems. However, without access to the original Microsoft account, he cannot apply the necessary new signature to the software.

If the situation remains unresolved, users who rely on VeraCrypt’s system encryption feature could find themselves unable to boot their computers after July 2026. Idrassi described the potential outcome as critical, noting that the inability to update the bootloader could effectively end the software’s usability on Windows platforms.

The situation highlights the level of control major technology companies maintain over software distribution within their ecosystems. It also underscores the risks associated with relying on third-party accounts that can be suspended or terminated, sometimes without clear justification.

This is not the first instance of developers facing account-related disruptions. Earlier this year, developer Paris Buttfield-Addison was locked out of their Apple account after redeeming what was believed to be a fraudulent gift card purchased from a retailer. That account was later restored after the case drew widespread attention.

For VeraCrypt users, the coming months will be critical in determining whether a resolution can be reached before the certificate changes take effect.