Driver Signature Problem

[EdTheShed1]

After following all the installation instructions, the virtual audio driver shows a warning sign beside it in Device Manager. Viewing information about it reveals an error code 52, stating that "Windows could not accept the driver signature", rendering the features of the driver unavailable. Updating/reinstalling the driver makes no difference.
Meanwhile, the virtual microphone device is nowhere to be found (should be under "Lydinnganger og -utganger" in the attached screenshot):

[Vincent0047]

Hello,
Same problem for me

[defsteph]

I am also facing this issue.

Windows 11 Pro.

Edit: I have tested disabling the driver signing by running the command bcdedit /set TESTSIGNING ON and rebooting. Besides that adding a little watermark overlay in the lower right corner of my desktop, it also enables the MTT Microphone Array and MTT Speakers as devices.

To me, this indicates strongly that something's off with the driver signing. @itsmikethetech happy to help you test this out if you need me to.

[itsmikethetech]

Investigating this. Thanks for reporting.

[godman-gomel]

Windows 11 Home.
Same problem. I am eagerly awaiting a solution. Thanks.

[Victor-Hugenay]

Yes, got this issue too

[godman-gomel]

Guys, has anyone tried installing a previous version instead of the latest one? For example, Virtual Audio Driver (25.5.3)

[itsmikethetech]

All will work in test signing mode, but we're stuck in the attestation phase at Microsoft. Need to save some funds to complete.

[Afeng-git]

一切都将在测试签名模式下运行，但我们目前处于微软的认证阶段。需要节省一些资金才能完成。

itsmikethetech，您好！期待“虚拟音频驱动程序”的驱动程序签名问题。“虚拟音频驱动程序”和“虚拟显卡驱动程序”是非常棒的产品！期待微软的认证阶段尽早通过。感谢。

[assmx]

All will work in test signing mode, but we're stuck in the attestation phase at Microsoft. Need to save some funds to complete.

It seems that the certificate is outdated:

[Faradayff]

Hello, same problem for me.
Anyone knows how to create a new certificate?

[FriedGenera]

Disable secure boot in bios and then force off all driver signature checks using an elevated (administrator command prompt). The driver will then work, but you are now at risk of a malicious driver causing an issue. However, this is usually not an issue unless you are getting drivers from a non-trusted source. After you change the boot options, you can reenable secure boot. TBH I hate this crap from MS. If I want to edit any part of my OS, I should be able to do so without jumping hoops.

1. Disable secure boot

2. bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS

3. bcdedit.exe -set TESTSIGNING OFF

4. bcdedit.exe -set NOINTEGRITYCHECKS OFF

Thanks, only needed to run bcdedit /set testsigning on after disabling secure boot to get it to work. Didn't need the other two commands.

[Faradayff]

Nice workaround but not a permanent solution, me and (I guess) more people need secure boot to be enabled to play games for example

[brain1401]

Nice workaround but not a permanent solution, me and (I guess) more people need secure boot to be enabled to play games for example

Fair point.