New
#1
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?
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.
Last edited by cytherian; 17 Sep 2016 at 09:51.