none
Some Win10 Enterprise Clients seeing 1703 update, others are not

    Question

  • Has anyone run into this?  The ones that are now I try to run the Win10 upgrade assistant it gives me the contact your system administrator to upgrade enterprise edition. 
    Monday, April 24, 2017 1:08 PM

All replies

  • Hi, 

    First to say, Upgrade assistant tool does not support Enterprise editions. 

    Then, I would like to confirm with you that if your have WSUS configured in your environment and if these computer are in the same OU. 

    Have you noticed that if there is any error message on the problematic computers on Windows update? We can take some ones to run Windows update reset tool to check this issue first:

    https://support.microsoft.com/en-sg/help/971058/how-do-i-reset-windows-update-components

    See if these issues can be resolved. 

    Also, if the computers with problems has been chosen Defer updates before, ,that could be the issue. 

    If you would like all the PCs have this upgrade, we can force to deploy the upgrade by tools like WDS, MDT, SCCM. 


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

    Thursday, April 27, 2017 7:08 AM
    Moderator
  • We are not using WSUS and they are all in the same OU.   Machines not getting the 1703 update are not generating any errors and are getting other updates just fine.  They are not deferring updates
    Thursday, April 27, 2017 1:20 PM
  • Hi, 

    At this time, the most efficient way for us is that we download the ISO file from volume licensing center by using your VLC key and do the In-place upgrade. 

    https://www.microsoft.com/Licensing/servicecenter/default.aspx


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

    Friday, April 28, 2017 8:15 AM
    Moderator
  • Not available until Monday and not feasible on 550 Win10 machines
    Friday, April 28, 2017 10:25 AM
  • I have this case, where my machine does not see 1703 upgrade, but others do. WSUS is used. I deleted wsus reg keys from my machine, to be able to talk to MS directly, but still couldn´t see 1703. (I did see some other single updates there which weren´t approved from our WSUS).

    Please remember to mark my post as an answer, if I really helped you out, or vote if usefull. Thank you!

    Friday, April 28, 2017 10:28 AM
  • Hi, 

    Please also check if you have any WU server configure on your Client PC, let's check this registry key: 

    Wuserver set in registry key: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate 

    If yes, remove from Client PC and see if they can get the feature upgrade.

    Also, please help to collect group policy results, and Windowsupdate.log on the problematic computer, let's do more research:

    https://support.microsoft.com/en-us/help/3036646/how-to-read-windows-update-logs-in-windows-10-version-1607

    Run commands as admin: 

    gpresults /h c:\test.html

    Then, upload test.html and windowsupdate.log onto OneDrive and share the link here. 


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


    Tuesday, May 02, 2017 6:07 AM
    Moderator
  • No WU server configured.  Here is a link to the logs

    https://tinyurl.com/lz5leyf

    Tuesday, May 02, 2017 2:12 PM
  • Hi, 

    I get this error when trying to access the shared files:

    Sorry, the link has expired.

    The link was set to expire after a certain amount of time. Please contact the person who shared this link with you.


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



    Thursday, May 11, 2017 9:44 AM
    Moderator
  • https://tinyurl.com/k7yexf6
    Thursday, May 11, 2017 7:00 PM
  • Hi Krdell,

    There could be some misunderstanding between us. 

    Please confirm again that to check your update issue, we need to get the Windowsupdate.log which we can get by running this powershell command:

    get-windowsupdatelog

    And the group policy settings on your PC by running this command:

    gpresults /h c:\test.html

    Please upload the test.html and windowsupdate.log onto OneDrive for our research. 


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

    Tuesday, May 16, 2017 8:26 AM
    Moderator