Driver not working because Windows 10 inforced secure drivers signing- any work around?

Page 3 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
Astralv

Astralv

Distinguished
May 6, 2013
1,946
11
20,015
My $2000 Fire Wire audio interface (Presonus StudioLive 24,4.2 mixer) does not work on newly built Kaby Lake system. We have tried everything. The system recognizes the hardware, the driver gets installed but no connection to the audio interface. The tech support says- this is because Microsoft started to inforce driver signing this January and the drivers that were installed on Windows 8 upgraded to Windows 10 will still work but would not install on the new Windows 10. It is devastating because I don't have another 2K to spend to replace it. They signed all drivers from the model next to my, but my driver is still not signed. It only supposed to be an issue when Secure Boot enabled, but my Secure Boot is disabled. Why do I still have problem and is there any work around? Thank you.
 
Sort by date Sort by votes
If the other machine has the Anniversary update installed than it should be fine to update just keep in mind how to change the driver to the legacy driver in Device Manager.
Windows Media Player probably isn't as the default app for Audio file so go to Settings, System, Default Apps and choose "set defaults by app" and select Windows Media Player. You now have to options Option one will set it to be the default app for all the file types it can handle or option two will allow you to select defaults by file type/extensions.
 
Upvote 0 Downvote
No- WMP does not work when Presonus set to Output- it just hanging, nut it playing when Dell monitor speakers selected as output device. I have to install my audio software to see if the issue solved because in the past with non-legacy driver, it was not able to play audio (and this is what it there for). Will update. Now- sorry for forcing it, but what you think about my Windows install- did it fully installed? I am thinking to reinstall it again. See this: http://www.tomshardware.com/forum/id-3343980/win10-install-completed-wanted-install-restarted.html
 
Upvote 0 Downvote
I'm not sure what could have happened. It could be that maybe during the initial install it downloaded the Anniversary update and was going to install it if during the install you connected to your internet. Hard to really say for sure. Now that we figured out the solution to the problem you may want to install the Anniversary edition. I would also skip disabling driver signing.
So Install Windows 10 Anniversary, than all your motherboard drivers. Change the firewire driver to the legacy driver than install the UC driver and mixer software. If the UC driver isn't signed I think Windows will tell you that it blocked an unsigned driver and if that happens that disable driver signing via Advanced Boot menu.
Well thankfully we made progress and I don't see any reason for everything to not work with the Anniversary edition now that you know what the solution is.
 
Upvote 0 Downvote
And it failed again. This time it actually says- the Windows blocked the driver (Presonus Universal Control) from working because it is not signed).

I reinstalled Windows and this time I had it connected.

Can it download Anniversary addition while installing? It has option, "Installing updates", but it took a second to pass that stage, so I doubt it downloaded it. How do I check the version?
 
Upvote 0 Downvote
Right cllck on the speaker icon in the bottom right corner of the taskbar and select Playback devices and check to see if the Presonus is set as the default device. It should probably be set to default under recording as well. Hopefully that will solve output to Presonus. You may also want to change the section under Sounds to No sound for sound schemes. Worse thing would be to be making a record and have a Windows sound end up in the recording because that wasn't changed.
 
Upvote 0 Downvote
OK probably didn't download the Anniversary update. So since it blocked the device hold shift key while click on Restart to bring up the advanced boot menu than choose Troubleshoot, Advanced Options, Startup Options than Restart from the menu that comes up after restart choose Disable driver signing.
Once you reboot the driver should be installed for UC and hopefully the Legacy driver for Firewire is now installed and working.
 
Upvote 0 Downvote
Check if other computer has 1607 installed. If so than we should be able to get it working on new computer with 1607 it is just a matter of getting things set the way it likes.
Anyways I am off to bed. Good luck and I will check back in the morning for any news. Hopefully good news.
 
Upvote 0 Downvote
I just reinstalled Windows AGAIN with Internet disconnected and some how the Windows version installed is 1607. How did it get there? I used that same drive earlier today and it did not install 1607 because I remember it updating and installing that update. Could it get installed on this USB drive?

Yes, it works when drivers signing is disabled but when I restart- it blocks it again- I have to do it every time I start. This will not work. The Legacy driver is still there. It is signing of drivers and 1607 update.

Only this morning it was NOT on my USB.
 
Upvote 0 Downvote
if you can dl the November 2015 version of win 10 and use that installer and then install drivers before letting it upgrade to 1607, then the unsigned drivers will keep working. I know as Samsung had a similar problem with their ssd drivers and they work fine if you upgrade to 1607, but won't install if you try to put them on 1607.

You two are doing good work. I had to crash before as had been awake all night
 
