Microsoft Hardware Dev Center / Partner Center – Four Months Later, I Still Can't Publish a Driver

I'm hoping someone from the Microsoft Hardware Dev Center or Partner Center team sees this.

I've been trying since April 2026 to get my account into a working state so I can publish and sign a Windows driver. Instead, I've spent the last four months fighting backend account issues between Entra ID, Partner Center, and the Hardware Dev Center.

Current support case:

Hardware | Onsite Dental Systems | Incomplete...

Tracking ID: #2606060010000492

Over the past several months I have:

Worked with multiple Microsoft support engineers.

Opened numerous support cases.

Followed every instruction provided by Microsoft.

Recreated my Entra tenant when instructed.

Waited through backend synchronizations and escalations.

Re-verified my organization.

Recreated applications, permissions, and identities multiple times.

Every time one issue appears to be resolved, another backend issue surfaces.

At this point, I've spent more time trying to become an approved Microsoft developer than actually developing software.

The situation became so drawn out that my original EV code signing certificate expired before Microsoft could get my account working. I had no choice but to purchase another EV code signing certificate, adding hundreds of dollars in unnecessary expense because my account was still blocked by backend provisioning issues.

This isn't simply frustrating—it's impacting my business.

I'm a small software developer. My customers rely on my software every day, and I cannot complete Microsoft's required driver-signing process because my account remains stuck in a state that only Microsoft appears able to fix.

I want to be clear that the support engineers themselves have been courteous and have genuinely tried to help. My frustration is with the platform and the apparent lack of tools available to support when these backend account issues occur.

I believe Microsoft should consider:

Providing a complete reset option for Hardware Dev Center registrations tied to broken tenants.

Better diagnostics instead of generic backend errors.

Improving synchronization between Entra ID, Partner Center, and Hardware Dev Center.

Giving support engineers the ability to repair account provisioning without weeks of escalation.

Publishing documentation for developers who must migrate to a new Entra tenant.

If anyone from the Hardware Dev Center or Partner Center team is reading this, I would greatly appreciate someone reviewing Tracking ID #2606060010000492.

I've been trying to accomplish what should be a basic task—publish and sign a Windows driver—since April 2026. Four months later, after countless hours, multiple support cases, and even purchasing a replacement EV code signing certificate because the first one expired during this process, I'm still unable to complete it.

I truly hope this feedback reaches the appropriate engineering team, because I can't imagine I'm the only developer who has experienced this. Hopefully this process can be improved so other developers don't spend months trying to overcome backend account issues instead of building software.