Missing Aniversary Update

BradTheGeek · 23 Mar 2017

Howdy. I work for a small IT firm and we have been auditing our clients. In this audit we have found a large percentage that have never received the anniversary update.

One client in particular with over 50 PCs (Win 10 pro) has about 60% still on build 10586. I have spot checked some of these PCs and they are getting cumulative updates with no failures but still no Anniversary update. Checking for updates reveals that the PC is up to date. Defer upgrades is not on, and there is no Group Policy in place that should affect this.

On one I tried to force the Anniversary Update by using the upgrade assistant, and it got stuck at 98% for over 5 hours. This particular PC had some other strange windows issues, so it could be an outlier and we decided to wipe and reload this particular PC.

I will be attempting to upgrade some of the others today. However, has anyone seen anything like this? Do you have any pointers as to why? With the creators update coming, and who know what in the future, I assume that MS will eventually stop supporting older builds like they did with Win 8/8.1 and I want to ensure our clients are not stuck in that position.

Thanks for any pointers.

(Edit for typos)

dalchina · 23 Mar 2017

At this stage, from one point of view I'd say don't spend time on the anniversary upgrade+ large subsequent cumulative update, and wait for the creator's upgrade - BUT - on the other hand, best wait for the dust to settle on the creator's upgrade on the 'Fools rush in' principle. I'd allow a couple of months before applying the Creator's upgrade.

There are many reports of difficulty applying the anniversary upgrade which you can research on this forum (just search e.g. "Solved anniversary update failed" or "anniversary update failed" and elsewhere- sometimes this is resolved by first doing an in-place upgrade repair install.

Example case (solved):
Anniversary Update Failure
https://www.tenforums.com/installation-upgrade/58463-anniversary-update-no-go-here-2.html

You can try checking the appropriate log files of course.

Also make sure there's at least 500Mb of unallocated space on the system drive.

BradTheGeek · 23 Mar 2017

Thanks for the reply. I had searched and found that thread but it did not really help. My problems are two-fold.

1. More from curisosity, why is Windows itself not detecting/attempting the upgrade that was released in August 2016. The googlinator states that the plans were to have it completely rolled out by Dec 2016.

2. The main solution presented in that thread is to use the ISO. These machines are spread across 5 offices in the state. We mostly manage them remotely and using the ISO will require a much larger amount of travel and on-site time, where if I can make it work remotely I can just monitor upgrades while working on other tasks.

dalchina · 23 Mar 2017

Appreciate the issue. For those machines where the upgrade fails, that would be a problem.

For the major issue- why not yet received- just wondering if you have Defer Upgrade set? Some ideas here which you've probably found already.

Why Your PC Hasn’t Received Windows 10’s Anniversary Update Yet and How to Get It

http://windowsreport.com/windows-10-...7-not-showing/

BradTheGeek · 23 Mar 2017

No. That was one of the first things I checked, defer is not on. I even tried turning it on and off again just to see. I looked through event logs, checked group policy settings on the DC, tried checking a probem PC with SFC, and then I hit a wall.

You mentioned appropriate log files. Can you point me to some other than event viewer. Maybe CBS log, but not sure if that is the right place to look.

FWIW Google and an imaging program are some of my best friends. I use terabyte tools Image for Windows and Image for Linux. I have a 36GB server I built just to keep system images for machines that hit our shop. Other than failed drives, imaging a PC is step one one anything that walks through the door.

dalchina · 23 Mar 2017

How to push updates through network from single location - WSUS Forum - Spiceworks

- if you can't fix 'normal' distribution of the anniversary edition, there is another way. However I have no experience in that, or how much work might be involved.

Article including log refs:
https://technet.microsoft.com/en-us/...upgrade-errors

BradTheGeek · 23 Mar 2017

I was thinking about WSUS myself but like you I do not have much experience with it. However I have managed to force update 2 of the PCs remotely today without the ISO, so the one that would not may have been an outlier.

Now I have a logistics issue in scheduling the attempt for all of these, but that is something I can manage!

Thanks.

Bree · 23 Mar 2017

BradTheGeek said:

No. That was one of the first things I checked, defer is not on.

Defer is no longer available for 1607, not now that it's on Current Branch for Business.
Windows 10 1607 is now a Current Branch for Business (CBB) release

1607 being CBB also triggered end of support for 1507.

...the 60-day grace period for Windows 10, version 1507 will begin. That means, after March 26th, 2017, Windows 10, version 1507 will no longer be serviced as only the two most Current Branch for Business (CBB) versions are actively serviced.

No more updates to original Win 10 version 1507/10240 after 26 March?

Looks like support for 1511 will continue until 60 days after the Creators Update becomes CBB, so at least you have plenty of time to sort out your upgrade issues.

erpster4 · 28 Mar 2017

Bree said:

Looks like support for 1511 will continue until 60 days after the Creators Update becomes CBB, so at least you have plenty of time to sort out your upgrade issues.

No. Support for v1511 will continue almost indefinitely until Microsoft makes an official announcement as to when they'll stop issuing updates (aka "end of servicing") for Win10 v1511. MS only made an announcement for the end of support for v1507 only, not for v1511.