Windows 10: Windows 10 to "anniversary" update FAILS... no message... no clue

I finally managed to get my laptop running on Windows 10. All was fine, running build 10240 (RTM, Threshold 1). But then the Windows Upgrade assistant informed me that I'm on an outdated version of Windows 10 and that I should update. Apparently it is pretty massive, an "anniversary update", so it's treated like an "upgrade" rather than a behind-the-scenes update.

Well... after 45 minutes of all this "progress" and work, the process simply FAILED. Windows was successful at "restoring the previous version." OK... but... after this, NO INDICATION of what went wrong. Launching the Windows Assistant for updating is all enthusiastic about helping me "update to the latest and most secure version of Windows 10"... with nary a clue that the previous attempt failed.

I'm AGHAST at how troublesome Microsoft has become with installs. This is the absolutely most terrible O/S upgrade experience I've ever had, going from 8.1 to 10 and now 10+. It's atrocious to see so many "hoops" that need to be leaped through without Microsoft taking the initiative to make this process an efficient and productive one. I cannot image how anyone who is a novice or with "general" Windows experience could manage this, without resorting to hundreds of dollars in support fees. It's a disaster on usability, and makes Apple seem like heaven.

Nevertheless... painful as it is, I'm on Windows 10 and would like to be "more secure" with the latest. Any clue as to what I can do to find out what choked Microsoft on this and how to get over it? *Mad

Going to Windows Events for "Setup" showed nothing, but "System" showed a plethora of DistributedCOM error messages. "The application-specific permission settings do not grant Local Activation permission for the COM server application." Failure to register with DCOM. And other Service Control Manager errors... timeouts.

Apparently there is some deliberate "Microsoft Windows Update Troubleshooter" program available... that Microsoft doesn't proactively tell you about. You have to "discover" it and then download from their site... to then analyze your system. You figure they'd at least point you in that direction after an update failure. I ran this, which fixed some kind of "Service registration is missing or corrupt."

Now... wouldn't Microsoft Windows run some kind of diagnostic like this FIRST before attempting a lengthy update? As part of the "CHECKING TO SEE IF YOUR PC IS READY TO BE UPDATED," or some other such sensible action.... instead of wasting people's time.

Hopefully I'll be able to come back with an update that comes with a happy ending.

:)

 

Enter on keypad " no. + # "

petrib is correct. It is a shortcut to SIM numbers.

Numbers on your SIM might not be in the position you think. Just because they appear sorted in alphabetical order in the contacts list doesn't mean that they appear in that same order on the SIM. On the SIM they appear in the order in which you input them,
unless you delete a number in which case the next one entered takes its place.

 

Enter on keypad " no. + # "

Hello guys :smileyhappy:

There's something make me crazy :s
When I click a certain number on keypad on any NOKIA mobile
Then click the symbol " # ", then a number of
a contact "in my contact list" will be appeared.
Is there anyone know how is that???
I feel curious toward this puzzle :smileyvery-happy:
OK., if anyone know about this topic, please tell me :smileysad:
Anyway thanks :smileywink:

 

No... despite the "diagnostic" tool repairing things... installation still failed. Somewhere after 50% done. Whole thing rolled back. This is insanity.

I ran the diagnostic tool again and this time it didn't come up with any issues "cannot find any problem." Exasperating. Something tripped it up. No log? Nothing to interpret?

Anyone have some advice other than scrapping the whole operating system and going to some minty flavor of Linux?

 

I take it that you're running the upgrade online.

I suggest downloading the .ISO and upgrading using that. In my limited experience, it's likelier to complete.

https://www.tenforums.com/tutorials/9...-download.html

You don't need to create a bootable DVD or USB flash drive to do the upgrade. Win 10 can mount the .ISO as a virtual drive, and you can run the upgrade from that.

 

Using the Win8 to 8.1 terminology it would now be Win10.2 [example would be Version 10.0 in July '15, Version 10.1 in Nov. '15 and Version 10.2 in Aug. 16] but numerology has changed and there is the Version number and Build numbers for each of those, e.g. Version 1511 Build 10586.82, Version 1607 Build 14393.105, with the build number changing with updates. Press the Windows key and the R together to get the Run box, type winver and press enter to get the Version and Build numbers. Also right-click the Start icon and choose System to get more. There's 2 types of Win10, Home [or core] and Pro in the RTM/Released version and the Insider Preview [BETA or Test] version.

 

Thank you. I didn't realize this was available as a full download. I'll give it a shot and report back. *Smile

 

You should have two installation folders on your C drive for the failed installation. Find the error logs and look towards the end of the file to see what caused the error. See https://msdn.microsoft.com/en-gb/win...and-event-logs

 

