Windows 10: March 15th 2017 Update KB3150513 for Windows 10 Version 1607

Compatibility definition update KB3150513 now available via Windows Update for Windows 10 Version 1607.

To manually download:

*Arrow Download KB3150513 from Microsoft Update Catalog

Read more: https://support.microsoft.com/en-us/...te-for-windows

 

Cheers Shawn. Feel free to delete this thread if you want Why has KB3150513 just installed?

:)

 

Microsoft Update KB3150513 installed 5 times in the last 2 months

Thanks for your response.

I have Win10 Version 1607.

For that version there only appears to be one update sent out according to the catalogue.

I put a search in for KB3150513 windows 10.

Whereas this is what I see in my Update History :

------------------------------------------------------------------------------------------------

2017-05 Update for Windows 10 Version 1607 for x64-based Systems (KB3150513)

Successfully installed on 15/05/2017

2017-05 Update for Windows 10 Version 1607 for x64-based Systems (KB3150513)

Successfully installed on 05/05/2017

2017-05 Update for Windows 10 Version 1607 for x64-based Systems (KB3150513)

Successfully installed on 02/05/2017

Update for Windows 10 Version 1607 for x64-based Systems (KB3150513)

Successfully installed on 24/04/2017

Update for Windows 10 Version 1607 for x64-based Systems (KB3150513)

Successfully installed on 16/03/2017

----------------------------------------------------------------------------------------------------

Hence my question : 5 successful installs for the same update!

 

MICROSOFT WINDOWS 10 UPDATE

Various sources are suggesting (at least) that KB3150513 was revised & re-released (Win10 1607 only) three (3) times since 21 Apr-17.

If your list of Installed Updates includes "2017-05 Update for Windows 10 Version 1607 for x64-based Systems (KB3150513)" [vs. “Update for Windows 10 Version 1607 for x64-based Systems (KB3150513)”], you have the most-recent version installed.

 

Seems to add a line under Windows Update.

 

I had that after the CU yesterday. this update didn't change it.

 

Hmm interesting

 

After yesterday's update borked my PC big time I am worried about installing anything else.
Almost ready to give up and format...FML. *Confused

 

I just did this update KB3150513, no need to restart computer *Smile

 

Well, those updates are already installed but the TIWorker is going crazy. with a 64% CPU utilization, maybe it is checking the actual compatibility or installing something.

 

Same problem here...

edit: it stopped by itself after more than one hour

 

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

 

Restarting is taking like a minute when in the past it was in a instant *Sad Just hope this is temporary!


Edit:

Fixed *Smile

Microsoft should make a warning saying: Don't get nervous your precious PC is okay the restart process is taking a little more time but it will be back to normal soon.

 

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