locked
Feature update to Windows 10 Enterprise version 1607 keeps failing on all client machines RRS feed

  • Question

  • Good day,
    Has anyone perhaps had the same issue where the Feature update to Windows 10 version 1607 fails on the client machines.
     I have had some feedback from various Forums suggesting that we add .esd to the MIME TYPE
    Infrastructure updated.
    Is there perhaps something that we might have missed or any suggestions.
    Wednesday, October 19, 2016 6:21 AM

Answers

  • Microsoft assisted with our WSUS and applied the following fix in our environment.

    https://support.microsoft.com/en-us/kb/3194588

    That is related to the WSUS being in a bad state with the Windows 10 upgrades.

    BUT now all the test workstations I deploy the Feature Update to 1607 all show Compliant even though they are not and no activity on the client machines.

    The log files show 0 updates detected.

    Running out of options.

    • Marked as answer by JvanRensburg Tuesday, November 1, 2016 6:03 AM
    Friday, October 28, 2016 11:46 AM

All replies

  • Is there perhaps something that we might have missed or any suggestions.

    Yes ... you missed to provide details ;-) "fails on the client machines" is not very helpful unfortunately. Any error messages/codes?

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, October 19, 2016 7:54 AM
  • Have you tried to download the Installation media manually and run an Inplace upgrade:

    How to upgrade to Windows 10 v1607 manually if the windows update doesn't find it


    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 20, 2016 2:49 AM
  • I was under the impression that there is a general issue with clients failing with the "Feature Update to 1607" ..

    Will provide details on the error code.

    Just picked up on another strange issue. Two test workstations are on Windows 10 (10586.589) and in the Windows 10 Servicing required for the "Feature Update". Deployed the update to the test collection and both workstations returned as "Compliant" and still on Windows 10 (10586.589)

    Thursday, October 20, 2016 7:06 AM
  • We have tested in our lab and the in-place upgrade works perfectly but cannot install manually for all the users. :)
    Thursday, October 20, 2016 7:07 AM
  • did you check the client, to see if the Defer Upgrades = Enabled ?

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Thursday, October 20, 2016 8:25 AM
  • Thanks for the feedback.

    We logged a call with Microsoft and identified that there is problems with specific KB updates on the WSUS.

    From an SCCM side everything is good just WSUS that needs some attention.

    Microsoft also supplied the following link.

    https://support.microsoft.com/en-us/kb/3194588#!%2Fen-us

    Friday, October 21, 2016 6:30 AM
  • Thanks for the feedback.

    We logged a call with Microsoft and identified that there is problems with specific KB updates on the WSUS.

    From an SCCM side everything is good just WSUS that needs some attention.

    Microsoft also supplied the following link.

    https://support.microsoft.com/en-us/kb/3194588

    Ah.

    Cause: The problem may occur if the (Upgrades classification) updates are synced before you apply KB3159706


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Friday, October 21, 2016 7:08 AM
  • Microsoft assisted with our WSUS and applied the following fix in our environment.

    https://support.microsoft.com/en-us/kb/3194588

    That is related to the WSUS being in a bad state with the Windows 10 upgrades.

    BUT now all the test workstations I deploy the Feature Update to 1607 all show Compliant even though they are not and no activity on the client machines.

    The log files show 0 updates detected.

    Running out of options.

    • Marked as answer by JvanRensburg Tuesday, November 1, 2016 6:03 AM
    Friday, October 28, 2016 11:46 AM
  • I get this same issue with error code 0x8024a105



    Tuesday, January 24, 2017 1:35 AM