Was there a bug in last week’s KB 3150513 “upgrade enabling” patch?

Topic

New Reply

Sure looks like it to me. Günter Born reports that KB 3150513 was re-issued on May 1, for Win10 1607 Anniversary Update only. You may recall that it w
[See the full post at: Was there a bug in last week’s KB 3150513 “upgrade enabling” patch?]

1 user thanked author for this post.

Reply | Quote

Replies

I have it waiting in the wings on all my 1607. I put off the upgrade to CU and updated all of them the week of April Patch Tues. After updating, I cleaned up (Disk Cleanup) and shut down. But KB3150513 didn’t show up until sometime after the updates. It’s been there for a while (the original April Ver). I did not installed it.

2 users thanked author for this post.

woody

Reply | Quote

woody wrote:

Like Günter, I haven’t seen KB 3150513 on my Win10 1607 production machine. The KB article was updated yesterday. I manually downloaded the patch from the Update Catalog, tried to install it, and was informed that it was already installed. What the ?

If you’re running on Creator’s Update, then off course an “Anniversary Update only” patch won’t install on your computer.

This only adds to my claims that Windows10 Creators Update is essentially a different OS from the original Windows10.

Fortran, C++, R, Python, Java, Matlab, HTML, CSS, etc.... coding is fun!
A weatherman that can code

1 user thanked author for this post.

Reply | Quote

I’m not running Creators Update (1703) on my production machine. I’m using 1607, and recommend that folks stay there, until 1703 hits Current Branch for Business.

1 user thanked author for this post.

Reply | Quote

Thanks for clarifying that part.

Still, the fact that there are separate forms of updates depending on which Windows10 you’re running… Windows10AU is essentially a different OS from Windows10CU or the original Windows10

Fortran, C++, R, Python, Java, Matlab, HTML, CSS, etc.... coding is fun!
A weatherman that can code

1 user thanked author for this post.

Reply | Quote

I am set to defer updates so I am still at version 1607.  This KB was installed on my system on May 2nd.

1 user thanked author for this post.

Reply | Quote

Did you have metered connection turned on?

1 user thanked author for this post.

Reply | Quote

No

1 user thanked author for this post.

Reply | Quote

On machines where the re-update has successfully installed, it appears with an unusual text label – a month/year designation:

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

The more info link goes here:

https://support.microsoft.com/en-us/help/3150513/latest-compatibility-definition-update-for-windows

 

~ Group "Weekend" ~

1 user thanked author for this post.

Reply | Quote

Weird! I’ve never seen that. But it’s good – it specifically identifies this version of the patch.

1 user thanked author for this post.

Reply | Quote

woody wrote:

Weird! I’ve never seen that. But it’s good – it specifically identifies this version of the patch.

I sorta like it too, but given what I (think) I know about Microsoft UI standards, it’s likely a bug – the label I mean.  🙂  It may also (check that, it does in WSUS) throw off sorting on long lists.

 

~ Group "Weekend" ~

1 user thanked author for this post.

Reply | Quote

I saw the exact same description when I updated the Win 10 partition on my primarily Linux laptop last night.  I don’t really do much with this install other than update it every couple of months in case I might need it for something eventually, but I did find that his update description was a departure from the usual labeling.

1 user thanked author for this post.

Reply | Quote

Definition = regulary updated

is Windows Defender definition have bugs? maybe 😀

2 users thanked author for this post.

woody

Reply | Quote