So, windows 10 anniversary update is upon us as im sure your all aware, Being that i spend most of my time in a linux terminal i was very excited to get into bash on windows...
Left it till later at night when i could push through the update, to find A horrible experience to say the least...
Upon updating, my taskbar had no rightclick functionality, Notification center would not work. Startmenu locked up when opening, Settings panel would not load no-matter how hard i tired.
So ofcourse, being past the "Do not turn your computer off screens" it makes sense, Lets try just a clean System reboot, from the ctrl alt delete menu.
Once the system rebooted, i was met with my login screen background missing.. strange but okay? upon logging in both my desktop and taskbar were flashing like crazy.
Below are two snaps i took of it, If flashy things aren't the best for you, Please don't watch.
https://www.dropbox.com/s/scfrtja9imu60ts/2016-08-03_23-55-59.mp4?dl=0
https://www.dropbox.com/s/xaiisp43xktwcni/2016-08-04_00-24-15.mp4?dl=0
After 3 hours of fighting with SFC, DISM in windows (which while blinking it is practically like someone mashing a mouse all around your screen, makes typing the worlds most frustrating task!), Safe mode (Please add F8 back in..) and Window RE/PE? I have finally given up for the night, and restored back to my original build.
As a one more last ditched effort to get things up and running, i used msconfig to drop down to Diagnostics Startup. Turns out, this disables the ability to get to the login screen! leaving me with a machine which is a great spiny circle simulator! - This is where the F8 key would have been great rather than literally having to hard reboot until windows itself forced the repair bootup...
Between windows 10 resetting filetype associations on installations, Random applications uninstalling, I'm certainly not a fan of doing the big updates but this one has been the most painful.
I've seen links to this sort of error being antivirus's conflicting, I run Windows Defender and Spybot, so unlikely to be the case. Graphics drivers popped up as another one, I did try removing my Graphics drivers completely only end making the pain into sandpaper on my eyes!
Disabling event and problem reporting services had no affect at all, They were still being fired up while looking at the service it was clearly stated that it was Disabled and Not running.
I should have snapshoted the error when i first pulled it up in eventviewer, but explorer was constantly being logged as a crash, error message had no indication of child processes, injected dll points or whatever to make the problem any more clear however.
Rants aside, does anyone have some serious advice? @nathan maybe? without just reinstall windows..