My Saffire interface will not connect after. Running Saffire units on Windows 10. The Windows 7 Firewire driver over to Windows 10 solves. Windows 10 Compatibility. Saffire firewire range (Pro 14, Pro 24, Pro 24 DSP, Pro 26, Pro 40, LS 56) Works with Windows 10?

Applies to: Saffire (whole range) We have become aware of a connectivity issue some users are experiencing running Saffire units on Windows 10 connected to FireWire cards with a VIA chipset. Our investigation has shown that this would appear to be an incompatibility with particular PCI/PCIe cards with Windows 10 in combination with specific incompatibilities between certain FireWire chipsets and some modern motherboards. Please note that this issue does not affect all systems and it appears to affect FireWire 400 PCI cards more than FireWire 800 PCI/PCIe cards. The best solution to this issue is to change to a different FireWire card. We recommend cards with the Texas Instruments XIO2213B chipset or the LSI/Agere FW643 chipset as outlined in A couple of alternative solutions may or may not work depending on your system: 1 - If using a PCIe Firewire card, if you feel comfortable doing so, you may be able to change the generation of the PCIe port in your PCs BIOS from ‘Auto’ to ‘1’.

2 - Some users have reported that migrating the Windows 7 Firewire driver over to Windows 10 solves the problem for VIA chipset cards, this suggests an issue between Windows 10 and VIA chipsets specifically, however this has not been confirmed. If you have any queries.

Hi, I work for a few years with the with no problems connected to a Windows 7 computer. Since I have the latest version of Saffire Mix Control 3.6 i get into trouble with Audio glitches.

Example: If Mix Control is running, and for example i play a audio file with Windows Media Player then i have audio glitches in my audio signal. If close Mix Control then the audio glitches are gone. When I start working with my DAW then the audio glitches are much worse.

In version 3.4 i had no troubles. If you install Mix Contro version 3.6 it will install a new firmware in to your.

It is not possible to downgrade the firmware version to the point when it whas working good. The works perfectly on my Mac with the latest version Mix Control 3.6. After further investigation I discovered that if I deinstall my video drivers of my AMD 7060 HD Radeo the audio glitches are gone.

All is working perfectly. I removed the AMD HD 7060 Radeo from my PC. And temporarily turned my onboard GPU of my motherboard on. When I test the same tings like i measured then I have no problems with audio creaks.

Maybe useful to know for those that have similar problems. Hi, first time posting Saffire pro 40 stopped working when I upgraded to windows 10. I had ZERO issues with windows 7 and saffire pro 40 interface. The PC just wont see the interface and ask that it be turned on, or to check connectivity. ( Note: the FW active light on front of interface would not turn on) After days of trouble shooting I discovered the following. Windows 8 up thru 10 DO NOT include IEEE-1394 host control in the LEGACY version. Gigabyte Drivers Windows 10 64 Bit more.

It's completely left out for some unknown reason by Microsoft. Apparantly the IEEE 1394 Legacy driver is the only driver that will work with Saffire interface and PC. There doesn't seem to be a problem with Windows upgrades except for the audio and some video interface users.

After numerous attempts to download and install the legacy IEEE 1394 with no success, I learned that Windows 8-10 actually ' Blocks' this driver from being installed in Windows 8-10. Reading informative post, I tried many tips and tricks. Nothing worked to restore my connection to the Saffire Pro 40 short of making hardware changes. I also was informed of possible chipset issues of which did not pan out. Strange, but during these attempts the FW active light came on; and remains on, allowing me to control volume while viewing YT and video post on social media using only the physical control knob on the Saffire Pro 40, the MIX Control remained unusable, and PC continues to indicate NO CONNECTIVITY.

The mere fact that I have common volume control via the Saffire pro 40 its self is proof the FW its self is good and the PC can see the interface but will not see the MIX Control. I re-Installed the MIx Control software, again after numerous attempts, no success. Same pop ups; not connected check connection or turn on interface. I noticed many folk's found the only solution was to DE-INSTALL their windows update and return to windows 7. They advised it worked and would wait til Focusrite resolved the issue before upgrading. I De-INSTALLED windows 10 via microsofts prompt box and strangly it reverted only to Windows 8.1. Intel Centrino Wireless N 1000 Windows 10 Driver here.

The IEEE1394 Legacy driver failed to show back up as promised, and again no success in connecting with the interface. Windows 7 seems to be a complete loss, as I can't seem to get back to it. I no longer have the CD to re-install it.

I'm completely at a loss as to what step to take from here. I do not desire to make hardware changes. The Darn thing was working like a charm before the upgrade, PERIOD. Now I'm in cyber hell trying to get back to creative work. I believe that Microsoft as well as Focusrite should have foreseen this issue and made every effort to head it off before releasing the upgrade.

Focusrite could have beta tested the upgrades effects on PC users the moment it was released and started working on fixes etc. After all how many PC based audio interface users are there? Any ways, hope someone can help out. Hi Mike, Apologies that you seem to be having some problems. It's worth noting that the Legacy Firewire (IEEE) driver that has been omitted from Windows 10 by Microsoft is only needed for our older legacy Saffires (Pro 10 i/o, Pro 26 i/o, etc).

It is not needed for the Saffire Pro 40, and the newer range of Saffires are tested as supported on Windows 10. We have been made aware of some Firewire card compatibility problems when some users have installed Windows 10, specifically with VIA chipsets and older TI chipsets, we have an answerbase article about that here: At the bottom of that article there is an OHCI tool application that will let you know what IEEE chipset you have installed, this will give us a clearer idea of where the issue might lie. It's also worth letting us know what motherboard make and model you have, as well as ensuring that all chipset and BIOS are recently updated. I hope the above helps, you may want to contact us directly with the above information so we can help you in our support ticket system as opposed to here on the forum: Let me know how you get on. Simon // Focusrite Technical Support [ Post last edited on at 07:44:22 ] • • • • • • • • 2 • •.