none
WSUS dependent Update - Behavior not consistent.

    Question

  • We are in the progress of updating our company (~150 PCs) to Windows 10. 

    We have now rolled out ~ 14 Windows 10 Machines so far, and we are very very unhappy with the Update behaviour. 
    (The WSUS is a 2008 R2)

    Each Windows 10 PC - even if the very same GPOs are applied everywhere - is behaving in its very own way. 

    A few problems that have been resolved so far: 

    - Machine does not find "new" Updates - always reports uptodate.
    - Machine does find Windows Update, but totally refuses to find any other MS-Product-Update.
    - Machine does download updates, fails to install and never ever tries again. (Installed manually)

    Two problems still remain: 

    - One machine - even if it's uptodate - fails to report it's status to WSUS. Last contact is almost updated daily, but no status report is transfered: 


    - One machine starts do download updates - then stucks with "Downloading..." forever. Stopping all related services, clearing the SoftwareDeployment Folder and retrying leads to the same. Some updates are downloaded, then it stucks, nothing is installed....

    All Clients are 10 Pro x64.

    Any Ideas?

    I really fear what else might come up for the remaining 140 Machines...


    • Edited by dognose Thursday, March 9, 2017 5:48 PM
    Thursday, March 9, 2017 5:46 PM

All replies

  • - One machine starts do download updates - then stucks with "Downloading..." forever.

    Any clues in Setupact.log?  I think I saw something like this except it ended with an unknown error code.  0xC1800104.  While researching that I ran into some great diagnostic resources

    https://technet.microsoft.com/en-us/itpro/windows/deploy/resolve-windows-10-upgrade-errors?f=255&MSPPError=-2147217396

    So, is forever really an uncontrolled loop or just an excessively long timeout?

    BTW there are also some direct links into WSUS blog posts for even more interesting reading.   ; )

     

    HTH



    Robert Aldwinckle
    ---

    Friday, March 10, 2017 1:29 AM
  • - One machine starts do download updates - then stucks with "Downloading..." forever.

    Any clues in Setupact.log?  I think I saw something like this except it ended with an unknown error code.  0xC1800104.  While researching that I ran into some great diagnostic resources

    https://technet.microsoft.com/en-us/itpro/windows/deploy/resolve-windows-10-upgrade-errors?f=255&MSPPError=-2147217396

    So, is forever really an uncontrolled loop or just an excessively long timeout?

    BTW there are also some direct links into WSUS blog posts for even more interesting reading.   ; )

     

    HTH



    Robert Aldwinckle
    ---

    Hey there,

    just checked today and now it reports Updates available for installation... So, it seems like we've got a "fourth" point on the list of strange behaviour:

    - Machine fails to download updates, when searching manually, but successfully downloads updates on the daily schedule.

    what is wrong with that windows 10 Update thingy? Running 7 along with wsus for years now, never faced something like this...

    ps.: setupact.log does not contain any entry newer than dec-2016, System time is correct btw.
    • Edited by dognose Friday, March 10, 2017 8:13 AM
    Friday, March 10, 2017 8:06 AM
  • ps.: setupact.log does not contain any entry newer than dec-2016

    That means that the problem is an update, not an upgrade.  So, the machine version will already be at 14393.   Use winver to find out what the current build actually is.  With no other clues I would use ReportingEvents.log to get a timestamp context and then dive into the CBS.log (or archived portions).  There may also be other timestamp contexts available from System Information Windows Error Reporting section (msinfo32.exe WER) and various Event logs.  Look at SetupAPI.Dev.log if you think there is a driver problem.  And as I hinted there are other WSUS specific diagnostics available.

    Good luck



    Robert Aldwinckle
    ---

    Friday, March 10, 2017 1:06 PM