What I’m seeing in winver and update is:

Version 1607 (OS Build 14393.1066)

Update history

2017-05 Update for Windows 10 Version 1607 for x64-based Systems (KB3150513)
Successfully installed on 5/5/2017

2017-05 Update for Windows 10 Version 1607 for x64-based Systems (KB3150513)
Successfully installed on 5/1/2017

Windows 10 Version 1607 for x64-based Systems (KB3150513)
Successfully installed on 4/22/2017

MS is rolling out 1703 in waves.
Maybe the update of the compatibility database on 1607 machines is reassessing the machines on a frequent basis to see who’s next.

wushowhide briefly showed this update only on my Win 10 Pro 32-bits tablet. But when I ran the full Windows Updates, it did not appear, did not download, and never showed up again, not even in wushowhide. On my Win 10 Pro 64-bits Intel NUC, this update has never shown up at all.

Weird!

woody wrote:

On April 24, I wrote in InfoWorld about the new version of 3150513 being pushed onto all versions of Windows.

It’s not being pushed to 1703.

I am glad that I don’t run Windows 10 on any of my production machines. In fact, I am glad that I never tried Windows 10 since the two computers which run Windows 10 at the office frequently have issues ranging from moderate issues to very serious issues. I consider an issue to be serious if, for example, if the Windows 10 computer instantly reboots for no reason and loses two hours ($800) worth of work. This has occurred several times on both of our office’s Windows 10 computers. In comparison, the other 20 or so computers which run Windows 7 are stable as a slab of granite.

KB4015219 for 1511 had not change, only some metadata revise

KB 3150513 appeared last night on my Win 10 Home with metered connection – I checked for updates knowing they wouldn’t auto download on metered connection.

KB 3150513 is already installed from the recent update at Defcon 3.

I have been in the habit of waiting (with most updates) to see if there’s problems before risking it.

I see now we are at Defcon 1 again now – https://www.askwoody.com/2017/ms-defcon-1-beware-of-win10-build-16212/

@gborn is reporting problems with May 2017’s KB3150513:

Windows 10: Issues with May 2017 update #KB3150513
Posted on 2017-06-06 by guenni

Microsoft has released update KB3150513 several times in May 2017 for Windows 10 Anniversary Update (Version 1607) . But it seems, that this update is causing issues on some user machines with Outlook and OneNote 2016, MalwareBytes 3.0, and TeamViewer.

Woody:

I continue to believe that KB 3150513 is for assessing readiness for Creators’ Update (1703).

I am on Windows 10 Home 1607 with all updates through May and my Update History only goes back to 4/30. I show KB 3150513 successfully installed on 4/30, 5/16 and 5/24. From watching my Update History, I believe that those dates may actually be download dates, at least it seems that way for Cumulative Updates.

I also received a message within the past few days that I am being invited to update to Creators Update for the second time; the first time was before rollout began. This makes me suspicious that I will be upgraded sooner than later now.

This is an original Lenovo ThinkPad Yoga S1 with I5 and 8B RAM which I keep on metered connections and, unless I make a mistake, I always put to SLEEP, no SHUTDOWNs or RESTARTs. The graphics is whatever is integrated into the U4200 processor. I suspect that systems without third party graphics chips are being upgraded earlier than others. Does anyone have any evidence for or against this idea?

New version of KB2976978 for Win 8.1 showed up today in my WU as Optional.

I got it twice.  On 5/8 and again on 5/29.  Those dates were selected by me, where I chose to run the Win 10 updates for 2017-04 and 2017-05, respectively.

New update from Jonathan Handler on KB 3150513 (which, interestingly enough is a palindrome – is that intentional?).

I checked 6/14 and 6/15 on the Update History page of Windows Update. It has changed a lot. All entries from 4/30 through 5/24, ending with the entry that KB 3150513 was “Successfully installed on 5/24” are still there.

Now there are NINE (9) newer identical update messages. They are about KB 3150513 (again and again): “Failed to Install on 6/13/2017.”

I wonder what will happen “next” and when “next” will occur.

The metered connection for my local public library is still in place.

That is all for now!

Here is what I’m seeing (I have appended the version after each (KB3150513) based on %WINDIR%\Logs\Dism\dism.log):

Version 1607 (OS Build 14393.1358)

Update history

2017-06 Update for Windows 10 Version 1607 for x64-based Systems (KB3150513) 10.0.4.0
Successfully installed on 6/9/2017

2017-05 Update for Windows 10 Version 1607 for x64-based Systems (KB3150513) 10.0.3.0
Successfully installed on 5/31/2017

2017-05 Update for Windows 10 Version 1607 for x64-based Systems (KB3150513) 10.0.2.1
Successfully installed on 5/24/2017

2017-05 Update for Windows 10 Version 1607 for x64-based Systems (KB3150513) 10.0.1.11
Successfully installed on 5/16/2017

2017-05 Update for Windows 10 Version 1607 for x64-based Systems (KB3150513) 10.0.1.10
Successfully installed on 5/10/2017

2017-05 Update for Windows 10 Version 1607 for x64-based Systems (KB3150513) 10.0.1.10
Successfully installed on 5/5/2017

2017-05 Update for Windows 10 Version 1607 for x64-based Systems (KB3150513) 10.0.1.9
Successfully installed on 5/1/2017

Update for Windows 10 Version 1607 for x64-based Systems (KB3150513) 10.0.1.8
Successfully installed on 4/22/2017

The earliest entry in %WINDIR%\Logs\Dism\dism.log I have for KB3150513 is on 3/31/2017 as version 10.0.1.7.