Focusrite 14 driver download

New AFfiliate

1 Posted on 12/12/ at

Just wanna share after trying all sort of things
My Focusrite Saffire firewire is finally WORKING with Windows 10 Creators Update.
How to do:
Download OHCI Compliant Host Controller {Legacy)from the Windows site.
Install it.
Then set it as driver for your firewire.
Open Windows Powershell (administrator) and type
bcdedit /set testsigning on
This puts your pc in test mode.
Restart computer
Now install saffireexe from focusrite and install.
Windows 10 will not like it, but install anyway after the notification.
Saffire is working now!

Open Windows Powershell (administrator) and type:
bcdedit /set testsigning off
Restart

You're in normal windows mode again
&
Voila!
Now you have your Saffire working under Windows 10

How this helps the many with this issue!
Themanandhismusic

New AFfiliate

2 Posted on 03/17/ at

Works as described and got my Saffire back!

So odd that this 10 year old interface works flawlessly despite the fact that they keep trying to disable it.

Many thanks for posting this.

New AFfiliate

3 Posted on 11/22/ at

Man, I literally registered to say THANK YOU for your post. It brought life back to my long-time cherished Focusrite Saffire device. I bought a VIA based PCIE Firewire card just for this card, to get my sound back. After having installed the legacy firewire windows driver, your guide made my sound card live again!

I wonder why Focusrite don't opensource the driver at least, when they don't want to support it anymore. These cards are a bliss, and having people forced to throw away COMPLETELY FUNCTIONAL sound cards, just because there's no software support, is a huge let down.

Cheers and thank you again!

New AFfiliate

4 Posted on 04/17/ at

Thanks to topic starter.
Very good solution to bring life to very good hardware under Windows
I have to say about Texas Instrument FW cards. They are do not require to change driver to special legacy version. At least, with my card.
Just tested with onboard VIA chip - works too. "Legacy" not required. But not long tested.
Third known firewire chip manufacturer is NEC, but i have no such card to test it too.
Some soundcard manufacturers recommends to change driver to legacy for resolving stability issues.

New AFfiliate

5 Posted on 06/04/ at

Hmmmmm looks like the feature update breaks it again. Gah!

Tried all the things but this time the Saffire will not boot. Will I ever get it working with Windows again? Who knows?

Probably advise against installing the update for the time being

New AFfiliate

6 Posted on 06/10/ at

Quote from Aitchy:

Hmmmmm looks like the feature update breaks it again. Gah!

Tried all the things but this time the Saffire will not boot. Will I ever get it working with Windows again? Who knows?

Probably advise against installing the update for the time being

Hey,

could you get it working already? I'm afraid to install that update now.

New AFfiliate

7 Posted on 06/19/ at

Thanks to the original poster - this totally saved me. It's remarkable to me that this old interface still compares extremely favourably to anything on the market now. In fact, I considered upgrading until I realised that everything else out there is basically the same thing with less outputs!

I have just been through the windows update and it broke it again, but I did manage to fix it. I did the following:

-turn off secure boot/set testsigning on (as before)
-uninstall saffire <--important
-install saffire from saffireexe (say yes to unsigned drivers). The device won't boot when you plug it in, just close the installer and move to the next step.
-go to device manager, you'll see the drivers aren't being used. Right click->update driver, then choose from already installed, and choose >focusrite->saffire. The trick here was that I didn't install drivers for the WDM devices, as these seem to cause the unit to become unresponsive.
-turn testsigning off/turn on secure boot.

Of course without the WDM devices, you'll only be able to access the unit through ASIO. This actually suits me quite well, since I use VB-Audio ASIO Bridge to create a virtual output anyway.

New AFfiliate

8 Posted on 07/01/ at

I had to register to say thanks so much to everyone on this thread! Particularly thanks so much to the OP @themanandhismusic and to @pipemerchant

First to OP for getting me back to being able to use my Saffire after years without it. And subsequently I'd been taken down by the update and tried a reinstall with no joy, I also replaced the Firewire interface with the Texas Instruments XIOB chipset (rather than VIA) to no avail. (recommended here www.cronistalascolonias.com.ar)

But on following @pipemerchant's tips I find my Focusrite is fully operational again - even using the WDM driver! There were different results too: My Saffire booted happily after the reinstall of Saffire and so I didn't need to manually set the driver. Perhaps the more compatible chipset with the reinstall did the trick? I'm just happy to have it back!

Thanks again!

New AFfiliate

9 Posted on 07/12/ at

New AFfiliate

10 Posted on 07/19/ at

Okay, left this be for a while after getting frustrated with it ( I have another interface however it's not as good IMO)

So came back here and followed the advice and instructions and we're back in business. Uninstalling and manually adding/installing the drivers was the key.

Thanks karolyi et al for taking the time to post the instructions

May the saffire live forever!!