Background: Mass Suspensions Hit Open-Source Developers
Microsoft has introduced a fast-track reinstatement procedure for developers whose accounts were recently suspended from the Windows Hardware Program. The move came in response to widespread complaints from well-known open-source contributors who found themselves locked out of the program without prior warning.
The suspensions, which occurred last week, affected accounts used to publish Windows drivers and updates for widely adopted tools including WireGuard, VeraCrypt, MemTest86, and Windscribe. Losing access to these accounts meant affected developers could not release new Windows builds or critical security patches, raising serious concerns about potential delays in responding to emerging vulnerabilities.
Developers Describe Being Locked Out Without Notice
Several high-profile developers publicly detailed the impact of the suspensions. Mounir Idrassi, the developer behind VeraCrypt, stated that his account had been terminated without any warning and that he was unable to reach a human support representative through available channels, leaving him unable to publish Windows updates.
Jason A. Donenfeld, the maintainer of WireGuard, reported a similar experience, describing being locked out while facing a lengthy and unclear appeals process. Other developers echoed these frustrations across social media platform X.
Microsoft's Explanation for the Suspensions
Following the wave of complaints on X, Microsoft Vice President Scott Hanselman responded publicly, explaining that the accounts had been suspended due to developers failing to complete mandatory identity verification within the Windows Hardware Program. Hanselman noted that Microsoft had been emailing partners about this requirement since October 2025.
Microsoft enforces identity verification for participants in the Windows Hardware Program because the program allows developers to sign and distribute kernel-level drivers. These drivers operate with elevated system privileges and have been exploited by threat actors in past attacks — making rigorous verification a legitimate security concern for the broader Windows ecosystem.
Despite Microsoft's assertion that notifications had been sent, many developers claimed they had never received any emails or other prior notice before their accounts were suspended. This discrepancy became a central point of frustration within the developer community.
The New Fast-Track Reinstatement Process
While Hanselman and other Microsoft staff began working informally to restore affected accounts, Microsoft yesterday rolled out a more structured temporary process designed to accelerate reinstatement for suspended developers.
"We've heard your feedback. We know that some partners whose accounts were suspended following Account Verification are experiencing challenges regaining access to the Hardware Dev Center (HDC). Protecting the security of the Windows ecosystem remains our highest priority, and we are adding a temporary process to accelerate the reinstatement experience for partners who are able to resolve outstanding compliance requirements."
This statement appeared in a new update to Microsoft's official advisory on the matter.
How to Request Reinstatement
Under the newly introduced procedure, developers are directed to open a support case through the Hardware Program, which Microsoft describes as the fastest available route to restoring account access. Key requirements for submitting a reinstatement request include:
- Opening a support case directly through the Hardware Program portal
- Providing a clear business justification explaining the intended use of the Hardware Dev Center
Microsoft has made clear that reinstatement does not equate to full access being immediately restored. Once an account is reinstated, any outstanding compliance requirements — including completing identity verification — must still be resolved before full functionality is returned.
Guidance on Support Workflow Issues
Microsoft also acknowledged that developers had encountered difficulties with the support submission workflow itself. To address this, the company advised partners to:
- Ensure they are signed in with the correct account when submitting support tickets
- Continue prompting Microsoft's Copilot assistant to create a ticket if automated assistance fails to do so
For developers unable to submit requests through standard channels, Microsoft provided an alternative support contact to help initiate the reinstatement process outside of the typical workflow.
Timeline and Urgency
Microsoft has not announced how long this accelerated reinstatement process will remain available, describing it only as a temporary measure. Developers whose accounts remain suspended are advised to act quickly and take advantage of the fast-track option while it is still in place.
The incident has spotlighted ongoing tensions between security enforcement mechanisms and the practical realities faced by open-source maintainers, who often lack the dedicated compliance infrastructure of larger organizations. The ability to sign and distribute kernel-level drivers is critical for security and utility software, and any extended disruption to that process carries tangible risks for end users who rely on timely updates.
Source: BleepingComputer