locked
1607 Upgrade not working. Downloaded updates before applying KB3159706 RRS feed

  • Question

  • Hi,

    Yesterday I approved education and enterprise 1607 upgrades on my WSUS before applying KB3159706.  They downloaded to WSUS and the clients ok but I had an install error on my (1511) test clients.  I was getting:

    Feature update to Windows 10 Enterprise, version 1607, en-us - Error 0x80240031

    I also got error 0xc1800118 on an education edition i was testing on.

    At this point I read the WSUS blog and realized I needed KB3159706.

    I declined the updates on WSUS and ran the cleanup wizard which removed the 1607 downloads.  I then applied KB3159706 and performed all of the manual steps. I re-approved and downloaded the updates.  On the clients I stopped windows updates service and cleared out C:\windows\softwaredistribution then restarted the service.  I then received the following error on my enterprise and education clients:

    Feature update to Windows 10 Enterprise, version 1607, en-us - Error 0xc1800118

    Will downloading the 1607 upgrades before applying KB3159706 give me this issue?  Please advise how to rectify.

    My WSUS server is correctly patched to download and distribute 1511 and has been doing for some time.  Just having issues with 1607.

    Cheers,

    Steve


    • Edited by Steve_23 Thursday, August 18, 2016 6:52 AM typos
    Thursday, August 18, 2016 6:51 AM

Answers

All replies

  • Hi Steven,

    Yes, to deploy 1607 upgrade, we need to install KB3159706 first and complete the manual steps after installing the KB, do you do the manual steps for KB3159706, and what is the result after installing the KB, can you deploy the upgrade successfully?

    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 Support, contact tnmff@microsoft.com.

    Thursday, August 18, 2016 7:58 AM
  • I deployed the KB and completed the manual steps I then re-downloaded the updates and still got the same error (as described in my original post above).  Please advise
    Thursday, August 18, 2016 8:06 AM
    • Edited by Fulgent Thursday, August 18, 2016 10:00 AM
    Thursday, August 18, 2016 8:23 AM
  • same Problem. Anyone from Microsoft who can explaint that error Code?


    • Edited by surfer13 Thursday, August 18, 2016 9:50 AM
    Thursday, August 18, 2016 9:49 AM
  • Same problem, KB is installed and finalized. In my case, this problem is RANDOM! 1/3 of machines cannot pull this through.
    Thursday, August 18, 2016 10:54 AM
  • Hi,

    1. Ensure WSUS server 4.0 installs both KB3095113 and KB3159706(with manual steps);

    2. Enable WSUS server download the 1607 file successfully before clients detecting them;

    3. Ensure .esd MIME type is added to 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 Support, contact tnmff@microsoft.com.

    Monday, August 22, 2016 8:25 AM
  • Hi Anne,

    KB3095113 has been on for some time before KB3159706.  I was successfully distributing 1511 with WSUS for months.   So I can safely assume my MIME type config is ok too?  (I have the .esd added to the IIS Site "WSUS Administration" Site.)

    As for point 2 in your reply. I have my WSUS set to download updates once approved.  I approved the update, let them download then tried it on the clients.  This process should work ok?

    Should I try running the manual steps on KB3159706 again?  Please bare in mind I have the 1607 updates currently downloaded to WSUS.

    Cheers,

    Steve




    Steven Crudgington Keele University UK

    Monday, September 5, 2016 9:01 AM
  • Hi Steve,

    >Please bare in mind I have the 1607 updates currently downloaded to WSUS.

    Then is there any other issues? If you have make things working, you may mark useful replies as answer, if not, what is your current situation now?

    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 9, 2016 9:17 AM
  • Hi Anne,

    My situation is still the same I am still getting the same error message on my clients.

    • Feature update to Windows 10 Enterprise, version 1607, en-us - Error 0xc1800118

    I don't have Microsoft .NET Framework 4.6.1 installed on my WSUS Server.  Would this help?

    This issue looks quite widespread, please see the comments on: https://community.spiceworks.com/topic/1774501-wsus-client-wont-update-from-1511-to-1607-error-0xc1800118

    Cheers,

    Steve


    Steven Crudgington Keele University UK




    • Edited by Steve_23 Tuesday, September 13, 2016 1:16 PM
    Monday, September 12, 2016 9:21 AM
  • There are additional steps required to properly purge encrypted content that has been downloaded prior to applying KB3159706.  Please refer to the KB published today for more information: https://support.microsoft.com/en-us/kb/3194588
    • Proposed as answer by Steve Henry [MSFT] Thursday, September 22, 2016 1:19 AM
    • Marked as answer by Steve_23 Tuesday, September 27, 2016 2:51 PM
    Thursday, September 22, 2016 1:19 AM
  • This worked.  Thanks

    Steven Crudgington Keele University UK

    Tuesday, September 27, 2016 2:51 PM