Microsoft terminated VeraCrypt Dev

-


Microsoft terminated the VeraCrypt developer’s Windows publisher account because the company said the account “did not meet verification requirements,” but did not provide any specific explanation, warning, or appeal path. All available reporting indicates the termination was abrupt, automated, and poorly communicated — not tied to any known security issue with VeraCrypt itself.

What actually happened

Across multiple credible reports, the situation is consistent:

  • Mounir Idrassi, the longtime maintainer of VeraCrypt, reported that Microsoft terminated the account he used to sign Windows bootloaders and drivers, with no prior notice, no explanation, and no ability to appeal.
  • The termination prevents him from publishing Windows updates, even though he can still update Linux and macOS versions.
  • Microsoft’s automated systems told him his organization “does not currently meet the requirements to pass verification,” but did not specify what requirement failed.
  • Attempts to reach a human at Microsoft resulted only in automated bot replies, leaving the developer unable to resolve the issue.

Why this matters

Because VeraCrypt’s Windows bootloader and drivers must be digitally signed:

  • Future Windows updates may refuse to load VeraCrypt’s bootloader once Microsoft revokes the old certificate authority (expected around June–July 2026).
  • Users with full‑disk/system encryption may face boot failures if the bootloader cannot be updated or re-signed.

Is this part of a bigger pattern?

Yes — the developer of WireGuard reported the same issue: sudden account termination, no warning, no explanation, and no ability to ship Windows updates.

This suggests a broader problem with Microsoft’s automated verification and enforcement systems, not a targeted action against VeraCrypt.

Microsoft terminated the VeraCrypt developer’s account due to an unspecified verification failure, provided no explanation or appeal process, and left the project unable to deliver Windows updates. This creates real risk for Windows users who rely on VeraCrypt for system encryption.

Popular posts from this blog

WSUS CVE-2025-59287 Mitigation

-
Image
CVE-2025-59287 is a critical Remote Code Execution (RCE) vulnerability affecting Windows Server Update Services (WSUS) . Here's a detailed breakdown of what it is, how it works, and what you should do about it: Overview Disclosed: October 2025 Patch Tuesday CVSS Score: 9.8 (Critical) Affected Systems: Windows Server 2012 through 2025 (including Server Core installations) Exploitability: Microsoft rates it as “Exploitation More Likely” Technical Details The vulnerability arises from unsafe deserialization of untrusted data in WSUS. Specifically, the GetCookie() endpoint in WSUS processes encrypted AuthorizationCookie objects without proper type validation. The deserialization occurs via .NET BinaryFormatter , which is known to be insecure when handling untrusted input. Attackers can send a crafted SOAP request to WSUS over port 8530 , containing a malicious AuthorizationCookie . The cookie is decrypted using a hardcoded AES key and then deserialized, allow...
Read more

Cloud Infrastructures are Having a Bad Week

-
Image
  Today’s disruptions across Microsoft Azure and Amazon Web Services (AWS) were significant, but they’re not signs of cloud computing’s demise. Instead, they underscore the risks of centralization and the importance of designing systems that can withstand provider-level failures. What happened today? • Microsoft Azure outage: Azure’s Front Door service suffered a major disruption due to a misconfiguration, impacting services like Outlook, Xbox, Microsoft 365, and even third-party platforms like Starbucks and Alaska Airlines. The Azure website states a little more than disruption. "Azure Front Door - Connectivity issues - Observing recovery Starting at approximately 16:00 UTC on 29 October 2025, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue. Affected Azure services may have included, but were not limited to: App S...
Read more

CVE-2025-58034 Fortinet Warnings and Mitigation

-
Image
Type: OS Command Injection vulnerability (CWE-78) Affected Product: Fortinet FortiWeb (Web Application Firewall) Affected Versions: 8.0.0 – 8.0.1 7.6.0 – 7.6.5 7.4.0 – 7.4.10 7.2.0 – 7.2.11 7.0.0 – 7.0.11 [nvd.nist.gov] , [cvedetails.com] Description The vulnerability is caused by improper neutralization of special elements used in OS commands . An authenticated attacker can exploit this flaw by sending crafted HTTP requests or CLI commands , allowing them to execute arbitrary code on the underlying system. This can compromise the integrity, confidentiality, and availability of the device. [nvd.nist.gov] , [cvedetails.com] Severity CVSS v3.1 Base Score: 7.2 (High) Vector: AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Attack Vector: Network Attack Complexity: Low Privileges Required: High User Interaction: None Impact: High on Confidentiality, Integrity, and Availability [cvedetails.com] Exploitation Status Actively Exploited: Yes. Fortinet confirmed expl...
Read more