Fire-wire audio device not working correctly after Win 10 updates 1903 and 1909

It is confirmed that the problem is on the #MICROSOFT end due to something they did to the default firewire drives and their behaviour  after the 1903 update.  I am using five Universal Audio devices and a Digidesign device, all with exactly the same issue you have encountered on sample rate not locking or BSOD crashes and the only way to solve this is to use the old Windows 10 and not allow any updates at all which requires digging into the system and sacrificing newer plugins and software.  If you have noticed, Universal Audio has a new DAW which is AMAZING but no word has come out for Windows users due to the fact that Microsoft is simply ignoring one of the MOST IMPORTANT CHAINS in the operation which is getting the hardware to work properly with Windows again. Many brands are simply just changing to Apple and not supporting Windows anymore which is terrible because Windows had so many advantages over Mac but it's business and customers/major brands can't just wait for Microsoft to get it together so I guess we'll all just have to say goodbye to Microsoft eventually if the issue is not resolved and the Audio - Visual industry will have to go back to Mac again or switch to Hackintosh which I've heard wonders from already.

So I got back from talking to Microsoft and the answer is NO.  Firewire support is nonexistent in Microsoft since 1903 and won't come back.

You can try installing legacy drivers or keeping your 18xx version of Windows 10 as I did without updating but if you're having issues with your current Win10, you're basically screwed. 

I'm going to download latest version of Win10, install legacy drivers and disable updates to see if it works. Any glitches, just going to opt for Hackintosh and if it's stable/powerful enough, might just do the final switch back to Mac after so many years Windows.

Good luck!

I have tried with XP and Windows 7 with no luck, nor with Windows 10 v1909 or v2004.  Legacy drivers and several others were tried, but nothing works.  It's possible that my camcorder's digital output has died - I don't have any other Firewire devices to test with.  The only option I have at this point is to capture the analog output with a USB dongle, and re-digitize it.  It's not the way I wanted to go, but I'm out of options.

This problem also affects digital camera backs that require firewire support.  I have reverted to build 1809 and it is now working but I am worried that even though I have disabled updates using services.msc the setting will change and I will get clobbered by an automatic update.  I understand firewire support may not be MS's priority but the ability to permanently disable updating is now a necessity for all of those in the same position in all of the industries mentioned in this thread.  :(

Damnm, this has just happened to me with my midas mixing desk & interface,

And I just reinstalled windows so just have a new fresh one which I think is post 1903?

So they just basically broke every firewire device?   ****

Stinks.  The only recourse is to use a restore point to get back to the version that originally worked.  If you did a fresh build you won't have that option.  Microsoft needs to give us the ability to turn off updates permanently or truly manually.

So they just basically broke every firewire device?   ****

This is the thing I find astonishing. Every mid-level professional recording studio, every video editing suite, every photo editing studio, every radio station, podcast studio, theatre company... Thousands upon thousands of companies, studios and freelancers in the creative sector around the world, anyone who was using Windows plus a Firewire device: Microsoft has just shut them all down, with no warning and no compensation. This is absolutely huge, and I'm surprised it hasn't been in more media stories yet. A LOT of people were depending on Microsoft + Firewire for their livelihoods, and MS has screwed them all without any warning, or any kind of help to transition to another system, or even any kind of apology. It's a genuinely sociopathic, reprehensible move by a company that tries to convince us it doesn't do that sort of thing, and I'm wondering when we'll see the first court case.

Even worse, with the 2020 update now even USB devices are starting to fail.. Intentionally it would seem due to the fact that it was working perfectly fine in the older versions..  If that first lawsuit begins, I personally think that MANY backers will support and favor the fact that Windows 10 and Microsoft are just breaking things on purpose and not wanting to support instead of moving on to a different OS and leaving the working Win10 that was sold one way, stay that way working.. With the motherboards and devices that were supported, the way they sold it to thousands of us!!!

Yup! And they´re not planning on fixing anything so they said in the customer service department and threads, it´s just unsopported.

 Instead of leaving the working driver, they literally busted it in the new updates and left it that way.  Now it´s happening with usb 2.0 devices like Mbox2 and the iLock 2 driver which brings a BSOD on startup after installing and was working fine on all other versions of Windows 10.  Microsoft really screwed a lot of us over with this.  I personally am already working in Hackintosh and will buy a Mac pretty soon after 2x years of Windows..

18xx versions work perfectly fine with Firewire devices.  If you can get a hold of that version and disable automatic updates for Windows versions, you should be fine.