locked
WSUS updates Windows 10 1607 Stuck at 45% RRS feed

  • Question

  • Hi,

    The last couple of cumulative updates for windows 10 Pro 1607 have gotten stuck downloading at 45% when using wsus ? e.g. KB 3199209

    I have noted that windows when updating language packs are also getting stuck.

    Anyone had any luck getting to the bottom of this?

    Stuart

    Wednesday, October 26, 2016 11:07 PM

Answers

  • I think I found a solution, at least for my Environment.

    We were running WSUS on Server 2008R2, when the Problems with Win 10 1607 started, I even upgraded one of our WSUS-Servers to Server 2016 as soon as it was out. Which took quite some time until I had it stable btw.

    Approx. all two-three months I rebuild our reference Images to include the latest cumulative Update. If new cumulative Updates are released and until I have time to rebuild the reference Images, I add the latest cumulative update to the deployment Task to have a fresh machine in an up-to-date state.

    But when the machines are in production and the next cumulative is released, even the latest builds kept being stuck at 45 % Downloading.

    Today I disabled "Download Express Installation files" on our WSUS Servers (Options => Update Files and Languages), let them download the missing parts, ran the Server cleaup wizard, the maintenance script and rebooted the Servers.

    Then I went over to the Clients. Some were updating after a reboot, maybe these were ones stuck downloading on an older cumulative update than the current one.

    On the other machines I was presented with an error message (0x80244019). I then set the Windows Update Service to Disabled, rebooted the machine, deleted the Content of c:\windows\softwaredistribution, set the Windows Update Service back to the original state and started it. Now the Client was able to download and install the updates again.

    I guess the Clients would start working again when the next cumulative Update is released. At the Moment they have the current cumulative update cached in its Express-Format which seems to cause our Troubles.

    Which pointed me to try this out was an entry in the c:\windows\logs\cbs\CBS.log, which repeated over and over again:

    2017-01-23 16:31:57, Info                  CBS    Exec: This is a PSF Package.  Job has been saved and we are returning to client.
    2017-01-23 16:31:57, Info                  CSI    00000013@2017/1/23:15:31:57.330 CSI Transaction @0x6f254c8 destroyed
    2017-01-23 16:31:57, Info                  CBS    Exec: DPX job state saved for one or more packages, aborting the staging and install of execution.
    2017-01-23 16:31:57, Info                  CBS    CommitPackagesState: Started persisting state of packages
    2017-01-23 16:31:57, Info                  CBS    CommitPackagesState: Completed persisting state of packages
    2017-01-23 16:31:57, Info                  CSI    00000014@2017/1/23:15:31:57.424 CSI Transaction @0x6f25810 destroyed
    2017-01-23 16:31:57, Info                  CBS    Perf: Stage chain complete.
    2017-01-23 16:31:57, Info                  CBS    Failed to stage execution chain. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
    2017-01-23 16:31:57, Info                  CBS    Failed to process single phase execution. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
    2017-01-23 16:31:57, Info                  CBS    WER: Failure is not worth reporting [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]

    It was referencing, that it deals with a PSF Package (=Express Installation File) and short time after this it crashes but it seems Windows Error Reporting doesn't kick in since the "Failure is not worth reporting", maybe that's the problem why Microsoft is not really aware of the issue.

    Maybe this helps you too.

    Best Regards
    Mario



    Monday, January 23, 2017 3:56 PM

