lissa.wang@mmd-p WINDOWS DRIVER submission access need to be recovered asap

Submission access issues for Windows Hardware Certification and driver signing cannot be fixed directly in the dashboard UI; they require Partner Center account and submission management steps and, if those fail, escalation through official support.

For immediate actions:

1. Verify Partner Center account and role
   • Confirm that the affected @mmd-p.com account still exists in the Partner Center tenant and is assigned the correct roles/permissions for Hardware submissions (for example, roles that can manage hardware drivers and submissions). If the account was removed or its role changed, restore the appropriate access.
2. Try using the Hardware dashboard API with a different account
   • If another account in the same Partner Center tenant still has driver management permissions, use that account to:
     • Query existing products and submissions via the Microsoft Hardware API scenarios (for example, methods under Drivers such as Get product data and Manage product submissions).
     • Confirm whether submissions can be created/updated from that account. This helps isolate whether the issue is specific to the @mmd-p.com identity or to the Partner Center hardware enrollment as a whole.
   • API overview and scenarios are described under Hardware dashboard API. See the Drivers scenario for methods to get, create, and update drivers and submissions.
3. Check submission process and common errors
   • If the problem is that new HLK-based submissions fail during upload or processing (rather than pure access/permission denial), verify that:
     • The HLK/HCKX/HLKX package is correctly repackaged as .zip (not Zip64) and then renamed back to .hckx/.hlkx if applicable.
     • The CAB structure for attestation or certification submissions is correct (no driver files in the CAB root; INF present in subfolders) as described under Create a new hardware submission → Troubleshoot submission errors.
   • Fix any “File missing”, “Zip64”, or “Package fails to open” errors as documented, then retry submission.
4. Use the dashboard search to confirm submission visibility
   • If some submissions are missing or appear inaccessible, use the View hardware submissions search:
     • Try plain-text search with product name, submission ID, INF name, or hardware ID.
     • Use keyword search like @ProductName:"<partial name>" or @SubmissionStatus:"Failed" to confirm whether submissions exist but are filtered out.
   • This helps distinguish between “no access to submit” and “submissions created but failing/hidden”.
5. Manage and monitor submissions after test upload
   • Once HLK results are uploaded successfully, manage the certification flow under the Windows Hardware Compatibility Program process:
     • Use the dashboard to monitor submission status and then manage shipping labels and distribution if needed, as described in Windows Hardware Compatibility Program Certification Process → Step 5: Manage and Update.
6. Escalate through official support (required if account is blocked or misconfigured)
   • Because the issue has persisted since late January and a support request from February is still unresolved, open or update a case through the official Partner Center / Hardware dashboard support channel referenced in the docs:
     • Use Support for Partner Center dashboard (linked from Create a new hardware submission → Other issues) or the support page linked from Hardware dashboard API to request help.
   • In the support ticket, include:
     • The exact @mmd-p.com account UPN.
     • Partner Center tenant ID and hardware program enrollment ID (if available).
     • Screenshots or exact error messages when attempting to submit HLK packages.
     • Date and ID of the previous support request from Feb-9 2026 and a request for escalation.
7. As a temporary workaround
   • If allowed by internal policy, create or use another Partner Center user in the same tenant with the required hardware submission permissions and attempt the HLK submission from that account while the original account’s access issue is being resolved by Microsoft support.

If none of the above resolves the problem, only Microsoft’s Partner Center / Hardware dashboard support can correct tenant-level or account-level issues preventing submissions, so escalation with full diagnostic details is mandatory.

References:

• Create a new hardware submission
• View hardware submissions
• Hardware dashboard API
• Windows Hardware Compatibility Program Certification Process