Third party, resident AV programs can interfere with upgrades.

 

Hi there

Actually I've been rather pleasantly surprised with the ease of upgrading initially to W10 (to get the "Freebie") and then doing install from scratch.

Had almost zero problems - mainly minor glitches which were soon fixed either by updates from Ms or help from this great Forum.

I only have 2 outstanding issues

1) Networking just seems totally random -- sometimes it works seamlessly, other times a Single computer that seems 100% identical to another in the network just refuses to show up whatever you do - in extreme cases a total windows re-install is the only way I've got it to be fixed.

Windows Networking though has been its weak point ever since they started with networking - I believe they used an old DOS LAN system at first from the fledgling Novell corporation at that time (Windows 3 / 3/1 / 3.11 for workgroups).

2) The NTFS file system with the 240 char or so name restriction (that includes the directory or folder name).

I have loads of music folders with long directory names and even longer track names and I'm not renaming those - it would take days and is a bit of a pointless task since I'm serving those files up on a Linux home built NAS server to TV's / phones etc.

For the rest I'm quite happy - everything works including some quite unusual hardware - and running back level of Windows as VM's such as XP for really old legacy devices works just fine too.

So at least (apart from the 2 points I've mentioned) I'm a happy customer and don't subscribe to the "Evil Empire" theory that a lot do by saying Ms has become a totally useless and evil corporation.

Cheers
jimbo

 

That is your software not NTFS or Windows. I have the same problem with SqueezeBox Server (not sure if you use that) but it isn't an OS problem and certainly not a NTFS problem. The developers just wrote it as it was at the time and haven't updated it.

Other than that I agree with you - I'm happy with it.

 

Allegedly AU version allows long filenames now but you have to enable it - never tried it though.

How to enable NTFS Long Paths in Windows 10

 

Your program will not use long (path) names if it is hard coded not to.

The maximum file name length has not changed. The maximum length of path name has.

That is you can now have C:\Users\Hali\<50 characters>\<50 characters\<50 characters\<50 characters\<50 characters\<50 characters\<50 characters\(etc)\myfile.txt

You can't have C:\<500 million characters>.txt

The issue is old programs assume the old limit.

I use Squeezebox server (and I think Jimbo45 does too). In that program it is hard coded not to let the entire path exceed a certain number of characters - even though Windows now does.

NTFS (afaik) never had that restriction anyway.

 

OK... some updates.

I tried to get assistance from the Microsoft Community, but the Microsoft MVP who tried to help me was FIXATED on Norton, because I had it installed some time ago. Even though I told him REPEATEDLY that I completely uninstalled it, used the Norton Removal Tool, and had manually CLEANSED the registry after UNINSTALLING all Symantec software, he could not let go... kept asking me when it was done. Dates seemed very important to him. He was also fixated on Defender having the latest definitions. Of course it had the latest -- Windows 10 controls the update of it completely, not giving the user the opportunity to refuse updates.

I attempted this anniversary update 6 times now. *Mad

The 2nd to last time it failed, I got this error message at around the 60% progress mark on the 2nd (last) phase of the install:





At this point, I had done the following:
1) Uninstalled my Avast! antivirus completely (before I had permanently disabled it - Windows warned me of no active anti-virus program, so I assumed I was OK).
2) Ran the windows update diagnostic tool - no errors.
3) Ran SFC /SCANNOW - no errors.
4) Ran DISM /online /cleanup-image [/scanhealth /checkhealth and /restorehealth separately] - no errors.
5) Disabled ALL non-Microsoft services
6) Ran the Windows Update Diagnostic, which did not find any errors.
7) Ran TaskManager to identify and stop any 3rd party running services.

Lastly, I discovered that there was a KB update that was not installed, and Windows just didn't seem to recognize that it needed to be installed. So I used WHDownloader and installed it. This was KB3172987. I repeated steps 1~7 above.

I tried the installation AGAIN. This time it failed at 71%.







The "STOP CODE" URL is completely useless. It doesn't tell you anything to help troubleshoot the problem.

Now, when I logged back in after Windows rolled back to the original Windows 10, I did NOT get an error message screen informing me of why the installation failed this time.

I'm... perplexed to say the least.

Does anyone know where I can find some kind of log about the last error encountered that caused the installation to abort? Event Viewer seems to be useless in this regard. I checked ALL nodes (application, system, setup, security) for the timing when that failure occurred, and there was nothing logged...

 

See my post 6. Did you check the installation error logs which should give some clue why the installation is failing? You need to look in the first 3 locations here https://msdn.microsoft.com/en-gb/win...and-event-logs