All replies

  • Hi stuart dyer,

    I tested in my lab, win10 1607 could download and install KB3199209 successfully:

    My win10 1607 have installed KB3194798 before, after installing KB3194798, it fixes the issue when downloading updates from WSUS server.

    https://support.microsoft.com/en-us/help/12387/windows-10-update-history

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Thursday, October 27, 2016 3:20 AM
  • Hi Anne,

    Mine is doing this...... windows 10 pro and enterprise both having this issue


    Thursday, October 27, 2016 3:33 AM
  • Hi stuart dyer,

    Please try installing KB3194798 manually, then download again, check if after installing the update, other updates can be downloaded correctly.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.




    Thursday, October 27, 2016 8:55 AM
  • Hi,

    Does KB3194798 need to be installed manually, are there issues with it ?

    Stuart

    Thursday, October 27, 2016 10:25 PM
  • Hi,

    tried a manual install of this KB from windows update catalog downloads but this one gets stuck on copying packages to the windows update cache

    Friday, October 28, 2016 12:29 AM
  • Hi,

    KB3194798 is now installed but it now keeps failing on KB3197954 at 45%

    Sunday, October 30, 2016 10:25 PM
  • Hi,

    Now KB3199986 & KB3197954 are getting stuck at 45% from WSUS on all of our endpoints....

    Monday, October 31, 2016 1:02 AM
  • Hi stuart syer,

    1. Please check if Windows Update service is running at that time;

    2. Please run windows update troubleshooter on Win10, then try again;

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, November 1, 2016 8:22 AM
  • Hi,

    The windows update service is running, i ran the update troubleshooter and it found a corrupt local db, fixed it, rebooted but it wants to now install KB3197954 & KB3199986 they are getting stuck at 45% if i switch to Microsoft servers they download fine. I can manually install these but I can't do it on over 100 end points'

    Tuesday, November 1, 2016 11:40 PM
  • Hi Anne,

    We are still having this issue with our WSUS

    Monday, November 14, 2016 1:52 AM
  • I think I found a solution, at least for my Environment.

    We were running WSUS on Server 2008R2, when the Problems with Win 10 1607 started, I even upgraded one of our WSUS-Servers to Server 2016 as soon as it was out. Which took quite some time until I had it stable btw.

    Approx. all two-three months I rebuild our reference Images to include the latest cumulative Update. If new cumulative Updates are released and until I have time to rebuild the reference Images, I add the latest cumulative update to the deployment Task to have a fresh machine in an up-to-date state.

    But when the machines are in production and the next cumulative is released, even the latest builds kept being stuck at 45 % Downloading.

    Today I disabled "Download Express Installation files" on our WSUS Servers (Options => Update Files and Languages), let them download the missing parts, ran the Server cleaup wizard, the maintenance script and rebooted the Servers.

    Then I went over to the Clients. Some were updating after a reboot, maybe these were ones stuck downloading on an older cumulative update than the current one.

    On the other machines I was presented with an error message (0x80244019). I then set the Windows Update Service to Disabled, rebooted the machine, deleted the Content of c:\windows\softwaredistribution, set the Windows Update Service back to the original state and started it. Now the Client was able to download and install the updates again.

    I guess the Clients would start working again when the next cumulative Update is released. At the Moment they have the current cumulative update cached in its Express-Format which seems to cause our Troubles.

    Which pointed me to try this out was an entry in the c:\windows\logs\cbs\CBS.log, which repeated over and over again:

    2017-01-23 16:31:57, Info                  CBS    Exec: This is a PSF Package.  Job has been saved and we are returning to client.
    2017-01-23 16:31:57, Info                  CSI    00000013@2017/1/23:15:31:57.330 CSI Transaction @0x6f254c8 destroyed
    2017-01-23 16:31:57, Info                  CBS    Exec: DPX job state saved for one or more packages, aborting the staging and install of execution.
    2017-01-23 16:31:57, Info                  CBS    CommitPackagesState: Started persisting state of packages
    2017-01-23 16:31:57, Info                  CBS    CommitPackagesState: Completed persisting state of packages
    2017-01-23 16:31:57, Info                  CSI    00000014@2017/1/23:15:31:57.424 CSI Transaction @0x6f25810 destroyed
    2017-01-23 16:31:57, Info                  CBS    Perf: Stage chain complete.
    2017-01-23 16:31:57, Info                  CBS    Failed to stage execution chain. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
    2017-01-23 16:31:57, Info                  CBS    Failed to process single phase execution. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
    2017-01-23 16:31:57, Info                  CBS    WER: Failure is not worth reporting [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]

    It was referencing, that it deals with a PSF Package (=Express Installation File) and short time after this it crashes but it seems Windows Error Reporting doesn't kick in since the "Failure is not worth reporting", maybe that's the problem why Microsoft is not really aware of the issue.

    Maybe this helps you too.

    Best Regards
    Mario



    Monday, January 23, 2017 3:56 PM
  • Yep that was it, took MS support a week to work it out.
    Monday, January 23, 2017 9:31 PM
  • Thanks for your answer.

    Did you get a Statement from MS Support if this will be fixed for 1607 or will we have to wait for the Creators Update?

    Tuesday, January 24, 2017 9:43 AM
  • Hi,

    They seemed to believe it was a problem with the WSUS server and needed a re-install and I was the only one with the issue so they had not seen it before. I won't be deploying 1607 at the moment as some features we use like custom menu and lock / log on screen images gpo policies were removed from professional and put into enterprise only.

    Thanks

    Stuart

    Tuesday, January 24, 2017 9:11 PM