• “2017-05 Update for Windows 10 version 1607” KB 3150513 appears over and over again

    Home » Forums » Newsletter and Homepage topics » “2017-05 Update for Windows 10 version 1607” KB 3150513 appears over and over again

    Author
    Topic
    #112937

    I’m seeing it on my main production machine, too. It shows up on the list of installed updates (installed 2 May), but also appeared this morning on th
    [See the full post at: “2017-05 Update for Windows 10 version 1607” KB 3150513 appears over and over again]

    Viewing 12 reply threads
    Author
    Replies
    • #112999

      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
      HP Compaq 6000 Pro SFF PC / Windows 10 Pro / 22H2
      Intel®Core™2 “Wolfdale” E8400 3.0 GHz / 8.00 GB
      • #113117

        I wish that I would get as much detail as you – “EyesOnWindows” – get. Are you on Win10, Win10 Pro or Win10 Enterprise or something else?

        I have to agree that it makes sense that Microsoft is prioritizing Win 1703 installation depending upon ease of installation, which it is learning from KB3150513. This would actually be a rational process. Why would MS keep it secret?

        1 user thanked author for this post.
        • #113170

          I wish that I would get as much detail as you – “EyesOnWindows” – get. Are you on Win10, Win10 Pro or Win10 Enterprise or something else?

          I’m running Windows 10 Pro (just changed my signature to reflect that).

          From the Start Menu, in the lower left, choose
          Settings (Gear icon) > Update & security > Windows Update
          then click on “Update history”.
          I just typed in the first three entries as shown above. The last entry should have started with “Update for” (my typo).

          The 30 last entries in mine are (one of latest patch opera sagas):

          Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4015438)
          Failed to install on 4/8/2017

          Running “WMIC qfe list” in a command prompt lists only the last installation KB3150513 on 5/5/2017.
          I see other patches KB3176936 installed on 8/23/2016 thru KB4015217 installed on 4/12/2017 suggesting that the earliest version of this patch predates 8/23/2016.

          Opening %windir%\WindowsUpdate.log shows:

          Please run the Get-WindowsUpdateLog PowerShell command to convert ETW traces into a readable WindowsUpdate.log.

          When I do that I get WindowsUpdate.log written to the Desktop. Among other things it only contains those last three entries for KB3150513, nothing older.

          Here I’ve hacked the contents of that log down to the essentials for KB3176936:

          2017/04/22 http://au.download.windowsupdate.com/c/msdownload/update/software/updt/2017/04/windows10.0-kb3150513-x64-express_407fcd84879fed4cd904b9a234aaf3f0433f2b14.cab
          2017/04/22 CBS package identity: Package_for_KB3150513~31bf3856ad364e35~amd64~~10.0.1.8
          2017/05/01 http://au.download.windowsupdate.com/c/msdownload/update/software/updt/2017/05/windows10.0-kb3150513-x64-express_d956cd1711d244b95779db4dc23d9db56e8af8ee.cab
          2017/05/01 CBS package identity: Package_for_KB3150513~31bf3856ad364e35~amd64~~10.0.1.9
          2017/05/05 http://au.download.windowsupdate.com/c/msdownload/update/software/updt/2017/05/windows10.0-kb3150513-x64-express_4a1a135808f1594c6010c58d325fc0e3fae85e9a.cab
          2017/05/05 CBS package identity: Package_for_KB3150513~31bf3856ad364e35~amd64~~10.0.1.10

          As you can see the last three entries correspond to versions 8, 9 and 10 of KB3150513.

          HP Compaq 6000 Pro SFF PC / Windows 10 Pro / 22H2
          Intel®Core™2 “Wolfdale” E8400 3.0 GHz / 8.00 GB
          2 users thanked author for this post.
          • #113622

            I have a hypothesis as to why your Update History is different from mine. As you not, you are running on Windows 10 Pro. I am running on Windows 10 (Home). I would not be surprised if there is more detail on Pro than there is on Home. Up to a few months ago, my Windows Update might show 6 or 7 items in the last month. This looks like a subtle “dumbing down” of Settings in Windows 10 Home.

            Am I missing something?

            Other comments?

    • #113000

      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.

      4 users thanked author for this post.
    • #113192

      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!

      -- rc primak

    • #113222

      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.

      Windows 11 Pro version 22H2 build 22621.2361 + Microsoft 365 + Edge

    • #113492

      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.

    • #113520

      KB4015219 for 1511 had not change, only some metadata revise

    • #119020

      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/

    • #119523

      @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.

    • #119559

      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?

      • #119582

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

        I think you are right and the “definitions” contained in it are updated when new information is made available.
        KB3150513 is never offered to the latest release build, which right now is 1703, but to all the previous builds and to Windows 7 and Windows 8.1.

        It is interesting that the 1607 LTSB builds (Windows 10 Enterprise LTSB and Windows Server 2016) are offered the same update, although they are not offered the 1703 upgrade, which is CB/CBB. However, an upgrade in place for Windows 10 LTSB to CB/CBB is supported. Less so for the server, unless/until a newer version will be released.
        I am wondering if there will be a new LTSB planned for the version released after 1703 (known as RS3 or maybe 1711), or KB3150513 is released for the LTSB builds purely for telemetry purpose and statistical analysis.

    • #119570

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

      Antec P7 Silent * Corsair RM550x * ASUS TUF GAMING B560M-PLUS * Intel Core i5-11400F * 4 x 8 GB G.Skill Aegis DDR4 3200 MHz CL16 * Sapphire Radeon 6700 10GB * XPG GAMMIX S70 BLADE 1TB * SanDisk Ultra 3D 1TB * DVD RW Lite-ON iHAS 124 * Windows 10 Pro 22H2 64-bit
    • #119573

      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.

      Windows 10 Pro 22H2

    • #120818

      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!

    • #120930

      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.

      HP Compaq 6000 Pro SFF PC / Windows 10 Pro / 22H2
      Intel®Core™2 “Wolfdale” E8400 3.0 GHz / 8.00 GB
      • #120933

        Perhaps they are scraping off information to direct the upgrading to 1703  CU.

      • #120961

        I wish that I could see what you are referring to in your message. I am technical to a point but I do not know how to convert %WINDIR% to see the fully qualified path for this on my Windows 10 Version 1607 Build 14393.1198, with C: as the partition for the OS.

        Very truly yours,

        Jonathan Handler

        • #120965

          C:\Windows is %WINDIR% is directory where Windows is installed.
          If you have not run DISM for the installed versions, you may not have that .log

          • #121090

            You are right. DISM is a new piece of the puzzle. Can you tell me more, or should I go to support.microsoft.com

            Thanks very much

            Jonathan Handler

            • #121100

              Big topic. You can start here and then Google DISM for more information.

            • #121189

              I will have to dig into this.  I intend ASAP ($) to upgrade from Windows 10 Home to Windows 10 Pro on this system to test the Deferred Channel experience on Windows 10.

              I recently upgrafed my Office 365 account from Business Essentials (using an old, non-updated license for Office 2013 from a former business partner) to Office 365 Business Premium.  I worked with Office 365 support to install it as Deferred Channel because Current Channel is the default installation for Business Premium.

              In September or so , Microsoft will be updating the Deferred Channels for Windows 10 Pro (and I believe Windows 10 Enterprise) and Office 365 Business Premium (and I believe Office 365 Enterprise versions) with a three month cycle instead of a four month cycle, as has been talked about a lot, recently.

              For this primarily work machine, I will be continuing to follow Ask Woody and I will be taking advantage of Deferred Channel as much as possible.

    Viewing 12 reply threads
    Reply To: “2017-05 Update for Windows 10 version 1607” KB 3150513 appears over and over again

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: