locked
Windows 10 Anniversary Update (1607) - Not Applicable RRS feed

  • Question

  • *** Asked to move this from the Windows 10 Forum,  Re-Posted here ***

    We have Windows 10 Enterprise 1511 deployed to several machines in our organization for production testing with some users.   On August 16th I see that the 1607 Anniversary Update hit my WSUS server.   (e.g.  "Feature update to Windows 10 Enterprise, version 1607, en-us")

    Environmental Notes:

    1. WSUS is running on Windows 2012 R2
    2. Patched WSUS to allow ESDs to installed and manual settings have been performed per KB3159706
    3. Patched WSUS with KB3095113
    4. All other patches were found and able to install on my Windows 10 1511 machines
    5. Tried deleting all updates from WSUS and re-syncing / downloading.
    6. Reset the Windows 10 1511 machines windows update client.   (e.g.  Delete SoftwareDistribution folder)

    Unfortunately the all the versions of the anniversary upgrades are showing as Not Applicable to my machines.   Is there something I am doing wrong?   I don't want to have to manually update all of these machines.


    Eric S.

    Monday, August 22, 2016 3:01 PM

Answers

  • I just found this post in a different forum/thread that worked for me to fix this issue:

    --------------------------------

    In my case, problem was in  group policy setting: Windows components - Store - Turn off the offer to update to the latest version of Windows.

    Proposed as answer by Anne HeMicrosoft contingent staff, Moderator 5 hours 30 minutes ago

    ---------------------------------


    Eric S.

    • Marked as answer by Eric Suger Thursday, September 1, 2016 2:45 PM
    Thursday, September 1, 2016 2:45 PM

All replies

  • Not the anniversary update isn't showing up either when I check against Microsoft directly instead of WSUS.

    What the H...


    Eric S.

    Monday, August 22, 2016 4:50 PM
  • Hi Eric Suger,

    1. Does the WSUS server download the upgrade file successfully, please check WSUS overview download status:

    2. Enable you approve the corresponding version for win10 1511 clients, for example "Enterprise" to "Enterprise":

    3. Please check the windows update log, search with the "Update ID", check if in windows update log, clients also record as "Not applicable", you may check the Update ID here:

    (Beside, seems you are not the only one that facing this issue)

    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.


    Tuesday, August 23, 2016 3:09 AM
  • 1.  This isn't a download issue of the WSUS patch itself.   All of my "Upgrade" Windows 1607 patches are all being indicated as "Not Applicable"  (Currently 16)  while in a non-approved status.  Including the two for Windows 10 Enterprise, 1607.

    2. See above

    3.   The logs produced from the powershell command (Get-WindowsUpdateLog)mon the Windows 10 PC doesn't give me the information that you are looking for.     Should I be looking somewhere else?   See the following:

    2016/08/22 22:48:06.5187078 844   3572  Agent           WU client version 10.0.10586.545
    2016/08/22 22:48:06.5189516 844   3572  Agent           SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
    2016/08/22 22:48:06.5192205 844   3572  Agent           Base directory: C:\Windows\SoftwareDistribution
    2016/08/22 22:48:06.5193355 844   3572  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
    2016/08/22 22:48:06.5193626 844   3572  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2016/08/22 22:48:06.5197619 844   3572  Shared          Network state: Connected
    2016/08/22 22:48:06.5654866 844   3572  Misc            LoadHistoryEventFromRegistry completed, hr = 8024000C
    2016/08/22 22:48:06.6461890 844   3572  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
    2016/08/22 22:48:06.6462041 844   3572  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2016/08/22 22:48:06.6462167 844   3572  Shared          Power status changed
    2016/08/22 22:48:06.6479204 844   3572  Agent           Initializing global settings cache
    2016/08/22 22:48:06.6479219 844   3572  Agent           WSUS server: https:// (changes for privacy)
    2016/08/22 22:48:06.6479228 844   3572  Agent           WSUS status server: https:// (changes for privacy)
    2016/08/22 22:48:06.6479237 844   3572  Agent           Target group: Client
    2016/08/22 22:48:06.6479245 844   3572  Agent           Windows Update access disabled: No
    2016/08/22 22:48:06.6491892 844   3572  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-08-23 16:36:29, not idle-only, not network-only
    2016/08/22 22:48:06.8459057 844   3572  Agent           Initializing Windows Update Agent
    2016/08/22 22:48:06.8460916 844   3572  DownloadManager Download manager restoring 0 downloads
    2016/08/22 22:48:06.8462061 844   3572  Agent           CPersistentTimeoutScheduler | GetTimer, returned hr = 0x00000000
    2016/08/22 22:48:24.6471189 844   2736  DownloadManager PurgeExpiredFiles::Found 0 expired files to delete.
    2016/08/22 22:48:25.1196992 844   2736  DownloadManager PurgeExpiredUpdates::Found 435 non expired updates.
    2016/08/22 22:48:25.2892237 844   2736  DownloadManager PurgeExpiredUpdates::Found 0 expired updates.
    2016/08/22 22:48:25.2933735 844   2736  Shared          Effective power state: AC
    2016/08/22 22:48:25.2933753 844   2736  DownloadManager Power state change detected. Source now: AC
    2016/08/22 22:53:05.6218069 4172  4208  AppAU           * START * Finding app updates
    2016/08/22 22:53:05.6219194 4172  4208  AppAU           * END * Finding app updates, exit code = 0x00000000
    2016/08/22 22:58:06.5209408 844   3056  Agent           Earliest future timer found:
    2016/08/22 22:58:06.5209779 844   3056  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-08-23 16:36:29, not idle-only, not network-only
    2016/08/22 22:58:07.5699620 844   3572  Agent           Earliest future timer found:
    2016/08/22 22:58:07.5699804 844   3572  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-08-23 16:36:29, not idle-only, not network-only
    2016/08/22 22:58:07.5748685 844   3572  Misc            CreateSessionStateChangeTrigger, TYPE:2, Enable:No
    2016/08/22 22:58:07.6064065 844   3572  Misc            CreateSessionStateChangeTrigger, TYPE:4, Enable:No
    2016/08/22 22:58:07.8692901 844   3572  Shared          * END * Service exit Exit code = 0x240001


    Eric S.

    Tuesday, August 23, 2016 4:18 AM
  • I have the same problem. All the feature updates for all windows editions are "Not Applicable"
    Tuesday, August 23, 2016 6:18 AM
  • Hi,

    Yeah, seems many people meet the issue. I'm trying to involve someone familiar with this aspect to do further research.

    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

    Tuesday, August 23, 2016 7:46 AM
  • Same problem here. Not sure if it's related to the updates been deferred? Between this issue and me trying to verify a office 365 domain, Microsoft really dropping the ball lately with SIMPLE things.

    Tuesday, August 23, 2016 8:32 AM
  • +1 over here.

    We've played around with the KB3095113 and KB3159706 + post manual tweaking.
    It seems they are OK.

    For us the Feature update downloads to the WSUS store (I can see two 2.x GB esd files in the folders for x86 and x64).
    esd file type added to the MIME in IIS.

    The upgrades showing up correctly as Upgrades (I've even deleted them with the PS cmdlet + cleanup wizard then resync).
    I've manually approved the corresponding version (Win 10 Ent en-us), not that it should matter, but still all of our computers reporting as Not Applicable.

    Could not find anything in the client windows update log.
    WSUS itself seems to be working as clients downloaded a few Office 2016 patches recently.

    Were there anyone managed to fix this somehow?

    Cheers,
    Gergo

    Tuesday, August 23, 2016 11:05 PM
  • Hi,

    Yeah, seems many people meet the issue. I'm trying to involve someone familiar with this aspect to do further research.

    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

    Any update on this from Microsoft?



    Eric S.

    Wednesday, August 24, 2016 2:27 PM
  • Hi Eric Suger,

    Do you install KB3095113 and KB3159706 prior to sync the update? If the update being synced before the KB was installed would cause some data loss in the SUSDB that would lead to the client being unable to get the decryption key from WSUS at the time of installation and thus causing a decryption failure for the update on the client side.

    Then, please delete the upgrade and sync it again, check if it could work.

    How to delete upgrades in WSUS

    https://blogs.technet.microsoft.com/sus/2016/01/29/how-to-delete-upgrades-in-wsus/

    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 25, 2016 7:50 AM
  • Those two patches were installed months ago (with manual steps) due to some of the patches not getting to my Windows 8.1 machines.

    However, I did try the delete upgrade in WSUS before I opened this thread. No impact it still doesn't work.


    Eric S.

    Thursday, August 25, 2016 3:23 PM
  • same exact issue here. followed similar steps. i'm now working through rebuilding the WSUS server to see if that helps.
    Thursday, August 25, 2016 5:16 PM
  • We have exactly the same problem here in Switzerland. Even a complete rebuild of the WSUS (before first sync clean install of patches KB3159706 and KB3095113) doesn't solved the issue.

    Regards
    Patrick

     
    Friday, August 26, 2016 9:28 AM
  • Got same problem on a freshly built 2012R2 WSUS

    All upgrades are showing up as not applicable.

    Done the KB fixes and ran powershell scripts to clean up the files.

    Friday, August 26, 2016 1:18 PM
  • Any update from Microsoft on this?

    Eric S.

    Saturday, August 27, 2016 2:35 PM
  • Hi Eric Suger,

    At the end, will you try reinstalling WSUS server?

    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.

    Tuesday, August 30, 2016 5:47 AM
  • Hi Eric Suger,

    At the end, will you try reinstalling WSUS server?

    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.

    That has to affect.  Still does not work.


    Eric S.

    Tuesday, August 30, 2016 2:04 PM
  • Ugh,  on another thread Microsoft is basically saying that they can't repro the issue so to bad... 

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/5521e7f1-fa2d-4867-a47c-b276c66e6a82/windows-10-anniversary-update-1607?forum=winserverwsus&prof=required

    Sigh.


    Eric S.

    Tuesday, August 30, 2016 10:00 PM
  • We still have the same issue.
    The 1511 version clients showing as Not Applicable towards the 1607 Upgrade.
    I was thinking of reinstall the WSUS server, but based on Eric's comment it is not a big help.

    On the mean time we've upgraded 2 clients to the latest 1607. The new hotfixes started to download for the 1607 version on the WSUS server but now they are showing as Not Applicable towards those 2 clients.

    This sounds pretty bad as actually my plan B was to upgrade the clients manually (one by one) to 1607, but it seems to be useless as after that they won't receive any new updates from WSUS.

    I wonder why MS could not recreate the issue if there are a few of us having it.

    Gergo

    Tuesday, August 30, 2016 11:15 PM
  • I just found this post in a different forum/thread that worked for me to fix this issue:

    --------------------------------

    In my case, problem was in  group policy setting: Windows components - Store - Turn off the offer to update to the latest version of Windows.

    Proposed as answer by Anne HeMicrosoft contingent staff, Moderator 5 hours 30 minutes ago

    ---------------------------------


    Eric S.

    • Marked as answer by Eric Suger Thursday, September 1, 2016 2:45 PM
    Thursday, September 1, 2016 2:45 PM
  • I checked this and made sure it was not configured or enabled and we don't have it set to ignore the latest version of Windows. I'm glad it is working for some people but it is not the case in my environment.
    Thursday, September 1, 2016 2:56 PM
  • I set "Windows components - Store - Turn off the offer to update to the latest version of Windows" to disabled in my domain GPO.   Local group policy had no affect.

    After setting this GPO, I followed these steps:

    1. Rebooted the Windows 10 1511 machines.

    2. Ran "GPUPDATE /FORCE"

    3. RAN "WUAUCLT /DETECTNOW /REPORTNOW".

    Afterwards within WSUS Console it showed the Windows 1607 for Enterprise en-us as applicable.


    Eric S.

    Thursday, September 1, 2016 3:32 PM
  • We have the named GPO setting in enabled state (The Store - Turn off offer...), so it might has no connection.

    For some unknown reason over the weekend the WSUS server made up its mind and decided to show our v1511 computers as Needed for the Feature update v1607.

    Annoyingly I still have no idea what caused the issue and what solved it but it is working fine now (so I am happy after all)

    Gergo

    Monday, September 5, 2016 1:36 AM
  • Hello,

    I get the same problem, but none of the above tricks corrected it.

    Anything new about this issue?

    Thanks,

    David

    Friday, September 9, 2016 1:48 PM
  • Hi all,

    i have problem that no systems needed this update (Feature update for widows 10 1607) are grayout and report 0 (never client needed)

    

    Also if we approve the update in client, update it is not visible in client machine when we check update from wsus 

    All update Feature update for windows 10 have this  problem

    We have also reinstallaed wsus but again not work. We have follow this steps:

    -Install patch  KB3095113 and KB3159706  on the system windows 2012 R2

    -Install Wsus role

    -Done post install of  KB3159706 

    -Sync update

    May be that the patch they must be installed after install Wsus 2012 Role?


    Wednesday, November 16, 2016 6:03 AM
  • Hi all,

    i have reinstalled WSUS in windows server 2012R2 and now update appair in client.

    Tuesday, November 29, 2016 8:41 AM