Hi, my computer updated to this latest version right when the May update came out and became virtually unusable until I manually restored to before the update. Now it just reinstalled it when I woke it up from sleep, even though I turned off updates until
the 11th of July.
Why I uninstalled it:
Log-in would take a long time to load, and then the whole screen would flash white at quick, almost random points (glad I don't have epilepsy). No applications could be opened. Sometimes I could see the desktop; other times the screen was otherwise black
except for the taskbar (which I couldn't click on; had the spinning cursor) and those flashing white lights; sometimes all of the above except for a tiny broken window that said "Personalization Settings" (presumably from something I frantically clicked when
I realized it was happening again). Last I checked, all my drivers are up to date. I'm running a CyberPower PC GMA4600BST and it runs great on the older Windows.
How I had to uninstall it:
When I'd use CTRL+ALT+DEL, the flashing would stop and I could easily select task manager. The flashing'd start up again and I would boot up CMD with admin rights using task manager and file>new task. The flashing white screen would basically be the computer
trying to switch the active window from CMD into something else, so when I would type the cd restore commands to restore to a previous version of Windows, I would have one hand clicking to keep my CMD window open and try and type one key at a time before the
random flashing would make CMD inactive again.
I've had to do this twice now. I know not having this update puts my computer security at risk, but like a lot of us, I have a ton of work to do on my PC and I'd rather just keep paying my bills as long as I can on an older version, haha.
Anyway, I'm fine uninstalling this version for as long as it takes to get a fix and don't need some more complex solution atm. But I didn't see this problem listed on the Known Issues article and I wanted it known.
ho ho just kidding--this second time gave me the same problem. Am still trying to restore it but... Welp. Hopefully this gets fixed soon. I also hope no one else has this problem (just for their sake), but in case you do--you're not alone even if it's not
on the Known Issues list! :D