search

eiz / SynchronousAudioRouter

Low latency application audio routing for Windows
http://sar.audio/
GNU General Public License v3.0
1.04k stars 138 forks source link

Error starting ASIO (Win 10) #44

Closed tilllt closed 6 years ago

tilllt commented 6 years ago

When i start reaper with SAR installed, the only thing i see is "Error starting ASIO"

screenshot_1

I am using ASIO4ALL as my "hardware" ASIO for now.

I uninstalled and reinstalled SAR but that didnt help anything. Also, starting Reaper as Admin or normal user doesnt change a thing...

Any Clues?

rehlinger commented 6 years ago

Same issue. I've tried both ASIO4ALL and UMC ASIO hardware interfaces and it fails to start either. New user though so not sure. Also, JackAudio fails to connect and start the driver.

tilllt commented 6 years ago

Ok, i think i found the problem, but i really dont feel comfortable to completely disable integrity check for device drivers just to install SAR, is there another way?

screenshot_27 screenshot_28

rehlinger commented 6 years ago

Yes, this is the problem. Restarting windows with advance settings to disable signature enforcement temporarily causes the driver to work with reaper.

JonnyLong commented 6 years ago

I was getting this same issue for a long time with my notebook, and was disabling signature enforcement to get around it. On a hunch, I tried going into my BIOS settings and disabling secure boot and somehow that fixed it. I now can use SAR regularly without using advanced boot settings to disable signature enforcement. Hope this helps!

bit-drifter commented 6 years ago

I think Jonny is correct as there is a note in the 4.50 changelog for Virtual Audio Cable that says "Signed with EV certificate to allow loading by Win10 in Secure Boot mode."

Additional information here https://blogs.msdn.microsoft.com/windows_hardware_certification/2016/07/26/driver-signing-changes-in-windows-10-version-1607/

eiz commented 6 years ago

I'll never be signing SAR with an EV signature. It's not a commercial project and I don't feel like paying the troll toll.

Issue with lack of timestamp countersignature + expired cert should now be fixed (0.13.1)

dooitze commented 4 years ago

In the new build 19041.208 of Version 2004 the problem has reappeared, with the same error in the driver tab.

EDIT: Secure boot was enabled, should be fixed now.

jeinstei commented 4 years ago

eiz -- I completely agree with not paying a toll, but I would love to get this working without having such problems. Would you take a donation for a Certum signing cert? https://www.certum.eu/en/cert_offer_en_open_source_cs/

amurzeau commented 4 years ago

The open source certificate is not what's required for a driver. A driver requires an EV certificate now with Windows 10 IIRC, and that's 360€ for only one year. And there are probably heavy administrative stuff to handle with this type of certificate I guess.

jeinstei commented 4 years ago

Ouch. Understood. They really need a program where people can at least sign drivers on their local machine somehow. What an opaque process for users of open source and developers.