none
September Cumulative Updates for Windows10 - KB3185611 for the original release, KB3185614 for 1511 (November Update), KB3189866 for 1607 (Anniversary Update) RRS feed

  • General discussion

  • And we're back yet again!

    We saw fewer update install issues in August, which is great news. What are you seeing in September? Let me know.

    Many thanks!

    John Wink [MSFT]

    Tuesday, September 13, 2016 5:56 PM

All replies

  • I am (was) at 1511 10586.545, ran Windows update, went into long install of "feature update Win 10 ver 1607" which failed and restored 1511 10586.545. Used Hide/Show app to hide "feature update Win 10 ver 1607". Hide/Show app shows lots of 1511 updates avail. Best way to proceed ?
    Tuesday, September 13, 2016 6:04 PM
  • I am (was) at 1511 10586.545, ran Windows update, went into long install of "feature update Win 10 ver 1607" which failed and restored 1511 10586.545. Used Hide/Show app to hide "feature update Win 10 ver 1607". Hide/Show app shows lots of 1511 updates avail. Best way to proceed ?
    That's odd. What 1511 updates are available? If you were on 10586.545 then you were on the latest update for the 1511 release. Thanks!
    Tuesday, September 13, 2016 6:18 PM
  • I am (was) at 1511 10586.545, ran Windows update, went into long install of "feature update Win 10 ver 1607" which failed and restored 1511 10586.545. Used Hide/Show app to hide "feature update Win 10 ver 1607". Hide/Show app shows lots of 1511 updates avail. Best way to proceed ?

    That's odd. What 1511 updates are available? If you were on 10586.545 then you were on the latest update for the 1511 release. Thanks!

    KB3185614 (cumulative update) Softpedia says it will update to OS Build 10586.589)

    http://news.softpedia.com/news/what-s-new-in-windows-10-cumulative-updates-kb3189866-kb3185614-and-kb3185611-508261.shtml

    There is also KB3161102, KB3181403 and 9 others (Office, etc.)

    Should I try WinUpdate again with "feature update Win 10 ver 1607" hidden or work with you to try to debug "feature update Win 10 ver 1607" ?

    Tuesday, September 13, 2016 6:42 PM
  • I am (was) at 1511 10586.545, ran Windows update, went into long install of "feature update Win 10 ver 1607" which failed and restored 1511 10586.545. Used Hide/Show app to hide "feature update Win 10 ver 1607". Hide/Show app shows lots of 1511 updates avail. Best way to proceed ?

    That's odd. What 1511 updates are available? If you were on 10586.545 then you were on the latest update for the 1511 release. Thanks!

    KB3185614 (cumulative update) Softpedia says it will update to OS Build 10586.589)

    http://news.softpedia.com/news/what-s-new-in-windows-10-cumulative-updates-kb3189866-kb3185614-and-kb3185611-508261.shtml

    There is also KB3161102, KB3181403 and 9 others (Office, etc.)

    Should I try WinUpdate again with "feature update Win 10 ver 1607" hidden or work with you to try to debug "feature update Win 10 ver 1607" ?

    10586.589 is today's update, I suggest seeing if that installs correctly (and feel free to take those other updates too). If you want to try 1607 again after that, we can try and figure out why it fails. Thanks!
    Tuesday, September 13, 2016 6:45 PM
  • I am (was) at 1511 10586.545, ran Windows update, went into long install of "feature update Win 10 ver 1607" which failed and restored 1511 10586.545. Used Hide/Show app to hide "feature update Win 10 ver 1607". Hide/Show app shows lots of 1511 updates avail. Best way to proceed ?

    That's odd. What 1511 updates are available? If you were on 10586.545 then you were on the latest update for the 1511 release. Thanks!

    KB3185614 (cumulative update) Softpedia says it will update to OS Build 10586.589)

    http://news.softpedia.com/news/what-s-new-in-windows-10-cumulative-updates-kb3189866-kb3185614-and-kb3185611-508261.shtml

    There is also KB3161102, KB3181403 and 9 others (Office, etc.)

    Should I try WinUpdate again with "feature update Win 10 ver 1607" hidden or work with you to try to debug "feature update Win 10 ver 1607" ?

    10586.589 is today's update, I suggest seeing if that installs correctly (and feel free to take those other updates too). If you want to try 1607 again after that, we can try and figure out why it fails. Thanks!
    Now up to date at 10586.589. What new features are available with 1607 ? I suspect the failure to install with roll back is Nvidia driver issue again. It will probably install if I disable the device. I am worried about loosing the only driver that works with win 10 (a not the latest modified by Microsoft). Might try 1607 at a later time.
    Tuesday, September 13, 2016 7:28 PM
  • I am (was) at 1511 10586.545, ran Windows update, went into long install of "feature update Win 10 ver 1607" which failed and restored 1511 10586.545. Used Hide/Show app to hide "feature update Win 10 ver 1607". Hide/Show app shows lots of 1511 updates avail. Best way to proceed ?

    That's odd. What 1511 updates are available? If you were on 10586.545 then you were on the latest update for the 1511 release. Thanks!

    KB3185614 (cumulative update) Softpedia says it will update to OS Build 10586.589)

    http://news.softpedia.com/news/what-s-new-in-windows-10-cumulative-updates-kb3189866-kb3185614-and-kb3185611-508261.shtml

    There is also KB3161102, KB3181403 and 9 others (Office, etc.)

    Should I try WinUpdate again with "feature update Win 10 ver 1607" hidden or work with you to try to debug "feature update Win 10 ver 1607" ?

    10586.589 is today's update, I suggest seeing if that installs correctly (and feel free to take those other updates too). If you want to try 1607 again after that, we can try and figure out why it fails. Thanks!

    Now up to date at 10586.589. What new features are available with 1607 ? I suspect the failure to install with roll back is Nvidia driver issue again. It will probably install if I disable the device. I am worried about loosing the only driver that works with win 10 (a not the latest modified by Microsoft). Might try 1607 at a later time.

    Here you go! :-) https://www.microsoft.com/en-US/windows/features
    Tuesday, September 13, 2016 8:18 PM
  • I am (was) at 1511 10586.545, ran Windows update, went into long install of "feature update Win 10 ver 1607" which failed and restored 1511 10586.545. Used Hide/Show app to hide "feature update Win 10 ver 1607". Hide/Show app shows lots of 1511 updates avail. Best way to proceed ?

    That's odd. What 1511 updates are available? If you were on 10586.545 then you were on the latest update for the 1511 release. Thanks!

    KB3185614 (cumulative update) Softpedia says it will update to OS Build 10586.589)

    http://news.softpedia.com/news/what-s-new-in-windows-10-cumulative-updates-kb3189866-kb3185614-and-kb3185611-508261.shtml

    There is also KB3161102, KB3181403 and 9 others (Office, etc.)

    Should I try WinUpdate again with "feature update Win 10 ver 1607" hidden or work with you to try to debug "feature update Win 10 ver 1607" ?

    10586.589 is today's update, I suggest seeing if that installs correctly (and feel free to take those other updates too). If you want to try 1607 again after that, we can try and figure out why it fails. Thanks!

    Now up to date at 10586.589. What new features are available with 1607 ? I suspect the failure to install with roll back is Nvidia driver issue again. It will probably install if I disable the device. I am worried about loosing the only driver that works with win 10 (a not the latest modified by Microsoft). Might try 1607 at a later time.


    Here you go! :-) https://www.microsoft.com/en-US/windows/features
    Windows Update now downloading KB3140743 (March Update).
    Tuesday, September 13, 2016 10:07 PM
  • I am (was) at 1511 10586.545, ran Windows update, went into long install of "feature update Win 10 ver 1607" which failed and restored 1511 10586.545. Used Hide/Show app to hide "feature update Win 10 ver 1607". Hide/Show app shows lots of 1511 updates avail. Best way to proceed ?

    That's odd. What 1511 updates are available? If you were on 10586.545 then you were on the latest update for the 1511 release. Thanks!

    KB3185614 (cumulative update) Softpedia says it will update to OS Build 10586.589)

    http://news.softpedia.com/news/what-s-new-in-windows-10-cumulative-updates-kb3189866-kb3185614-and-kb3185611-508261.shtml

    There is also KB3161102, KB3181403 and 9 others (Office, etc.)

    Should I try WinUpdate again with "feature update Win 10 ver 1607" hidden or work with you to try to debug "feature update Win 10 ver 1607" ?

    10586.589 is today's update, I suggest seeing if that installs correctly (and feel free to take those other updates too). If you want to try 1607 again after that, we can try and figure out why it fails. Thanks!

    Now up to date at 10586.589. What new features are available with 1607 ? I suspect the failure to install with roll back is Nvidia driver issue again. It will probably install if I disable the device. I am worried about loosing the only driver that works with win 10 (a not the latest modified by Microsoft). Might try 1607 at a later time.


    Here you go! :-) https://www.microsoft.com/en-US/windows/features

    Windows Update now downloading KB3140743 (March Update).

    Windows Update trying to download/install old update is similar to what I reported last month (minor annoyance).

    Tried "feature update Win 10 ver 1607" again after successful update to 10586.589 (takes about one hour, 25 minutes), again it failed and rolled back.

    Will try third time with Nvidia Graphics Adapter disabled and will post results.

    Tuesday, September 13, 2016 11:31 PM
  • I am (was) at 1511 10586.545, ran Windows update, went into long install of "feature update Win 10 ver 1607" which failed and restored 1511 10586.545. Used Hide/Show app to hide "feature update Win 10 ver 1607". Hide/Show app shows lots of 1511 updates avail. Best way to proceed ?

    That's odd. What 1511 updates are available? If you were on 10586.545 then you were on the latest update for the 1511 release. Thanks!

    KB3185614 (cumulative update) Softpedia says it will update to OS Build 10586.589)

    http://news.softpedia.com/news/what-s-new-in-windows-10-cumulative-updates-kb3189866-kb3185614-and-kb3185611-508261.shtml

    There is also KB3161102, KB3181403 and 9 others (Office, etc.)

    Should I try WinUpdate again with "feature update Win 10 ver 1607" hidden or work with you to try to debug "feature update Win 10 ver 1607" ?

    10586.589 is today's update, I suggest seeing if that installs correctly (and feel free to take those other updates too). If you want to try 1607 again after that, we can try and figure out why it fails. Thanks!

    Now up to date at 10586.589. What new features are available with 1607 ? I suspect the failure to install with roll back is Nvidia driver issue again. It will probably install if I disable the device. I am worried about loosing the only driver that works with win 10 (a not the latest modified by Microsoft). Might try 1607 at a later time.


    Here you go! :-) https://www.microsoft.com/en-US/windows/features

    Windows Update now downloading KB3140743 (March Update).

    Windows Update trying to download/install old update is similar to what I reported last month (minor annoyance).

    Tried "feature update Win 10 ver 1607" again after successful update to 10586.589 (takes about one hour, 25 minutes), again it failed and rolled back.

    Will try third time with Nvidia Graphics Adapter disabled and will post results.

    Windows update no longer presents "feature update Win 10 ver 1607", says I am up to date, tried "Windows 10 Upgrade 10 Assistant". It told me 10586 is not the latest build, click continue to install 14393, which fails and rolls back (with Nvidia disabled), might try again with Nvidia uninstalled.
    Wednesday, September 14, 2016 12:55 AM
  • I am (was) at 1511 10586.545, ran Windows update, went into long install of "feature update Win 10 ver 1607" which failed and restored 1511 10586.545. Used Hide/Show app to hide "feature update Win 10 ver 1607". Hide/Show app shows lots of 1511 updates avail. Best way to proceed ?

    That's odd. What 1511 updates are available? If you were on 10586.545 then you were on the latest update for the 1511 release. Thanks!

    KB3185614 (cumulative update) Softpedia says it will update to OS Build 10586.589)

    http://news.softpedia.com/news/what-s-new-in-windows-10-cumulative-updates-kb3189866-kb3185614-and-kb3185611-508261.shtml

    There is also KB3161102, KB3181403 and 9 others (Office, etc.)

    Should I try WinUpdate again with "feature update Win 10 ver 1607" hidden or work with you to try to debug "feature update Win 10 ver 1607" ?

    10586.589 is today's update, I suggest seeing if that installs correctly (and feel free to take those other updates too). If you want to try 1607 again after that, we can try and figure out why it fails. Thanks!

    Now up to date at 10586.589. What new features are available with 1607 ? I suspect the failure to install with roll back is Nvidia driver issue again. It will probably install if I disable the device. I am worried about loosing the only driver that works with win 10 (a not the latest modified by Microsoft). Might try 1607 at a later time.


    Here you go! :-) https://www.microsoft.com/en-US/windows/features

    Windows Update now downloading KB3140743 (March Update).

    Windows Update trying to download/install old update is similar to what I reported last month (minor annoyance).

    Tried "feature update Win 10 ver 1607" again after successful update to 10586.589 (takes about one hour, 25 minutes), again it failed and rolled back.

    Will try third time with Nvidia Graphics Adapter disabled and will post results.

    Windows update no longer presents "feature update Win 10 ver 1607", says I am up to date, tried "Windows 10 Upgrade 10 Assistant". It told me 10586 is not the latest build, click continue to install 14393, which fails and rolls back (with Nvidia disabled), might try again with Nvidia uninstalled.

    Fourth attempt (to upgrade to 14393 via "Windows 10 Upgrade 10 Assistant" with Nvidia uninstalled) also failed and rolled back and major difficulties on rollback I guess due to uninstalled Nvidia (many BSOD with VMMI (VIRTUAL_MEMORY_MANAGEMENT_INTERNAL) crashes. Got it to stop by installing an old driver in safe mode and when examining old driver with Device Manager after restart in normal mode, MAGIC HAPPENED and I have a new driver with Microsoft mod (UGLY version 2.1 Build_223) but I'm still at 1511 10586.589, not 1607 or 14393. Also: My manual restore points have disappeared (deleted by upgrade attempt ?)



    • Edited by Mighty Tiger Wednesday, September 14, 2016 5:35 AM
    Wednesday, September 14, 2016 4:26 AM
  • What are you seeing in September? Let me know.

    Many thanks!

    John Wink [MSFT]

    John,

    Any comment on the other posts in this forum regarding the CU stalling at "downloading 45%"?  I had this on just 1 of 7 PC's and resolved it through the standard workaround of stopping services, deleting folders under SoftwareDistribution, re-starting services, and repeating update.  Others are apparently finding quicker results by just installing from Update Catalog.

    Thanks...

    Wednesday, September 14, 2016 2:18 PM
  • What are you seeing in September? Let me know.

    Many thanks!

    John Wink [MSFT]

    John,

    Any comment on the other posts in this forum regarding the CU stalling at "downloading 45%"?  I had this on just 1 of 7 PC's and resolved it through the standard workaround of stopping services, deleting folders under SoftwareDistribution, re-starting services, and repeating update.  Others are apparently finding quicker results by just installing from Update Catalog.

    Thanks...


    I heard a number of cases of this overnight, I'm checking into it this morning. Might need some logs from you, is that okay? Thanks!
    Wednesday, September 14, 2016 2:26 PM
  • I heard a number of cases of this overnight, I'm checking into it this morning. Might need some logs from you, is that okay? Thanks!

    Yes on sending logs but I have infrequent access to the one PC so may take some time.

    Some other observations that might help:  update was successful first time on both 32-bit and 64-bit installs but the one that failed was a 64-bit.  It was also the only one that is still an upgrade from Win7 to Win10 (7 to 1511 to 1607).  All others had been upgraded but then subsequently clean installed.  Also, prior to my workaround on the one, I tried rebooting to see if it would complete but instead it found an update for Silverlight (KB3182373) that was not listed with the first set and installed it before showing the CU again stuck at 45%.  Almost had the feeling that the Silverlight download was somehow interrupting the initial download (probably just coincidental).  None of the other six PC's had Silverlight installed since they were clean installs.  I have now removed Silverlight from the problem PC since I don't really need it.

    Wednesday, September 14, 2016 2:46 PM
  • I heard a number of cases of this overnight, I'm checking into it this morning. Might need some logs from you, is that okay? Thanks!

    Yes on sending logs but I have infrequent access to the one PC so may take some time.

    Some other observations that might help:  update was successful first time on both 32-bit and 64-bit installs but the one that failed was a 64-bit.  It was also the only one that is still an upgrade from Win7 to Win10 (7 to 1511 to 1607).  All others had been upgraded but then subsequently clean installed.  Also, prior to my workaround on the one, I tried rebooting to see if it would complete but instead it found an update for Silverlight (KB3182373) that was not listed with the first set and installed it before showing the CU again stuck at 45%.  Almost had the feeling that the Silverlight download was somehow interrupting the initial download (probably just coincidental).  None of the other six PC's had Silverlight installed since they were clean installs.  I have now removed Silverlight from the problem PC since I don't really need it.

    Thanks for the additional info, this could help. :-)

    When you get a sec, please download the copylogs tool from my OneDrive, run it from an Administrator command prompt, and then upload the logs to the TechNet folder on the same OneDrive. Many thanks in advance!

    OneDrive is here: https://1drv.ms/f/s!AtwXjrnjoGBml2txQtByBKq8_Yrj

    Wednesday, September 14, 2016 3:30 PM
  • Here you go! :-) https://www.microsoft.com/en-US/windows/features

    That page looks atrocious (and is mostly dysfunctional) in IE.  Much better looking and performing in Edge.

    Apparently I am still using the August update for 1607.

    Ah.  It's the Microsoft Compatibility List!  Unchecking that makes it look and act much better--similar to Edge.   <LOL/>



    Robert Aldwinckle
    ---

    Wednesday, September 14, 2016 5:31 PM
  • Here you go! :-) https://www.microsoft.com/en-US/windows/features

    That page looks atrocious (and is mostly dysfunctional) in IE.  Much better looking and performing in Edge.

    Apparently I am still using the August update for 1607.

    Ah.  It's the Microsoft Compatibility List!  Unchecking that makes it look and act much better--similar to Edge.   <LOL/>



    Robert Aldwinckle
    ---


    No comment. :-)
    Wednesday, September 14, 2016 6:23 PM
  • as my update is also hanging at 48% on  KB3189866, I uploaded my logs, too.
    Wednesday, September 14, 2016 6:47 PM
  • as my update is also hanging at 48% on  KB3189866, I uploaded my logs, too.

    Great, thanks!
    Wednesday, September 14, 2016 6:50 PM
  • KB3185614 failed at 95% (or maybe it was 98%?) and rolled back. Running Win 10 Pro 1511 10586.545 on an ACPI x64 PC w/ Intel HG Graphics 3000. Win 10 Pro was installed as an upgrade from Win 7 Pro. 

    Seems a replay of the failed KB3140745 Cumulative Update failure experienced back in March 2016. In that episode, after multiple roll-backs at 98%, I hid the culprits. Two months later in May 2016, cumulative update KB3163018 successfully installed. No issues since until today. 

    I uploaded the logs for you: (WULogs-Eileen-OLEANDER-BLUE-20160915-065704.zip)

    Thursday, September 15, 2016 2:29 PM
  • my update is also hanging at 48% on  KB3189866  W-10 version 1607.  Have rolled back image several times with same results.

    Also note this on Dell computer which came with W-10 a year ago.
    • Edited by Ensign986 Thursday, September 15, 2016 5:17 PM
    Thursday, September 15, 2016 5:12 PM
  • KB3185614 failed at 95% (or maybe it was 98%?) and rolled back. Running Win 10 Pro 1511 10586.545 on an ACPI x64 PC w/ Intel HG Graphics 3000. Win 10 Pro was installed as an upgrade from Win 7 Pro. 

    Seems a replay of the failed KB3140745 Cumulative Update failure experienced back in March 2016. In that episode, after multiple roll-backs at 98%, I hid the culprits. Two months later in May 2016, cumulative update KB3163018 successfully installed. No issues since until today. 

    I uploaded the logs for you: (WULogs-Eileen-OLEANDER-BLUE-20160915-065704.zip)

    Hi Eileen,

    This one looked a little odd, but I think the following steps should sort you out. Can you give it a try and let me know?

    Open an Administrator command prompt

    1. Net stop bits
    2. Net stop wuauserv
    3. Net stop appidsvc
    4. Net stop cryptsvc
    5. Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat" (quotes and all!)
    6. Del c:\windows\SoftwareDistribution\*.* /s
    7. Net start bits
    8. Net start wuauserv
    9. Net start appidsvc
    10. Net start cryptsvc
    11. Check for Updates and see if it works.

    Thanks!

    John Wink [MSFT]

    Thursday, September 15, 2016 6:41 PM
  • my update is also hanging at 48% on  KB3189866  W-10 version 1607.  Have rolled back image several times with same results.

    Also note this on Dell computer which came with W-10 a year ago.

    Is the installation hanging, or the download? Thanks!
    Thursday, September 15, 2016 6:41 PM
  • as my update is also hanging at 48% on  KB3189866, I uploaded my logs, too.

    We think we tracked down the source of this problem yesterday, but it takes some time for our corrective measure to replicate out to all the Windows Update cache servers. Should sort itself out before too long though.

    Thanks!

    John Wink [MSFT]

    Thursday, September 15, 2016 6:42 PM
  • The download is hanging.
    Thursday, September 15, 2016 7:47 PM
  • How would we get rid of the partial download in order to get the new version to pass through?
    Thursday, September 15, 2016 7:49 PM
  • I do see a permanently failing download of kb3189866 on WSUS... its simply said impossible to distribute that patch with WSUS.

    here the WSUS server eventlog entry:

    Task Category: 2
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      
    Description:
    Content file download failed.
    Reason: CRC verification failure. 
    Source File: /d/msdownload/update/software/secu/2016/09/windows10.0-kb3189866-x64_d33b0b945db5ce1ea6414ffcb3e2afbad25fbe74.psf 
    Destination File: c:\WSUS\WsusContent\74\D33B0B945DB5CE1EA6414FFCB3E2AFBAD25FBE74.psf
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Windows Server Update Services" />
        <EventID Qualifiers="0">364</EventID>
        <Level>2</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2016-09-15T11:28:53.000000000Z" />
        <EventRecordID>11095</EventRecordID>
        <Channel>Application</Channel>
        <Computer></Computer>
        <Security />
      </System>
      <EventData>
        <Data>Content file download failed.
    Reason: CRC verification failure. 
    Source File: /d/msdownload/update/software/secu/2016/09/windows10.0-kb3189866-x64_d33b0b945db5ce1ea6414ffcb3e2afbad25fbe74.psf 
    Destination File: c:\WSUS\WsusContent\74\D33B0B945DB5CE1EA6414FFCB3E2AFBAD25FBE74.psf</Data>
      </EventData>
    </Event>

    Thursday, September 15, 2016 8:38 PM
  • Cannot download 3185611 to WSUS.  CRC verification failure.  One interesting thing is that when I manually download the psf file, the digital signature is invalid.

    http://wsus.ds.download.windowsupdate.com/c/msdownload/update/software/secu/2016/09/windows10.0-kb3185611-x64_d4a088ac78c72872cc32d4fe953e8cfc324b6af1.psf

    Log:

    2016-09-16 00:43:49.784 UTC Info WsusService.30 ContentSyncAgent.ProcessBITSNotificationQueue ContentSyncAgent recieved Transferred Event for Item: c52c8f86-88a5-4721-ae32-0a9c6b330635
    2016-09-16 00:43:49.785 UTC Info WsusService.30 ContentSyncAgent.ContentSyncSPFireStateMachineEvent ContentSyncAgent firing Event: FileDownloaded for Item: c52c8f86-88a5-4721-ae32-0a9c6b330635
    2016-09-16 00:43:49.848 UTC Info WsusService.30 ContentSyncAgent.VerifyCRC filelocalpath is E:\WSUS_Cache\WsusContent\F1\D4A088AC78C72872CC32D4FE953E8CFC324B6AF1.psf, additionalHash is A473AD0640B6A7ABB18B6C76C5CE4F22F72FE7C5D4D09351111ABC2A49D9C96A
    2016-09-16 00:44:21.342 UTC Info WsusService.30 ContentSyncAgent.VerifyCRC calculated sha1 hash is 31EB3B28F2DC12C8FB131C346D7FCAC4803E175A
    2016-09-16 00:44:21.498 UTC Warning WsusService.30 ContentSyncAgent.ProcessBITSNotificationQueue Invalid file deleted: E:\WSUS_Cache\WsusContent\F1\D4A088AC78C72872CC32D4FE953E8CFC324B6AF1.psf
    2016-09-16 00:44:21.499 UTC Info WsusService.30 ContentSyncAgent.ContentSyncSPFireStateMachineEvent ContentSyncAgent firing Event: FileVerificationFailed for Item: c52c8f86-88a5-4721-ae32-0a9c6b330635
    2016-09-16 00:44:34.129 UTC Info WsusService.30 EventLogEventReporter.ReportEvent EventId=364,Type=Error,Category=Synchronization,Message=Content file download failed.
    Reason: CRC verification failure.
    Source File: /c/msdownload/update/software/secu/2016/09/windows10.0-kb3185611-x64_d4a088ac78c72872cc32d4fe953e8cfc324b6af1.psf
    Destination File: E:\WSUS_Cache\WsusContent\F1\D4A088AC78C72872CC32D4FE953E8CFC324B6AF1.psf


    Friday, September 16, 2016 2:29 AM
  • Step #5: Path not found. Proceeded to delete SoftwareDistribution files anyway. Update rolled back at 99%.
    Friday, September 16, 2016 5:26 AM
  • Step #5: Path not found. Proceeded to delete SoftwareDistribution files anyway. Update rolled back at 99%.

    Me too. Dell XPS 15 Win10 x64. KB3185614 fails at 99% and is rolled back. In contrast to evollo I did not tried the Steps you suggested. 

    I tried disabling the UEFI Secure Boot feature and deleting old Entries of registries ProfileList, but no success. 

    Always get error code 0x800F0922 in event log (german text: Installationsfehler: Die Installation des folgenden Updates ist mit Fehler 0x800F0922 fehlgeschlagen: Kumulatives Update für Windows 10 Version 1511 für x64-basierte Systeme (KB3185614))


    • Edited by Luke15153 Friday, September 16, 2016 7:14 AM added error code
    Friday, September 16, 2016 7:07 AM
  • SUCCESS!!  update  KB3189866  processed ok along with 7 other updates this morning at 0600 EST.  Thanks!
    Friday, September 16, 2016 10:48 AM
  • What are you seeing in September?

    Better experience with workarounds.   <eg>

    A success reported today:

    http://answers.microsoft.com/en-us/windows/forum/windows_10-update/cumulative-update-for-windows-10-version-1511-for/fb1ad651-ac4e-456b-bd45-bb9d9921ae13?msgId=f2d3ba78-0548-497b-8f7d-f7efbc59d32d

    Meanwhile I am still uncertain how brittle I should be regarding the update procedure.  E.g. yesterday, I updated my mother's W10 X64 Home.  Coincidentally her MBAM happened to be completely uninstalled because I had done that while trying to solve a problem involving her HP Support tool.  It was the smoothest cumulative update so far.  Usually I always at least disable MBAM from starting with Windows and turn off its real-time monitor.

    And today, I have to decide whether I should uninstall Hyper-V before allowing the latest cumulative update.  Probably now would be the time to do it to minimize all possible interactions with Hyper-V and the update because it is currently showing as "ready to download".  Also, IE seems to be in a very strange state, especially on Answers, so a reboot for both seems like a good idea before getting and installing the update.  TBD.



    Robert Aldwinckle
    ---

    Friday, September 16, 2016 12:27 PM
  • This update excelled itself. First time I tried it I ended up with a completely unbootable computer which could only tell me "An operating system wasn't found" when it started.

    After some repair work and then a long period while it backed out the update it was back to normal again. I've since tried the installation twice, the same problem didn't recur but neither did the update install. The last time it took 55 minutes to get to 98% then failed and spent what must have been a similar amount of time rolling back the update.

    The Event Viewer reports "Installation Failure: Windows failed to install the following update with error 0x800F0922: Cumulative Update for Windows 10 Version 1511 for x64-based Systems (KB3185614)."

    I'm on 1511 10586.164 by the way.

    Friday, September 16, 2016 2:51 PM
  • error 0x800F0922

    This is one of the "this should never happen" codes that finally got its own code but has not been clearly documented.  You can find out what it supposedly means by finding it in your CBS.log (or relevant archived portion).

    Here's an example

    http://superuser.com/questions/1120506/windows-10-pro-64-bit-version-1607-fails-to-install-kb3176938-with-0x800f0922

    You could try using the timestamp in the Event log entry as context which should bound your search in the CBS.log.   E.g. probably the error occurred before it was reported.

    HTH



    Robert Aldwinckle
    ---

    Friday, September 16, 2016 3:52 PM
  • kb3189866 is now downloaded by WSUS ... but now KB3185611 fails with CRC error:

    Log Name:      Application
    Source:        Windows Server Update Services
    Date:          9/16/2016 8:57:07 PM
    Event ID:      364
    Task Category: 2
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Description:
    Content file download failed.
    Reason: CRC verification failure. 
    Source File: /c/msdownload/update/software/secu/2016/09/windows10.0-kb3185611-x64_d4a088ac78c72872cc32d4fe953e8cfc324b6af1.psf 
    Destination File: c:\WSUS\WsusContent\F1\D4A088AC78C72872CC32D4FE953E8CFC324B6AF1.psf

    Friday, September 16, 2016 7:16 PM
  • Edit: solved problem. My bad! It appears App Readiness service was disabled, which caused Edge updates to fail. After enabling App Readiness  KB3185611 installed flawlessly. 

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

    KB3185611 for Windows 10 x64 fails to install no matter if it started from Update Manager or as standalone downloaded windows10.0-kb3185611-x64_be480763644c5b51f63b299b89e0281e1a32aba1.msu package. Always reaches 100% and always rolls back with error code 0x800f0922.

    CBS log explains this code as [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED].

    Tracking the same log for reason which caused rollback, i.e. searching for string "Failure will not be ignored: A rollback will be initiated" leads to following sections:

    ---SECTION 1---

    2016-09-19 00:28:30, Info CSI 00000069 Begin executing advanced installer phase 24 (0x00000018) index 199 (0x00000000000000c7) (sequence 224)
    Old component: [ml:336{168},l:334{167}]"Microsoft-Windows-MicrosoftEdge.appxsetup, Culture=neutral, Version=10.0.10240.16384, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    New component: [ml:336{168},l:334{167}]"Microsoft-Windows-MicrosoftEdge.appxsetup, Culture=neutral, Version=10.0.10240.17113, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: uninstall
    Smart installer: FALSE
    Installer ID: {f1aab1ba-6ee0-4d94-baeb-c9fd61f365cf}
    Installer name: [36]"AppX Registration Advanced Installer"
    2016-09-19 00:28:30, Info CSI 0000006a Performing 1 operations as follows:
    (0) LockComponentPath: flags: 0 comp: {l:16 b:f822269af311d201ac00000044045004} pathid: {l:16 b:f822269af311d201ad00000044045004} path: [l:242{121}]"\SystemRoot\WinSxS\amd64_microsoft-windows-m..osoftedge.appxsetup_31bf3856ad364e35_10.0.10240.16384_none_ab4b13347435e765" pid: 444 starttime: 131187076513411279 (0x01d211f376b430cf)
    2016-09-19 00:28:30, Info CSI 0000006b Performing 1 operations as follows:
    (0) LockComponentPath: flags: 0 comp: {l:16 b:4c85289af311d201ae00000044045004} pathid: {l:16 b:4c85289af311d201af00000044045004} path: [l:242{121}]"\SystemRoot\WinSxS\amd64_microsoft-windows-m..osoftedge.appxsetup_31bf3856ad364e35_10.0.10240.17113_none_ab3ee046743f201a" pid: 444 starttime: 131187076513411279 (0x01d211f376b430cf)
    2016-09-19 00:28:30, Info CSI 0000006c@2016/9/18:21:28:30.839 Package Full Name found from manifest: [70]"Microsoft.MicrosoftEdge_20.10240.16384.0_neutral_neutral_8wekyb3d8bbwe"
    2016-09-19 00:28:30, Info CSI 0000006d@2016/9/18:21:28:30.839 Enumerating Key [ml:256{128},l:254{127}]"\Registry\Machine\Software\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\S-1-5-21-2072796489-2219481737-1248562613-500".
    2016-09-19 00:28:30, Error CSI 0000006e@2016/9/18:21:28:30.855 (F) base\appmodel\inboxappinstallerai\appxreg.cpp(157): Error HRESULT_FROM_WIN32(1058) originated in function Windows::WCP::AppXRegistration::BasicInstaller::Uninstall expression: RDSAppXOnlineNotifyPackageChanges(APPCHANGETYPE_INBOX)
    [gle=0x80004005]
    2016-09-19 00:28:30, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
    2016-09-19 00:28:31, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160918203728.log to WER report.
    2016-09-19 00:28:31, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160918164438.log to WER report.
    2016-09-19 00:28:31, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160918153145.log to WER report.
    2016-09-19 00:28:31, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160918014104.cab to WER report.
    2016-09-19 00:28:31, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160917172641.cab to WER report.
    2016-09-19 00:28:31, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
    2016-09-19 00:28:31, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2016-09-19 00:28:31, Info CBS Startup: Changing logon timeout to a static timeout: 10800000
    2016-09-19 00:28:31, Info CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Percent progress: 36.
    2016-09-19 00:28:32, Info CSI 0000006f Performing 1 operations as follows:
    (0) LockComponentPath: flags: 0 comp: {l:16 b:988ff59af311d201b000000044045004} pathid: {l:16 b:988ff59af311d201b100000044045004} path: [l:238{119}]"\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_10.0.10240.16384_none_e4739596a56e9b02" pid: 444 starttime: 131187076513411279 (0x01d211f376b430cf)
    2016-09-19 00:28:32, Error [0x018051] CSI 00000070 (F) Failed execution of queue item Installer: AppX Registration Advanced Installer ({f1aab1ba-6ee0-4d94-baeb-c9fd61f365cf}) with HRESULT HRESULT_FROM_WIN32(1058). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]
    2016-09-19 00:28:32, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
    2016-09-19 00:28:32, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160918203728.log to WER report.
    2016-09-19 00:28:32, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160918164438.log to WER report.
    2016-09-19 00:28:32, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160918153145.log to WER report.
    2016-09-19 00:28:32, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160918014104.cab to WER report.
    2016-09-19 00:28:32, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160917172641.cab to WER report.
    2016-09-19 00:28:32, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
    2016-09-19 00:28:32, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2016-09-19 00:28:32, Info CSI 00000071 Creating NT transaction (seq 2), objectname [6]"(null)"
    2016-09-19 00:28:32, Info CSI 00000072 Created NT transaction (seq 2) result 0x00000000, handle @0x484
    2016-09-19 00:28:32, Info CSI 00000073@2016/9/18:21:28:32.870 Beginning NT transaction commit...
    2016-09-19 00:28:33, Info CSI 00000074@2016/9/18:21:28:33.026 CSI perf trace:
    CSIPERF:TXCOMMIT;152830
    2016-09-19 00:28:33, Info CSI 00000075@2016/9/18:21:28:33.026 CSI Advanced installer perf trace:
    CSIPERF:AIDONE;{f1aab1ba-6ee0-4d94-baeb-c9fd61f365cf};Microsoft-Windows-MicrosoftEdge.appxsetup, Version = 10.0.10240.17113, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35};2258376us
    2016-09-19 00:28:33, Info CSI 00000076 End executing advanced installer (sequence 224)
    Completion status: HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED)

    ---SECTION 2---

    2016-09-19 00:29:08, Info CSI 000004eb Begin executing advanced installer phase 38 (0x00000026) index 295 (0x0000000000000127) (sequence 334)
    Old component: [ml:336{168},l:334{167}]"Microsoft-Windows-MicrosoftEdge.appxsetup, Culture=neutral, Version=10.0.10240.16384, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    New component: [ml:336{168},l:334{167}]"Microsoft-Windows-MicrosoftEdge.appxsetup, Culture=neutral, Version=10.0.10240.17113, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Smart installer: FALSE
    Installer ID: {f1aab1ba-6ee0-4d94-baeb-c9fd61f365cf}
    Installer name: [36]"AppX Registration Advanced Installer"
    2016-09-19 00:29:08, Info CSI 000004ec Performing 1 operations as follows:
    (0) LockComponentPath: flags: 0 comp: {l:16 b:1619abb0f311d2017d02000044045004} pathid: {l:16 b:1619abb0f311d2017e02000044045004} path: [l:242{121}]"\SystemRoot\WinSxS\amd64_microsoft-windows-m..osoftedge.appxsetup_31bf3856ad364e35_10.0.10240.16384_none_ab4b13347435e765" pid: 444 starttime: 131187076513411279 (0x01d211f376b430cf)
    2016-09-19 00:29:08, Info CSI 000004ed Performing 1 operations as follows:
    (0) LockComponentPath: flags: 0 comp: {l:16 b:1619abb0f311d2017f02000044045004} pathid: {l:16 b:1619abb0f311d2018002000044045004} path: [l:242{121}]"\SystemRoot\WinSxS\amd64_microsoft-windows-m..osoftedge.appxsetup_31bf3856ad364e35_10.0.10240.17113_none_ab3ee046743f201a" pid: 444 starttime: 131187076513411279 (0x01d211f376b430cf)
    2016-09-19 00:29:08, Info CSI 000004ee@2016/9/18:21:29:08.605 Enumerating Key [ml:256{128},l:254{127}]"\Registry\Machine\Software\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\S-1-5-21-2072796489-2219481737-1248562613-500".
    2016-09-19 00:29:08, Info CSI 000004ef@2016/9/18:21:29:08.605 Enumerating Key [ml:276{138},l:274{137}]"\Registry\Machine\Software\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\EndOfLife\S-1-5-21-2072796489-2219481737-1248562613-500".
    2016-09-19 00:29:08, Error CSI 000004f0@2016/9/18:21:29:08.605 (F) base\appmodel\inboxappinstallerai\appxreg.cpp(87): Error HRESULT_FROM_WIN32(1058) originated in function Windows::WCP::AppXRegistration::BasicInstaller::Install expression: RDSAppXOnlineNotifyPackageChanges(APPCHANGETYPE_INBOX)
    [gle=0x80004005]
    2016-09-19 00:29:08, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
    2016-09-19 00:29:08, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160918203728.log to WER report.
    2016-09-19 00:29:08, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160918164438.log to WER report.
    2016-09-19 00:29:08, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160918153145.log to WER report.
    2016-09-19 00:29:08, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160918014104.cab to WER report.
    2016-09-19 00:29:08, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20160917172641.cab to WER report.
    2016-09-19 00:29:08, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
    2016-09-19 00:29:08, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2016-09-19 00:29:09, Error [0x018051] CSI 000004f1 (F) Failed execution of queue item Installer: AppX Registration Advanced Installer ({f1aab1ba-6ee0-4d94-baeb-c9fd61f365cf}) with HRESULT HRESULT_FROM_WIN32(1058). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]
    2016-09-19 00:29:09, Info CSI 000004f2@2016/9/18:21:29:09.261 CSI Advanced installer perf trace:
    CSIPERF:AIDONE;{f1aab1ba-6ee0-4d94-baeb-c9fd61f365cf};Microsoft-Windows-MicrosoftEdge.appxsetup, Version = 10.0.10240.17113, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35};679693us
    2016-09-19 00:29:09, Info CSI 000004f3 End executing advanced installer (sequence 334)
    Completion status: HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED)

    I miss the times when updates for each application and component were being released separately.


    Sunday, September 18, 2016 11:22 PM
  • kb3189866 is now downloaded by WSUS ... but now KB3185611 fails with CRC error:

    Log Name:      Application
    Source:        Windows Server Update Services
    Date:          9/16/2016 8:57:07 PM
    Event ID:      364
    Task Category: 2
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Description:
    Content file download failed.
    Reason: CRC verification failure. 
    Source File: /c/msdownload/update/software/secu/2016/09/windows10.0-kb3185611-x64_d4a088ac78c72872cc32d4fe953e8cfc324b6af1.psf 
    Destination File: c:\WSUS\WsusContent\F1\D4A088AC78C72872CC32D4FE953E8CFC324B6AF1.psf

    We're working on getting that fixed, sorry about that. :-(

    (And sorry for the delay, was away from the office for a few days for a family event.)

    John Wink [MSFT]

    Tuesday, September 20, 2016 7:10 PM
  • This update excelled itself. First time I tried it I ended up with a completely unbootable computer which could only tell me "An operating system wasn't found" when it started.

    After some repair work and then a long period while it backed out the update it was back to normal again. I've since tried the installation twice, the same problem didn't recur but neither did the update install. The last time it took 55 minutes to get to 98% then failed and spent what must have been a similar amount of time rolling back the update.

    The Event Viewer reports "Installation Failure: Windows failed to install the following update with error 0x800F0922: Cumulative Update for Windows 10 Version 1511 for x64-based Systems (KB3185614)."

    I'm on 1511 10586.164 by the way.

    What Robert said. :-)

    Elsewhere in the CBS log you should be able to pinpoint *which* installer actually failed, and I'd love to know so we can look into it.

    Thanks!

    John Wink [MSFT]

    Tuesday, September 20, 2016 7:11 PM
  • kb3189866 is now downloaded by WSUS ... but now KB3185611 fails with CRC error:

    Log Name:      Application
    Source:        Windows Server Update Services
    Date:          9/16/2016 8:57:07 PM
    Event ID:      364
    Task Category: 2
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Description:
    Content file download failed.
    Reason: CRC verification failure. 
    Source File: /c/msdownload/update/software/secu/2016/09/windows10.0-kb3185611-x64_d4a088ac78c72872cc32d4fe953e8cfc324b6af1.psf 
    Destination File: c:\WSUS\WsusContent\F1\D4A088AC78C72872CC32D4FE953E8CFC324B6AF1.psf

    We're working on getting that fixed, sorry about that. :-(

    (And sorry for the delay, was away from the office for a few days for a family event.)

    John Wink [MSFT]

    We've reissued the Windows 10 RTM and Windows 10 Anniversary Update packages as KB3193821 and KB3193494 respectively; This is intended to resolve the various download issues. Please let us know if it works for you (or not!). Thanks!

    John Wink [ MSFT]

    Wednesday, September 21, 2016 6:12 PM
  • Any plans to incorporate ability to view .webp images with the Edge browser or with the "Photos" app?
    Sunday, September 25, 2016 3:01 AM
  • Concerning my installation issues:

    I checked the cbs.log and found three files missing in system32 folder. I reinstalled win 10 and since then everything runs fine. The cumulative update has installed without any problems.

    Sunday, September 25, 2016 2:30 PM
  • Is that "spinning dots" thing (e.g. the one caused by a broken profile) being handled yet?  If so, there may be a regression or something related was missed by the fix for it

    http://answers.microsoft.com/en-us/windows/forum/windows_10-update/windows-10-update-install-error/482ee3c8-a4f0-4486-be77-dd47bbc69fc5?msgId=b2d3b9f9-a35b-41a6-8ffb-4f7e5d7e69ee



    Robert Aldwinckle
    ---

    Monday, September 26, 2016 10:21 PM
  • Follow-up to my Win 10 Pro update issues. Never succeeded with the KB3185614 update. Solution was a direct download and install of the Win 10 Anniversary Update. While this update to 1607 completed, I was left with a dead Print Spooler. This was not the first time the Print Spooler crashed after a major Win 10 update. The first time was when the machine was upgraded from Win 7 Pro to Win 10 Pro; the second time was after a subsequent Win 10 cumulative update (which interestingly also repeatedly rolled back at 99% and never completed); this was the third occurrence. Each time this occurs, I have to fix the registry to get the spooler going again. (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler>DependOnService>[Delete the string value "http"]. Makes me wonder whether the Print Spooler error may be related to this 99% roll-back issue. 

    Friday, September 30, 2016 4:08 AM
  • My pc has been trying to update to kb3185614 update and keeps coming up as update failed, this has happened about 6 times in the last few days.
    Saturday, October 1, 2016 10:12 AM
  • KB3189866 for 1607 (Anniversary Update)                                 

    ?

    On two 1607 machines I just saw  KB3194496  which supposedly replaces  3192366  (?) and gave build  14393.222 (according to winver.exe).   However, according to  Update History it is  KB3189866  which is being superseded.

    In any case, both installations happened in one pass.  In one case I was prepared and had disabled MBAM (on my mother's W10 Home).  On the second I had an incredibly bad UX before the Update Restart reboot.  Maybe the good news is that I didn't have to do anything with Hyper-V.  I didn't resort to doing a hard reset but it sure looked like I might have to.  I couldn't see anything but a presentation that I had been watching continued to be heard; I had to sign in using Narrator; my pen was not matching anything which was on the screen; etc.  My keyboard arrow keys were backwards (normally my Tablet is in Portrait orientation and I think something made it think that it was in Landscape).  Eventually I got Task Manager up on my big monitor (which is always Landscape but at first had been disconnected) and killed everything I could including explorer.exe then started shutdown.exe -r.  That's when I was "informed" that I was doing an Update.  I should have known.   ; ]


    Robert Aldwinckle
    ---

    Saturday, October 1, 2016 2:08 PM