PlanetZ forums - scopeusers.com

Hello, during booting my Win10 PC yesterday some updates have been installed. Since that I'm not able to start scope application, only getting the following:
It worked fine until yesterday since July under Win 10.

Any Idea ?

Thanks

I suppose it is the driver signing thing, again.

Enable the unsigned drivers permission.

http://forums.scopeusers.com/viewtopic.php?f=1&t=31313

yep, google "disable driver signature enforcement windows 10" for instructions. after following the directions, reinstall the Scope driver either by choosing "update driver" in the device manager and then manually choosing the Scope driver, or, easier, go to program files\Scope\driver and run the SetupDriverScopePCI.exe

thanks everybody. I'll try these days. Until then, any additional idea is welcome.

there is no additional idea.

the Scope driver isn't signed by Microsoft.
now that Microsoft considers the operating system to be a service and not a product, they feel that it is within their rights to remove unsigned drivers(i.e. drivers that did not send money to Microsoft for approval) after an update. it's not a big deal.

in the very likely event of an update to Scope, there will probably be a signed driver, just because it's a pain for everyone otherwise, even though it's expensive and will drive up the cost of the update.

Ok, gary. I'll try and let you know. Thanks

yes, you need to install scope drivers again after major upgrade to 1607 version.

garyb wrote:go to program files\Scope\driver and run the SetupDriverScopePCI.exe

...as administrator.

Thanks!

Hello Everybody,

today I took the time trying to bring my scope card back to life.

I did the following according to above recommendations:

I entered in the comand prompt (as admin) bcdedit /set testsigning on.
After reboot in the right lower corner I recognized the follwing... Finally the card does work again.

Thank you all for your help. Overall it took me 15 minutes.

Michael

use the same method to turn test mode off...

use this command:
bcdedit /set testsigning off

Is that required or recommended ? Assuming scope won't work any longer.

well, it doesn't matter if you don't use online apps that might install a bad driver without your permission, but the system was designed to run with driver security enabled. it won't matter to Scope once the driver is installed. it's only necessary to disable driver security to install the driver.

is that an authorized version of windows? i usually only see the build version on Windows install that have not been authorized...

Ok, testmode disabled and scope still works.
My Windows is an official copy. An online upgrade from Win7 during the free upgrade period...

glad it's working!

me, too

Hello, today I tried to use the ASIO1 source and the audio application comes up with....
Analog Input and Output are working great...

Any Idea ? --> before the Win10 Issue occured Asio worked fine.

Do you have ASIO modules in your project?
Show a screenshot of your routing window.

Here you are !

Go to services ->Restart Audio Service and Windows Audio Endpoint Builder and check if it fixed the issue.

did you change the ASIO driver while your audio app was open? the ASIO drivers need to be in place BEFORE opening your sequencer.

also, we cannot see which ASIO dest module you are using. the ASIO source and dest modules much match and both must be present.

what do your sequencer's audio settings look like?