Microsoft rolls out fast-track to reinstate Windows hardware dev accounts

Microsoft has introduced a fast-track process to help developers regain access to suspended Windows Hardware Developer accounts, following widespread complaints that they were locked out without warning.

Last week, the company suspended accounts used to publish Windows drivers and updates for widely used tools like WireGuard, VeraCrypt, MemTest86, and Windriver. The suspensions prevented developers from releasing new Windows builds and security patches, raising concerns about potential delays in responding to vulnerabilities.

VeraCrypt developer Mounir Idrassi stated that his account had been terminated without warning and that he was unable to reach a human support representative, leaving him unable to publish Windows updates. Similar experiences were reported by WireGuard maintainer Jason A. Donenfeld and others, who described being locked out while facing lengthy or unclear appeals processes.

After many developers took to X to report the suspensions, Microsoft Vice President Scott Hanselman said the accounts were suspended for failing to complete identity verification in the Windows Hardware Program and that the company had been emailing partners about the requirement since October 2025.

Microsoft requires identity verification for the Windows Hardware Program because it allows developers to sign and distribute kernel-level drivers, which run with high privileges and have been abused by threat actors in past attacks. However, many developers claimed they had not received any prior notification, including emails, before they were suspended.

While Hanselman and others at Microsoft have been working to reinstate accounts, Microsoft yesterday introduced a temporary process to fast-track reinstatement for suspended accounts.

"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)," reads a new update to Microsoft's advisory.

"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."

Under the new process, developers are told to open a support case through the Hardware Program as the fastest way to reinstate accounts. Requests must include a clear business justification explaining how access to the Hardware Dev Center will be used. Microsoft says that once reinstated, all outstanding compliance requirements must still be resolved before full access is restored.

The company also addressed issues developers reported with the support workflow. It advised partners to ensure they are signed in with the correct account when submitting tickets and to continue prompting Copilot to create a ticket if automated assistance fails. For those unable to submit requests through standard channels, Microsoft provided an alternative support contact to help initiate the process.

Microsoft has not said how long this accelerated process will remain in effect, so affected developers are advised to act quickly.

This incident highlights the delicate balance between security requirements and maintaining developer access to critical infrastructure. The Windows Hardware Program's identity verification requirements, while important for preventing malicious actors from distributing signed kernel drivers, have created significant disruption for legitimate open-source projects that many Windows users rely on.

The fast-track reinstatement process represents Microsoft's attempt to address immediate concerns while maintaining security standards. However, the situation raises questions about communication practices and the potential impact on security updates for widely used tools when developer accounts are suspended unexpectedly.

For affected developers, the key steps are:

• Open a support case through the Hardware Program immediately
• Include a clear business justification for account access
• Ensure you're signed in with the correct account when submitting tickets
• Use the alternative support contact if standard channels fail
• Be prepared to complete all compliance requirements after reinstatement

The incident serves as a reminder of the critical role that developer accounts play in the software supply chain and the potential security implications when access to these accounts is disrupted.