search

eiz / SynchronousAudioRouter

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

0.13 audio driver unsigned, won't install on Windows 10 x64 1703 #39

Closed SnorreSelmer closed 6 years ago

SnorreSelmer commented 6 years ago

Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)

paulheu commented 6 years ago

As I recall there's a thread about this here and how to make this work is also well documented on the net. I do not have the links handy, but if you google the first sentence in your post it should come up.

SnorreSelmer commented 6 years ago

Seems like a lot of these solutions involve gimping Windows security, and that's not really an option for me. I'll keep my eye on this project in the hopes it will change. ;)

eiz commented 6 years ago

SAR is in fact signed and you should not get this error.

Does 0.12 work for you? Are you able to reach the DigiCert timestamp server (timestamp.digicert.com)?

JonnyLong commented 6 years ago

I'm getting this same issue on Windows 10 64-bit 1709. Device manager says the driver signature couldn't be verified.

eiz commented 6 years ago

I've got the cert for 2018 now, I'll post a resigned build this weekend and we'll see if that clears it up for you.

SnorreSelmer commented 6 years ago

Excellent!

JonnyLong commented 6 years ago

Has the re-signed build been posted? I haven't been able to find it. Thanks!

ValentinLindblad commented 6 years ago

Can't find it either, the certificate installed when using the latest link was valid to: ‎ Monday, ‎13 ‎November ‎2017 13:00:00 @eiz could you resign? Everything works for me when in Windows Testing Mode.

JonnyLong commented 6 years ago

@eiz Do you have a place to donate? I really appreciate this project and use it daily for livecasting, would love to help support software I use! I'm waiting to reinstall my OS until the re-signed build is uploaded, do you know when that will be? Thanks :)

pitkley commented 6 years ago

@eiz If you get around to re-signing and publishing a build, would it also be possible to sign the SarAsio.dll and SarAsio_x64.dll files?

I am running into an issue with an anti-cheat (specifically the 3rd party FACEIT anti-cheat for Counter-Strike Global Offensive) where it blocks the SarAsio.dll. I have contacted FACEIT support and apparently signing the DLLs should fix it. (Quote: "The DLL has not been signed, that is why it is blocked.")

As an aside: I want to thank you very much for what you have enabled us to do with SAR and the time you have spent on it, I value the flexibility it gives me. If there is anything I might be able to help with, let me know.

spencerius commented 6 years ago

I have this problem today with the latest version available on the site here.

massivelivefun commented 6 years ago

Looking forward to the new build that comes with the signed system drivers. Hopefully the driver signatures can fix a lot of the problems that I run into when it comes to Battleye and Easy Anti Cheat.

omarcostahamido commented 6 years ago

where's the resigned build?

eiz commented 6 years ago

0.13.1

pitkley commented 6 years ago

Thank you very much @eiz. As far as I can tell, the signed DLLs get accepted by the FACEIT anti-cheat and I can use SAR now without issues. :+1:

jbadnes commented 5 years ago

Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)