March 15th 2017 Update KB3150513 for Windows 10 Version 1607

Same effect here. TIWorker is writing lots of stuff to c:\Windows\WinSxS\Temp\InFlight

KB3150513 broke my MOTU audio.

I have a MOTU UltraLite external IEEE-1394 audio interface (plugged into an add-in card, no native 1394 on my mobo). I was capturing some video with audio today using a different IEEE-1394 device plugged into a different port on the same card (I've been doing this for days without a snag), and suddenly the sound went silent. The audio was still making it from the source device to the capture program, but it was not making it back out to the speakers through the UltraLite.

Inputs into the UltraLite showed signal levels on the front panel, but I could not get the sound successfully routed to the speaker outputs using the front panel controls. I opened MOTU's console app, and every time I changed a setting in the interface it reverted back to 0 or Disabled, depending on the setting. It looked like a software problem was forcing bad settings in the application, rather than being a hardware problem.

I had been running a slightly older driver from MOTU (v4.0.5.9644 (Release Date 2014-01-03)), so I clean-installed the newest driver (v4.0.6.6814 (Release Date 2015-10-28)) from their site. It had no effect on the problem.

I also checked my cables and the add-in card drivers. Then it occurred to me to check for recent Windows update installations, and guess what? I found that update KB3150513 had installed itself just prior to the audio output problem.

I did a system restore to before the update, and the audio came back. So yeah, the update somehow broke my MOTU audio drivers.

It might be foolish to hope either MS or MOTU would notice and/or fix this since it's old Firewire equipment, but apart from the interface it's a perfectly good device that would cost hundreds of dollars to replace.

Windows Update KB3150513 seems to have been released earlier in May and September 2016. I have installed it and all seems OK but it is still unnerving as Microsoft does not explain clearly what it does! At first it was released for Windows 8.1 as explained here; Mystery solved: KB 3150513 is another Windows 10 update-enabling patch | InfoWorld

KB3150513 automatic install today via normal update / nothing visible

dalchina said:

This is odd: I had this installed on 16/3/17, then about 9 other updates, the last being 4015217, then KB3150513 installed again on 22/4/17 and 2/5/17. My build number is 14393.1066.

same here. Not sure why MS keeps sending this down the pipe. Looks like it's only for anniversary edition machines and related to diagnostics

OldMike65 said:

Same as you guys KB3150513 has been installed 3 times for me .....guess MS wants to make sure we got it.

I feel left out. They offered it to me only once.