Microsoft Ban Leaves VeraCrypt Unable to Sign Critical Windows Drivers

VeraCrypt, a preeminent figure in the realm of open-source disk encryption, has recently encountered a formidable crisis: the project lead’s Microsoft account has been summarily suspended. This administrative sanction has effectively paralyzed the developer’s ability to procure the requisite signatures for drivers and bootloaders, potentially rendering future iterations of the software incapable of initializing on Windows 10 and 11.

The project’s lead developer, Mounir Idrassi, has issued an urgent appeal for assistance, lamenting that Microsoft enacted the ban without prior warning or a detailed explanation of the perceived transgression. Despite his efforts to seek recourse, he has found himself trapped in a digital labyrinth, unable to secure an audience with a human representative. While typical applications missing valid code signatures merely trigger warnings within Microsoft Defender, the integrity of driver and bootloader signatures is non-negotiable within the Windows ecosystem.

Windows 10 and 11 enforce stringent prohibitions against unsigned or invalid kernel-mode components. Consequently, this account suspension prevents the release of any novel updates for the Windows platform, although legacy versions—bearing previously verified signatures—remain functional for the time being. This predicament is exclusive to the Windows environment; the macOS and Linux distributions of VeraCrypt remain unscathed and fully operational.

Of particular concern to existing users who have encrypted their system partitions is a looming deadline in late June. Should the developer’s account remain in limbo, the expiration of 2011 UEFI boot certificates may render the system unable to trust existing signatures, thereby precipitating catastrophic boot failures. Adding to the frustration, Microsoft’s automated review process has deemed the organization ineligible for re-verification and summarily closed the application without offering a path for appeal.

Mounir’s attempts to protest this decision have been met with a wall of automated responses, leaving the sudden revocation of an account used faithfully for years shrouded in mystery. While the situation has garnered significant traction on social media—potentially catching the eye of Microsoft employees who might facilitate an internal resolution—the ultimate restoration of the account remains an agonizing uncertainty.