RME Support wrote:Please don't install proprietary FireWire drivers; the FireFace requires the standard Windows driver.
Daniel, I was confused on this topic, as I have not used FireWire since many years.
So at first I didn't understand your statement, as I thought that there is still something like a Firewire legacy driver.
But this doesn't seem to be the case anymore.
Question: Are the following findings from the internet ok?
It’s been a long time since I used FireWire with the UFX. Under Windows 7, you had to open Device Manager, go to the driver properties of the FireWire card, and select the "legacy driver" (Legacy 1394 OHCI driver).
Reason: Many audio interfaces and DV capture apps worked more reliably with the legacy stack because the standard inbox driver had issues with certain controllers and device protocols, leading to dropouts, disconnects, or enumeration failures. This is why guides from various manufacturers recommended switching to the legacy driver in Windows 7.
If I recall correctly, Microsoft removed the legacy 1394 bus drivers (1394bus.sys, Ochi1394.sys) from the default install in Windows 8/8.1 and later, so you had nothing to select in many systems unless you manually installed older drivers.
There used to be a third-party webpage explaining how to download and install the legacy FireWire driver on Windows 8, 10, and possibly 11. Last time I checked (about a year ago), that page was no longer available.
What exactly do you mean by “do not install proprietary FireWire drivers”? My understanding was that the original Microsoft legacy driver simply wasn’t bundled with Windows anymore and that it could be downloaded via the URL from that page.
On internet I found the following informations:
1. that no official Microsoft “FireWire legacy driver for Windows 11” page currently exists. The most reliable method historically was extracting the legacy driver from older Microsoft standalone packages and installing through Device Manager, but that is not guaranteed to work on Windows 10/11 due to driver signing and OS integration changes.
2. Third‑party driver download sites claim to host IEEE‑1394 drivers for Windows 10/11, but these are not official Microsoft drivers; using them risks compatibility/stability issues and may not work due to driver signing and Windows security
3. Windows 11 would still enumerate and use some IEEE‑1394 functionality via the standard built‑in 1394 host controller driver that Windows provides. Is this the reason why RME is telling users not to install third‑party/proprietary FireWire drivers but to use the firewire driver which is included in Windows 11?
In short: with Windows 11 there is no other choice than to stick to the Firewire driver which is bundled with Win11.
Either it works or not and if Microsoft would cease Firewire support entirely, then you can't use firewire anymore.
Is the current status correctly summarized by this?
BR Ramses - HDSPe MADI FX, M-1620 Pro D, 12Mic, UFX III, ADI-2 Pro FS R BE, Nuendo 15, Win10 IoT Ent