Upvote 0 Downvote
If you still end up having to boot into Advanced boot menu and disable driver signing on each boot I think I found a solution. Download EasyBCD run it and go to the Advanced Settings section and choose the Advanced tab and and select the option "Allow use of unsigned drivers 64-bit Windows" and save settings. Now it should have enforcement permanently disabled.
 
Upvote 0 Downvote


Thank you for the idea. I dont know about this. This is what Secure Boot is for- to disable bootloaders. I dont know if I want to change my bootloader.
 
Upvote 0 Downvote


Actually, they are wrong. Its because they didn't release a version of their drivers signed by Microsoft that this is happening. As I said, Microsoft announced this requirement 1 year before, I think when they released Win 10, so PreSonus are to blame. Sure, the person who received message from Microsoft may have not been right person in company and it might have got lost, but that is no excuse now.

If they don't intend to release a new driver they should make a note on it on web site so others can make own minds up. The longer it goes on, the more likely someone else will have the same problem
 
Upvote 0 Downvote
They should also in that readme for the driver mention that you need to switch to legacy firewire drivers, where to download the drivers and how to properly switch to them.
I don't have a high opinion of some of the people that work the Tech support for some companies as it seems that if the problem and solution isn't in a database they use than some of them are absolutely clueless.
 
Upvote 0 Downvote
I agree with you. The guy that was helping me is actually computer enthusiast- he told me that he also built his music system and that he has the same mixer as I do (or similar) and that he has to constantly disable signing of the drivers- every time he restarts.

Also it bugs me- why, why for the first 2 weeks, I installed driver over and over and it never gave me Signing error, but then when I got Legacy driver- if I install Legacy driver first, then it detects unsigned driver. Not likely. Why did it accept it for 2 weeks?
 
Upvote 0 Downvote
I'm not sure why that would be. I don't think it would be the legacy Firewire driver since one would assume Microsoft would sign there own drivers.
I think with W10 1607 version when you disable driver signing Microsoft must of thought it best to make it temporary when you disable driver signing until next boot. It looks like my machine no longer has it disabled so I guess Paragon update HFS+ and got the recent driver signed and must have re-enabled driver signing.
 
Upvote 0 Downvote
Guys...

It is working!

And I did not have to reinstall Windows. It works with 1607.

Remember, I was keep saying- I changed this setting from "Other OS" in secure boot... Well- this was the problem. I set it back to "Other OS" and it works now and not asking for drivers signing.

I cant believe it- I reinstalled Windows at least 6 times for nothing.

Now I don't know what to do. Should I accept this install or do another new install? This particular install went ok, but it was 3 am and I was not paying attention to what was happening- I just wanted to run installer fast as possible and test it. I did not even install any drivers other than Chipset. I hardly remember any of this. (No, I was not drunk. It just that it is hard to remember details of each install). The significant part of it is that I was not paying attention when installing, it was installed from new installer I downloaded from- hopefully- Microsoft web site to USB drive... and I don't remember what computer I used and if Antivirus was running when I downloaded Windows installer. I am willing to do all over again. Or- not? Please, let me know if I am not being objective. Thank you.

We solved it!
 
Upvote 0 Downvote
What is the chance that Antivirus would affect downloading of installer?
I am thinking- I don't remember installation process and was rushing through it, but if something was wrong- I would remember it, right?

I have Acronis True Image. Is it ok?

It just that this computer will contain hundreds of software titles- small programs of software synths and effects and I will have to register them. After registration, reinstalling them is very difficult. When the system is made, it would take weeks to rebuild again. So if something is not right, it would be harder to fix later. But yeah, you are right- may be I should not fix it if it not broken...
I also need help to find drivers for my NVidia 1060 6gb video card. Will take it to graphics forum. Last time it forced me to install NVidia experience and I don't want to have it. Just need a driver.
 
Upvote 0 Downvote
Like Colif said I would leave well enough alone just make sure you no longer have that problem with Media Player, hopefully it was just a buggy install from before. Install all your Motherboard drivers, GPU etc... Once you do have everything installed definitely use Acronis to image the drive.
If NVidia install does install Experience you can just uninstall that under Settings / System / Apps and features. Well good lucky and happy recording.
 
Upvote 0 Downvote


The install I have now was USB install, so it got to be from Microsoft. I dont remember downloading it, and I dont remember any errors. So may be I should leave it alone and just use it.

 
Upvote 0 Downvote
Just wanted to post update: it is still not working. The UC communicating with hardware mixer, but it can not read Audio. I have all inputs and Outputs set correctly but it does not work. Same as it was before the 10 Windows reinstalls.

The Presonus tech support was questioning our solution. So he was right- it still not working.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom