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

Page 2 - 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,931
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
I appreciate all the help. I cant believe Presonus takes it so lightly. It is not just a mixer. All my gear is connected by cables- each cable is like $20 x 24 channels. If I have to change audio interface, I would have to change cables. They releasing new model mixer that cost $3000. They left 16 channels unchanged, but other 16 need different type of cables. I have all my cables marked- this going to be soooo much work to rewire everything. The new mixer would not fit in place of old. If I go with another company- again- so many things to consider. I have a day job, when I get to my gear, it is time to work on music. And all I do is building and rebuilding this gear. Rebuilt it in 2013 with Presonus. Changing it because I ran out of SATA ports for SSD- I needed system that has larger SSDs. One SSD is like $700. What in the world! Who has money like this?
 
Upvote 0 Downvote
So I reinstalled Windows. And it still not working.

2 things I noticed: this time I did not have Norton Antivirus installed. But when I attempted to open Universal Control first time, I got message, "Windows Firewall disabled access of this program to something..." So I selected "Allow access on all networks" something. I was suspecting something is blocking. I should of disable Windows FireWwall when installing. But I did not know how. I have Windows Defender in tray and I can disable that, but not FW.

When Windows started to install updates, I realized that I should of attempt to install UC before Anniversary update installs. I realized when it already started installing and I did not want to install at the same time. Would it be worth to Re-install Windows again just to try to install this driver before Anniversary update installs? This driver works good on old system that had it installed on Windows 8 and then upgraded to Win 10. I am wondering if it would imitate this scenario.
 
Upvote 0 Downvote
Might be worth a try. I also noticed on one of the forum posts https://forums.presonus.com/viewtopic.php?f=67&t=21188 that wahlerstudios mentions "To get your board alive again you have to make a "factory reset", which means that you have to install firmware again and force the board to renew any stored information inside."
I know that option probably sucks unless you can somehow save any custom settings beforehand to be able to restore after.

Karyn in the same posts mentions "The first thing to check though is the Windows firewire driver... Find the firewire in device manager, un-install it, search for new hardware and allow Windows to re-install it but choose the LEGACY driver option." usually when you search for new hardware Windows just installs the driver if available and doesn't ask you which driver to install.
You could try going to Device Manager than choosing the Firewire device or IEEE 1394 not sure how it shows in Device Manager
Right click on it "Update Driver Software" than "Browse my computer for driver software" than "Let me pick from a list of device drivers on my computer" and see if there is another Firewire/IEEE 1394 driver that could be the Legacy driver that Karyn mentions.
 
Upvote 0 Downvote
Ok, thank you very much. I just noted something weird. My Secure Boot in BIOS shows as Enabled and it is grayed out, so I can not change it. I will start another thread about it, but I don't understand how that happened- I did not update the BIOS. Secure boot is what checks for drivers signature. I know it was disabled, because even system data collection software showed it as disabled and I remember seeing it disabled. But now it says "Enabled", grayed out, has weird options of "Windows UEFI mode" and "Other OS" mode. Other mode supposed to be for OS not supporting Secure Boot, and for some reason Other OS is selected. There also some strange Secure boot keys: PK Management, KEK Management, DB Management and DBX Management. How do I disable Secure Boot again?
 
Upvote 0 Downvote
Not 100% sure of this but if under the Boot section of your bios CSM option is enabled than if I am not mistaken it overrides and disables Secure boot. CSM Enabled=Allows Legacy Boot.
It is strange that you even need it disabled because disabling driver signing for me anyway allowed me to keep secure boot enabled. One of my drivers needs driver signing disabled to work. Driver is for HFS+ For Windows.
 
Upvote 0 Downvote
did you try installing an older version of win 10, install drivers and then upgrade to anniversary? that would let you used unsigned drivers as though you cannot install them on anniversary, it doesn't complain if the drivers already existed in place.
 
Upvote 0 Downvote
Right. This was my next step- to reinstall Windows AGAIN without internet connected, install drivers and then install Presonus. BUT. I did try to disable driver signing in Startup Options and even install with it being disabled and it did not help.
What secure boor does? isn't it only there to check for drivers signature? Strangely- I am almost positive I saw it disabled (unless I confused it with Fast Boot). I never saw any secure boot keys. Also one video says to delete secure keys but I am too scared. See this video: https://www.youtube.com/watch?v=tnOHi0w77bU
 
