Topic: Fireface400 fw (win11) computer does not see my sound card.

Hello everyone. can you tell me if there are any chances that I will run fireface400 on a new computer? windows 11. I connect via PCI-e. The power is on, but the computer does not see my sound card(.

2 (edited by waedi 2026-01-23 19:40:01)

Re: Fireface400 fw (win11) computer does not see my sound card.

Does the device manager show the PcIe Firewire card or any working Firewire port ?
What exactly is installed on this PCIe ?

What is the driver version you did install ? Should be the 3125 driver. https://rme-audio.de/downloads/driver_fw_win_3125.zip

M1-Tahoe, Madiface Pro, Digiface USB, Babyface silver and blue

Re: Fireface400 fw (win11) computer does not see my sound card.

Is the Fireface 400 known to work or did you just buy it used?

Which mainboard and into which PCIe slot did you install the FW400 card, and what card is this?

Is the FW card visible in Windows Device Manager?
If not, try different PCIe sockets.

The next step is to install the so-called FireWire legacy driver.
If it still doesn't work I would try another FireWire cable.

BR Ramses - HDSPe MADI FX, M-1620 Pro D, 12Mic, UFX III, ADI-2 Pro FS R BE, Nuendo 15, Win10 IoT Ent

4 (edited by stak 2026-01-24 23:02:26)

Re: Fireface400 fw (win11) computer does not see my sound card.

Thanks for the reaction. It's really important to me.

waedi wrote:

Does the device manager show the PcIe Firewire card or any working Firewire port ?
What exactly is installed on this PCIe ?

What is the driver version you did install ? Should be the 3125 driver. https://rme-audio.de/downloads/driver_fw_win_3125.zip

Yes, this is exactly 3125

indeed, the driver for my firewire board was not installed. I just installed it. It is now displayed in the device manager correctly.  CROSS MATCH Technologies 1394 Bus OHCI VIA
But the problem is not solved. The computer still does not see the fireface400.

5 (edited by stak 2026-01-24 23:33:06)

Re: Fireface400 fw (win11) computer does not see my sound card.

ramses wrote:

Is the Fireface 400 known to work or did you just buy it used?

Which mainboard and into which PCIe slot did you install the FW400 card, and what card is this?

Is the FW card visible in Windows Device Manager?
If not, try different PCIe sockets.

The next step is to install the so-called FireWire legacy driver.
If it still doesn't work I would try another FireWire cable.

yes, the fireface 400 is 100% working. it was bought new from me. And the problem only appeared when updating the PC.

mainboard - Micro-Star International Co., Ltd. B850 GAMING PLUS WIFI (MS-7E56)
installed in PCI bus 5 (name card CROSS MATCH Technologies 1394 Bus OHCI VIA)

yes the fw card is visible in the device Manager

driver 3125

on another PC, everything worked with this cable. But maybe it really should be changed.  So far, my PC does not see my fireface400
rme setting does not start.

Re: Fireface400 fw (win11) computer does not see my sound card.

Please don't install proprietary FireWire drivers, the FF requires the standard Windows driver.

Regards
Daniel Fuchs
RME

Re: Fireface400 fw (win11) computer does not see my sound card.

I rolled back to the standard driver. The result is the same. The firewire card supplies power to the fireface400, but the PC still doesn't recognize the fireface400.

8 (edited by ramses 2026-01-25 23:10:45)

Re: Fireface400 fw (win11) computer does not see my sound card.

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

9 (edited by ramses 2026-01-25 13:38:44)

Re: Fireface400 fw (win11) computer does not see my sound card.

stak wrote:
ramses wrote:

Is the Fireface 400 known to work or did you just buy it used?

Which mainboard and into which PCIe slot did you install the FW400 card, and what card is this?

Is the FW card visible in Windows Device Manager?
If not, try different PCIe sockets.

The next step is to install the so-called FireWire legacy driver.
If it still doesn't work I would try another FireWire cable.

1) yes, the fireface 400 is 100% working. it was bought new from me. And the problem only appeared when updating the PC.

