Two hot takes (so to speak):
Auto-updaters shouldn’t run when the system is really busy.
And installers that check to see the whether the same or newer version is “already installed” should either be really thorough about what they’re checking, or offer to do a repair install anyway.
I’d fired up a game of No Man’s Sky, which even after redoing the thermal paste and adding another case fan still pushes the limits of my system’s cooling, especially if I forget to wait for all the background processes to finish loading on Windows startup. I left a space station, landed on a planet, started mucking around with the structure I had found, and hit a waypoint pole to save again—
And the system shut down.
I turned it back on to get the fans running again and help cool off. Which worked. But when I logged in, I had a bunch of errors with Google Drive. Apparently its auto-update launched during my GPU-intensive game and overheated it enough to reach the shutdown threshold.
Fortunately, I’d just saved my game — or so I thought.
I spent about half an hour trying to fix Google Drive before I decided to just go back to the game for now.
No Man’s Sky picked up seamlessly…at the previous save. Maybe the write cache hadn’t been flushed yet or something. I’m glad I only lost about a minute of gameplay, though… I’ve got several hundred hours on this save file, and I’d hate for it to get lost or corrupted!
Anyway, back to Google Drive. I couldn’t reinstall it because I couldn’t uninstall it, and despite my efforts I couldn’t remove enough traces of it for the installer to be willing to run. You can read the whole reinstalling Drive saga on my troubleshooting site, along with the taskbar that lost its icons halfway through.
I eventually fixed it by copying the installed program files from another system and running the uninstaller manually. That resolved both the taskbar icons and the Drive installer being willing to run.
Then I dragged myself into bed.
Yeah, it was a fun Saturday night. 🙄