locked
Cannot update Windows 10 Pro computers from 10240 to 1607 from WSUS RRS feed

  • Question

  • Hello, I have problem to update company computers (about 300) from Windows 10 Pro build version 10240 (installed version) to newest Windows 10 anniversary update 1607. Updates are delivered from our WSUS server (Windows Server 2012 R2) with latest updates and all computers are set (via GPO) to download and install updates from wsus (and wait for reboot). I approved updates to 1607 (KB3176936) and when I check for updates on computers I get option to download and install "Feature update to Windows 10 Pro, version 1607, en-us, Retail", but after couple minutes of download and install I get error message:

    There were problems installing some updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help:

    Retry

    After this may help: isn't any error code or anything.

    From SoftwareDistribution log:

    {5DCCA5A3-22D5-4964-8A88-4B8C61F561F9} 2016-09-09 09:17:38:204+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244010 UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x80244010.
    {F87996D4-B2C2-4D67-B4AC-A9A579BB4BF5} 2016-09-09 09:17:38:992+0200 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 0 updates.

    Friday, September 9, 2016 7:18 AM

Answers

All replies

  • Hi garmada,

    >Software Synchronization Windows Update Client failed to detect with error 0x80244010.

    Error 0x80244020 means "Exceeded max server round trips", this error often exits at the first sync on new build computers.

    https://blogs.technet.microsoft.com/sus/2008/09/18/wsus-clients-fail-with-warning-syncserverupdatesinternal-failed-0x80244010/

    Are the win10 10240 clients new build that haven't been updated ever?

    If yes, please update these clients first then upgrade them:

    1. On the WSUS server, not approve the 1607 upgrade (enable clients not to detect it);

    2. Decline all unneeded updates and superseded updates on WSUS server and run server cleanup wizard;

    3. On Win10 clients, clear "SoftwareDistribution" folder;

    4. Then check update on win10, if you still have error 0x80244010, just keep on checking for updates, generally, this error may occur 3-4 times, after 3-4 times sync, the error may disappear and windows update may work well;

    5. After updating the windows 10 clients, then approve upgrade 1607, check update on client to install the upgrade.

    Check if this method could work.

    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.


    Monday, September 12, 2016 2:56 AM
  • This computers are updated regularly and since Windows 1607 came for WSUS, I wanted to upgrade all computers but about 90% of computers (about 100) are falling to install with error code Error 0xc1800118. I tried to reset Windows update (delete softwaredistribution) on computers but still nothing. 

    I also found this topic which seems to be related to my issues. https://social.technet.microsoft.com/Forums/office/en-US/d2afda41-7f28-4ab7-b044-fe60238ac6fd/1511-to-1607-enterprise-feature-upgrade-failing?forum=win10itprosetup

    Now I am just waiting for Microsoft to fix this problem (as always).

     
    Wednesday, September 14, 2016 8:54 AM
  • Hi garmada,

    Then do you add .esd MIME type in the WSUS IIS site?

    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.

    Friday, September 16, 2016 3:15 AM
  • Hi garmada,

    Could the above replies be of help? If yes, you may mark it as answer, if not, feel free to feed back.

    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, September 20, 2016 9:57 AM
  • garmada, you may be running into the issue that is caused by synching Upgrades (feature updates) such as 1607 before your WSUS has been properly prepared. You might find https://support.microsoft.com/en-us/kb/3194588 useful in resolving this.
    Thursday, September 22, 2016 1:17 AM
  • Hi garmada,

    Could Steve Henry's information be of help? Feel free to feed back.

    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.

    Friday, September 23, 2016 7:28 AM