Upvote 0 Downvote
Secure boot appears to be there to protect from root kits: https://www.howtogeek.com/116569/htg-explains-how-windows-8s-secure-boot-feature-works-what-it-means-for-linux/

You do have fast boot in the bios, I saw it mentioned. I don't think you need to delete keys, just enable CSM should turn secure boot off.
 
Upvote 0 Downvote
It still did not install correctly or not communicating after reinstall.

At this point I am ready to give up on it until Presonus releases update. No, they did not promise. In fact they releasing new mixers in 2 weeks and their tech support and developers team will be busy with new issues and support requests. I guess I am just out of luck. Too bad it is not tax deductible because my main income is not from music.

Now that it not working again, I want to get rid of this driver. Yes, it can be uninstalled but if it does not install correctly- what makes me trust that it will UNinstall correctly? So I am considering to Re-Install Windows AGAIN just to get rid of the driver. Is it overkill? Also Windows acted strange and attempted to Reinstall itself after Windows reinstall was completed (probably just detected USB drive still in the port), but it is concerning- see my other post. Should I reinstall?
 
Upvote 0 Downvote
The other machine that it is working on is now upgraded to Windows 10 correct?
Try backing up the drivers from that machine using Powershel following the instructions here http://www.thewindowsclub.com/export-and-backup-device-drivers-in-windows-10-using-powershell the Powershell command is "Export-WindowsDriver -Online -Destination D:\DriverBackup" replace D:\DriverBackup with the location to a usb thumbdrive. Now on the new machine in Device Manager go to IEEE 1394 Bus host controllers section and Right-click the host controller, and then click "Update Driver Software and select Browse my computer for driver software" now click on browse and go to the USB drive where you backed up your drivers to and select Next and hopefully it will pick up and installed the Firewire driver from the working machine. You can also try this driver for the mixer also.
 
Upvote 0 Downvote
Use that driver as it will work in Windows 10. Try that driver before doing the driver backup thing from above post since it is more likely to allow you to install the legacy driver where my above post it may just say the best driver is already installed.
Also if you go into Device Manager in the machine that is working and expand IEEE 1394 Bus host controllers what does it show as the host controller?
 
Upvote 0 Downvote
After I installed it (if it installed because I don't see anything created in Program files)

After you install the 1394 OHCI Legacy Driver.msi file, follow these steps:
Right-click the Legacy1394.inf file under one of the following paths based on the computer's architecture:
C:\Program Files\1394 OHCI Compliant Host Controller (Legacy)\x86_driver
C:\Program Files\1394 OHCI Compliant Host Controller (Legacy)\x64_driver

I don't have 1394 folder in Program files.

But there was some generic driver on the list of drivers for FW, but it did not have work Legacy in it.

Just like this Generic1394 OHCI compliant host controller (Legacy), but no Legacy. So I don't know if it installed.
 
Upvote 0 Downvote
OMG! It is working!!!

Wow! After 3 full Windows installs! All this trouble over one little thing!

You are genius! Thank you so much for not giving up and putting so much work in to it!

Wow. I don't know how to thank you.

Ok, there still problem- the Window Media Player is still hanging and can not play .wav file that it easily plays with generic audio. But the Universal Control opened with its beauty and I can see the movement on the meters. It also forced me to update Presonus firmware. It was risky not to knowing if it reliably communicates but I did not want to ruin it by massing it up, so I let it update. So now it probably will not work on my old computer, and I did not finish mixing/mastering our last CD. But I will worry about it later. Can not test it yet because I don't have any audio software installed.

So... do you think my Windows installed correctly and it is safe to leave them? (When I installed it this time and it completed- it went to reinstall it again and I aborted install- details in my other thread).

Now I am worrying about Anniversary update. What if it masses it up? So what now? Go on and install Anniversary update, then audio editing software and test it? Thank you.

 
Upvote 0 Downvote
YES! OK so you should know that it is possible for Windows Update to change the driver back on you so if you do an Windows update and it stops working just go back into Device manager and change it back to the legacy driver. Anyways I am so glad to hear this.
 
Upvote 0 Downvote
I don't know what could be going on with Media Player but you could always install MPC Classic and it will play .WAV files as well Groove Music should also play .wav files...
If it doesn't work on old machine you probably will just need to update the UC to the version you are using now.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom