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

Win 10 Pro 1809 17763.194 Update #71

Closed hoemon closed 4 years ago

hoemon commented 5 years ago

Recent update broke SAR for my system. None of the defined virtual ins and outs are available. Uninstallation/Reinstallation of SAR and deleting and recreating virtual input and outputs give the same result.

amurzeau commented 5 years ago

Does the driver load correctly in the device manager ?

amurzeau commented 5 years ago

Also, can you tell which updated got installed exactly or your previous version before 17763.194 ?

markjfisher commented 5 years ago

I've just reinstalled windows as SAR stopped working, but thought it might have been because of some VoiceMeeter changes I'd made (desperate to get SAR working again - went for the nuke windows option).

Now, with the new windows and all updates on a base system, it's still not working.

Windows is showing me version 10.0.18362 Build 18362.

Any other information I can provide, I will do so as I really want to get this working again to use SAR/Jack/Pedalboard/Catia rather than VoiceMeeter which doesn't have as many options for routing.

markjfisher commented 5 years ago

It's not loading in the Device Manager, here's the error:

image

Driver Version: 8.46.47.980

In the Events log, during installation:

Device ROOT\MEDIA\0000 had a problem starting.

Driver Name: oem11.inf Class Guid: {4d36e96c-e325-11ce-bfc1-08002be10318} Service: SynchronousAudioRouter Lower Filters: Upper Filters: Problem: 0x34 Problem Status: 0xC0000428

amurzeau commented 5 years ago

You can try to enable testsigning in boot options: https://docs.microsoft.com/en-us/windows-hardware/drivers/install/the-testsigning-boot-configuration-option

This should fix the driver loading error. I guess there is a new driver signature enforcement since some weeks by Windows

markjfisher commented 5 years ago

do you know how much effort it will take to get it resigned?

amurzeau commented 5 years ago

the major issue with driver signing is the cost. It seems that since fresh installs of Windows 10 1607, drivers need to be signed by microsoft itself, and that require having an EV certificat which is somewhat costly. https://techcommunity.microsoft.com/t5/Windows-Hardware-Certification/Driver-Signing-changes-in-Windows-10-version-1607/ba-p/364894

This particular signature enforcement can be disabled by disabling secure boot, maybe its a better alternative for you. If you try that (disable secure boot in your efi bios), can you tell if it works ?

markjfisher commented 5 years ago

After (the scary process of) enabling test-signing mode, I can confirm that SAR no longer shows an error on startup as in my earlier screen shot.

I assume this means that all windows updates going forward will render SAR unusable without being in test mode?

I've just looked at costs for EV signing - shocking.

hoemon commented 5 years ago

Wow, this is very sad, any long term solutions?

amurzeau commented 5 years ago

The EV signature is needed only for fresh install of windows 10 1607, not if it was updated from the previous windows version. So I guess that's why not all users have issues.

From MSDN:

Enforcement only happens on fresh installations, with Secure Boot on, and only applies to new kernel mode drivers (after July 29th, 2015) :

amurzeau commented 5 years ago

Turning Secure Boot OFF might be a better alternative than enabling testsigning.

jnki commented 5 years ago

So, to get this straight... on a fresh install of Windows, we would need Secure Boot off permanently? Or just to install SAR, and then we can switch it back on?

amurzeau commented 5 years ago

I didn't tried, but I think secure boot need to be disabled even after installation, else the driver probably won't be loaded.

@markjfisher @hoemon which solution did you do ?

markjfisher commented 5 years ago

I did (2) and (3), as I couldn't enable test signing without disabling secure boot. Once I'd disabled secure boot, I didn't try to run it without testsigning enabled.

amurzeau commented 4 years ago

Closing this as the issue has been worked around using test signing option.

markjfisher commented 4 years ago

I've had to revisit this.

I previously left my windows 10 in test signing mode on using bcdedit -set TESTSIGNING ON

However, another application won't run in this mode, so I turned it off again, and have found that SAR is still working.

I had assumed it would fail unless both secure boot was disabled AND test signing was on, but it appears it is only secure boot that needs to be left permanently off for SAR to work.