SAR still unsigned.

[EarthasaurusRex]

I've been trying a 0.12 and 0.13 and they all seemed to be unsigned for me.

I've recently just got it to start working! Check this link here for ways to install unsigned drivers:

https://www.supportrix.com/kb/how-to-install-unsigned-drivers-in-windows-10/

I've tried using the Advanced Boot Menu method and it worked for me. You should be able to check whether the driver is working in the Device Manager (using the search function should bring it up for you) under "Sound, video, and game controllers." If "Synchronous Audio Router" has an exclamation icon next to it then it means that Windows won't run it. After getting it installed properly it should disappear. Hope this helps!

EDIT: This method seems to deactivate the driver upon restart; I tried using the enable test mode method and SAR still worked after several reboots after so maybe you could try that too if you'd like.

[ramonsmits]

Release 0.13.2 is not signed. I could install 0.13.1 without issues. Will future releases be signed again? I read the following https://github.com/eiz/SynchronousAudioRouter#unsigned-prereleased-drivers-note

Prereleases of SAR are unsigned. That means that it is required to enable testsigning boot option to make Windows load the driver. Else the driver won't be loaded.

However, I just looked at the releases and all releases are marked pre-release. Release 0.13.1 is signed and I could install that without any issues.

[amurzeau]

Signing a driver for Windows 10 requires:

• understanding the complex process of signing a driver by Microsoft
• and probably a registered enterprise or maybe just a AD directory
• a lot of money for an EV certificate (around 600€ / year)

Previous releases were signed using an older certificate that is now expired.

Maybe eiz is working on it, but sadly that's a lot of administrative work to get it signed. (which I'm not willing to do, this is too much for me and I don't have any issues using Windows with testsigning enabled).

[lahwran]

what sort of bounty would you/eiz need in order to be willing to go through the process for a given renewal period?

[amurzeau]

See also: https://discord.com/channels/373750800947871745/731985642950754366/799747195841937448

Now, signing a driver requires heavy administrative stuff (like having a registered enterprise). And that's mostly the issue, not a money issue.
To quote eiz in the above discord link:

from time to time people have offered to chip in money to help solve this problem, and it's 100% not the issue. I can pay for any fees. The issue is I don't have the time or patience to navigate this bullshit, they just keep making it more and more complicated and locking things down more

See also:
#86 (comment)
https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/register-for-the-hardware-program
https://www.reddit.com/r/windowsdev/comments/aloemr/just_what_is_needed_to_sign_a_windows_driver/eg1sow3?utm_source=share&utm_medium=web2x&context=3
https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/attestation-signing-a-kernel-driver-for-public-release

[btnmasher]

Reading that reddit thread you cited, it seems that the poster discovered that an EV certificate (the one requiring the registered enterprise and so forth) is only required for SecureBoot-compatible drivers, and a Standard Class 3 certificate can be used with SecureBoot disabled and not require testsigning mode to be enabled? Would that be a possibility?

[MPeti1]

I've recently just got it to start working! Check this link here for ways to install unsigned drivers:

https://www.supportrix.com/kb/how-to-install-unsigned-drivers-in-windows-10/

I've tried using the Advanced Boot Menu method and it worked for me. You should be able to check whether the driver is working in the Device Manager (using the search function should bring it up for you) under "Sound, video, and game controllers." If "Synchronous Audio Router" has an exclamation icon next to it then it means that Windows won't run it. After getting it installed properly it should disappear. Hope this helps!

EDIT: This method seems to deactivate the driver upon restart; I tried using the enable test mode method and SAR still worked after several reboots after so maybe you could try that too if you'd like.

Did you use test mode only for installation, or you left it turned on?

[Gamershy]

Signing a driver for Windows 10 requires:

• understanding the complex process of signing a driver by Microsoft
• and probably a registered enterprise or maybe just a AD directory
• a lot of money for an EV certificate (around 600€ / year)

Previous releases were signed using an older certificate that is now expired.

Maybe eiz is working on it, but sadly that's a lot of administrative work to get it signed. (which I'm not willing to do, this is too much for me and I don't have any issues using Windows with testsigning enabled).

I, personally, am unable to enable testsigning, so this sucks. Lmao.

[ramonsmits]

I, personally, am unable to enable testsigning, so this sucks. Lmao.

Just use something else then unless you want to donate a large sum of money so that someone can spend hours or days to get this done?

If not, keep your LMAO to yourself.....

[lahwran]

I think I was unclear before - how much would it cost to pay for someone to go through the frustration of figuring this out? I wasn't talking about paying for microsoft fees, I'm talking about cost of labor of getting it to work with microsoft's system so that the fees can be paid. My expectation is that the answer will be "geez, like, $5000 at least? I don't know?" and then that will be that unless someone turns up who wants it enough to spend either that much money to pay for the frustration-time of the core devs, or who wants to spend that-much-money's-worth of their own developer skills. But that's where I'm coming from in asking. But it's possible the answer is "If someone wanted to pay enough, I would be unwilling to accept the money due to suspicion"