Windows 10: Long update wasn't the Anniversary Update... what was it?

Strange things are happening here on my W10x86 Pro system, and I am worried...

After being shut down for some time, I turned on this computer yesterday Monday, and it finished configuring some updates that it had apparently installed last time I shut it down. When shutting it down on Monday evening, it again goes into installing updates, but looking like it was stuck on 0%. After an hour I just let it sit over night, and this morning it had shut down. Then today when I turn it on in the afternoon, it goes into configuring a big update, before booting up, taking close to 30 minutes and restarting three or four times, showing me this screen
http://blogs-images.forbes.com/anton...w10-update.jpg that I have never seen before.

After the half hour it tells me that it has updated my W10 and there are lots of new exciting things. Naturally I thought that this was the Anniversary Update, so I looked into the Update History, and to my surprise this was entirely empty. "No updates installed yet", it told me.

Then I manually clicked "Check for new updates", and then it finds lots of updates, like "Cumulative Update for Windows 10 Version 1511 (KB3176493)" and a whole bunch of other updates all numbered with 1511.

I am baffled here... what goes on?

:)

 

Windows 10 Anniversary update fails to install 76% into the installation process

Hi All

Windows 10 Anniversary is not installing

Received the update via windows update and it failed during the restart and installation phase.After that it wasn't present in windows update.

I then deleted the anniversary update files from C/Windows/SoftwareDistribution/Downloads and also the anniversary files from C/

then downloaded the windows 10 update assistance from Microsoft and it downloads the windows 10 Anniversary update and does the same thing, restarts and installs and then fails at 76% and restores the pc.

What can I do ?

Using Lenovo flex 2 14 on windows 10 version 1511

 

Windows 10 Anneversary Update

You can certainly update to Windows 10 Pro v1511 via ISO as that is what I did. I wasn't getting the Nov update at the time.

Not sure about the anniversary release so I might be best to update to v1511 first.

 

What does "winver" show?

 

How long was this system turned off?
That update in the picture looks like the major upgrade to 1511 back on Nov 2015 and all previous update history is cleared with major upgrades. You need to run all those updates to catch up then see if you get the 1607 upgrade. If not you can download the 1607 ISO and use it to upgrade.

Jim *Cool

 

Running into something similar here, with what is the Anniversary update (updating from prior build, per winver). One computer was stuck for hours on "Configuring Update.... 99%"

Finally gave up and did a hard power down (not too worried, as had a recent disk image to go to). Took a couple of power ups to get it booting back into Win 10 - the first time it saw the SSD but didn't see any "boot executables" (if I interpreted the messages correctly).

When entering the "Check for Updates" dialogue, it shows the Anniversary update as available to install and requires a reboot. The power options show "Update and Shutdown", and "Update and Reboot" - after multiple attempts, neither actually triggers the update to install.

My guess is I need to reset the windows 10 update, as the following link instructs, but want to check here first if anyone who has had a similar problem if something else might be the real cause.
https://answers.microsoft.com/en-us/...?page=1&auth=1

This is a tough one to research as a google search brings up "upgrades" (as in Win 7 to Win 10) as synonymous with "updates", since nominally the same process is involved - many end up suggesting downloading and installing from the ISO - already done that for other problems and the system was working just fine before these updates.

Editorial: If MS is forcing updates to run, then it ought to have a flawless update process. Probably tons of small business people getting into panic mode when something like this happens. I'm now looking at turning off auto updates and running them on an independent schedule that we have better control over, and can be monitored. (Yes, I am aware that they can be scheduled, but our schedules don't always consistently run that way - besides, hung for hours at 99% is still a problem, so still need someone to babysit it).
Disable / Turn Off Automatic Updates In Windows 10, Here's How | Redmond Pie
Turn off Automatic Updates in Windows 10 - 4sysops

 

OppfinnarJocke has a Surface Pro 3

Is there a different release cycle for tablets?

Microsoft Surface Pro 3 update history | Surface firmware updates

and this article is odd:
Windows 10 Version 1511 and Version 1507 receive new cumulative updates
Tuesday, Aug 9, 2016

The builds are cumulative aren't they. You shouldn't have to upgrate to anything but 1607.

 

Lately there have been a number of small updates in addition to the Redstone 1 Anniversary update many are running into snags on. Either the RS1 fails to appear in the WU as was seen here on multiple systems or the updates will hang for some unknown reason where the Windows Update Troubleshooter tool needs a look!

For the more experienced users familiar with custom installing Windows as well as upgrades and partitioning, formatting drives the solution found here when the RS1 didn't show was to download the MC Tool's "windows.iso" directly and then mount the iso in order to manually start the setup.exe file which then saw the upgrade to update take place. For the most part the upgrade installs went smoothly on the three desktops and a 10 laptop that were involved.

 

As a low internet bandwidth user for a long time till now, I never use Windows Updates to upgrade Windows. Always download the ISO and mount it, did not encounter any sort of issue.

Before that, you'll have to get your old version of Windows fully updated, this will give the upgrade process runs smoothly.

 

That will eleviate any number of small loose updates like Windows Defender in particular that tends to gum things up a bit at times. I have noticed that along with each newer build that comes along including the updates(Threshold 2 last November, Redstone 1 Anniversary present time) there'll be one WD update being a constant! And that will always have to finish up before the next new build even starts to unpack and install.

 

Thanks for the comments and ideas. I'm sorry for being away from this thread for so long...

This all happened to me on my W10x86 running in Virtualbox 5, so maybe Jim has a point. However, it sure has not been off the web since November 2015...

On my Surface Pro 3 I finally got the AU, after 4 tries and a lot of 1511 cumulative updates in-between. It seems as if the SP3 had to first install those, even though it had the AU available, and tried and failed three times before finally succeeding.