Updating from Windows 10 Pro 64-bit fully updated. version 1511 build 10586.494
256 GB SSD with OS & essential apps [Office, Norton, etc.]
2TB SATA HD - all other Programs & Games, plus data [pictures, videos, documents, music]
1TB SATA HD - File History backup
16 GB RAM
i7 Intel Processor 4.00 GHz
Samsung 27" HD Curved monitor
Logitech unified Mouse & backlit keyboard
PC was running smooth as silk, all live tiles functioning as expected, NO browser crashes, freeze-ups, or non-responsive programs, no hardware issues.
Have tried to update to the Anniversary Update in various ways:
-- Manually ran Windows Update
-- Used Windows 10 Upgrade Assistant - disconnected all non-essential peripherals [web cam, all-in-one printer, phone], shut off anti-virus [Norton Security], disconnected my LAN after download was complete
--Tried Media Creation Tool
--Tried Media Creation Tool by using a USB Flash Drive
ALL resulted in same:
--Download & installation seem to go smoothly, no hangs, no errors
--Lock Screen Appears
--I Log In to Microsoft Account [NOTE: PIN does not work, even though that was the method I had been using; I am forced to use Password, even though the PIN option is still showing]
-- Windows goes through its multi-colored pages of "Hi," "Let's Start, etc."
--After that, the Window goes to black ... and stays there .. forever. Mouse cursor is visible & moveable but does nothing. Neither does the keyboard. Ctrl-Alt-Delete does not work. Error pops up: "The sign-in process could not display security and sign-in options when pressing Ctrl-Alt-Del. Please use ESC key or Power Button." Esc does not work. Have to use Power Button.
I tried rebooting into Safe Mode and that appeared to be a step in the right direction. I got in to Windows on the desktop, Start was there, my apps were there. Edge would not work. Windows Update seemed to hang with no progress.
So, I'm thinking, this being an Anniversary celebration & all, this really should not be so difficult. On a machine that was working perfectly, updating its OS should not cause a disaster.
The only positive has been that rolling back to the previous build has proven to be a piece of cake!
Very disappointed. I have spent the better part of the past 24 hours trying to resolve this, to no avail.
So, is this a common or known issue? I find reference to similar predicaments, but they are with test versions earlier on. How is it fixed without starting from scratch?