2) mainboard - Micro-Star International Co., Ltd. B850 GAMING PLUS WIFI (MS-7E56)
installed in PCI bus 5 (name card CROSS MATCH Technologies 1394 Bus OHCI VIA)

3) yes the fw card is visible in the device Manager
driver 3125

4) on another PC, everything worked with this cable. But maybe it really should be changed.  So far, my PC does not see my fireface400. rme setting does not start.

to 1: so you got a new PC with a new mainboard?

to 2: is it this board? https://geizhals.de/msi-b850-gaming-plu … 83264.html
What happens if you use a different PCIe socket?
If the list on geizhals.de is correct you could try between these three PCIe sockets:
1x PCIe 4.0 x16 (x4) (PCI_E2)
2x PCIe 3.0 x16 (x1) (PCI_E3 + PCI_E4)

BTW, I see no PCI bus 5 on the mainboard, the PCIe Slots on the mainboard are labeled as PCI_E1 - PCI_E4.

to 3: ok, but still I would try the other PCIe sockets and also recommend a BIOS upgrade if none of the PCIe sockets work.
But first try the other PCIe sockets before upgrading the BIOS.

to 4: do you still have the other PC, could you still test/check all components in the other PC? Just to validate, that the PCIe Firewire card or the cable are not damaged.

BR Ramses - HDSPe MADI FX, M-1620 Pro D, 12Mic, UFX III, ADI-2 Pro FS R BE, Nuendo 15, Win10 IoT Ent

Re: Fireface400 fw (win11) computer does not see my sound card.

ramses wrote:
stak wrote:
ramses wrote:

Is the Fireface 400 known to work or did you just buy it used?

Which mainboard and into which PCIe slot did you install the FW400 card, and what card is this?

Is the FW card visible in Windows Device Manager?
If not, try different PCIe sockets.

The next step is to install the so-called FireWire legacy driver.
If it still doesn't work I would try another FireWire cable.

1) yes, the fireface 400 is 100% working. it was bought new from me. And the problem only appeared when updating the PC.

2) mainboard - Micro-Star International Co., Ltd. B850 GAMING PLUS WIFI (MS-7E56)
installed in PCI bus 5 (name card CROSS MATCH Technologies 1394 Bus OHCI VIA)

3) yes the fw card is visible in the device Manager
driver 3125

4) on another PC, everything worked with this cable. But maybe it really should be changed.  So far, my PC does not see my fireface400. rme setting does not start.

to 1: so you got a new PC with a new mainboard?

to 2: is it this board? https://geizhals.de/msi-b850-gaming-plu … 83264.html
What happens if you use a different PCIe socket?
If the list on geizhals.de is correct you could try between these three PCIe sockets:
1x PCIe 4.0 x16 (x4) (PCI_E2)
2x PCIe 3.0 x16 (x1) (PCI_E3 + PCI_E4)

BTW, I see no PCI bus 5 on the mainboard, the PCIe Slots on the mainboard are labeled as PCI_E1 - PCI_E4.

to 3: ok, but still I would try the other PCIe sockets and also recommend a BIOS upgrade if none of the PCIe sockets work.
But first try the other PCIe sockets before upgrading the BIOS.

to 4: do you still have the other PC, could you still test/check all components in the other PC? Just to validate, that the PCIe Firewire card or the cable are not damaged.

1. yes

2. Of the available ones, I have 2 left. But I can't connect to the other one because the coolers are installed. It didn't match physically by design)

3. ok. as one of the options, I'll try. Someday, but not now.

4. on another PC, I have an old motherboard and another full-size FW board. When I'm out of town, I'll try, but I know that everything will work there)

I feel like I'm knocking on the wrong door)
Do you think this method can help me? https://www.youtube.com/watch?v=fojCIdB … mp;index=4