how to submit a virtual audio driver to microsoft store?

Question

Hi Friends,

As of 2026, how to submit a virtual audio driver to microsoft store?

People gives me different answers, some says I need open a microsoft hardware account first? I already have a microsoft store account. Where is the link to open a microsoft hardware account?

Some says I need a EV signing before I submit to microsoft store. Some says once I submit to microsoft store, microsoft store will handle the EV signing.

What is exactly the latest microsoft process to handle such a business? any one is currently working for microsoft, and may know its latest policy and process?

Thank you.

TianTu Tech

Answer 1

Hi,

Thank you for posting.

---

You’re mixing two different channels a bit:

• Microsoft Store → for apps
• Windows Hardware / Windows Update → for drivers (including virtual audio drivers)

For an actual virtual audio driver, the relevant path today is the Windows Hardware dashboard / Windows Update, not the Microsoft Store directly. The Store is usually only for a companion app that talks to your driver.

---

1. Hardware (partner) account vs. Store account

A normal Microsoft Store account (for apps) is not enough.

You also need to enroll in the Windows Hardware Developer Program and use the Partner Center for Windows Hardware (“hardware account”). That’s where you:

• upload driver packages
• get them attestation‑signed / certified
• publish them to Windows Update

Start here:

• Partner Center / driver publishing overview Publish a driver to Windows Update

From that page you can navigate to the hardware dashboard and enrollment docs.

---

2. EV certificate vs. Microsoft’s own signing

For a typical virtual audio (kernel‑mode) driver there are two different signatures to think about:

1. Your EV code signing certificate
   • You use this to sign your driver package before you submit it.
   • It’s also how Microsoft verifies who you are as a publisher.
2. Microsoft’s attestation / WHCP signature
   • After you submit, Microsoft re‑signs the package.
   • That Microsoft signature is what Windows actually trusts on end‑user systems.

That’s why you see conflicting answers:

• “You need EV signing” → this is about your certificate, required for submission.
• “Microsoft will handle the signing” → this is about the final signature that Windows loads.

The official code‑signing requirements are documented here:

• Code signing requirements for Windows hardware Code signing requirements for Windows hardware

---

Hope this helps.

Answer 2

To submit a virtual audio driver to the Microsoft Store, you will need to follow several steps, which include creating a Microsoft Hardware account and ensuring your driver meets specific requirements.

1. Create a Microsoft Hardware Account: If you already have a Microsoft Store account, you will need to create a separate Microsoft Hardware account. You can find the necessary information and links to create this account on the Windows Dev Center.
2. Obtain EV Signing: It is important to have your driver signed with an Extended Validation (EV) certificate before submission. This is a requirement for drivers submitted to the Microsoft Store. However, you should check the latest guidelines from Microsoft, as they may have specific processes regarding EV signing and submission.
3. Follow Submission Guidelines: Make sure to adhere to the submission guidelines provided by Microsoft. This includes ensuring that your driver is tested and meets all necessary compliance requirements.
4. Use the Partner Center: All submissions go through the Partner Center. If you do not already have a Partner Center developer account, you will need to sign up for one before you can submit your driver.

For the most accurate and up-to-date information, it is recommended to consult the official Microsoft documentation or reach out to Microsoft support directly.

---

References:

• Create and submit a product for signing
• Step 1: Create a UWP device app
• Submitting an app to the Microsoft Store