This article talks about the “your machine is not yet ready to update” error message, but it’s pretty vague.
IMHO, the best thing to do with Windows is to say “yes” when it wants to do an update, but not actively seek update (i.e. don’t click on “check for update”). That should be sufficient, and also, there were some reports a few months ago that said clicking on “check for update” sometimes downloads beta versions that aren’t fully vetted.
I wish I could say that. Despite having nothing open when I okayed the update–the request came when I started to shut down–I still lost parts of all the documents I’d been working on that day.
Specifically, when I logged on today, I noticed none of those documents appeared on the desktop where I’d left them. I opened Word and from the list of ‘recently worked on’, chose each one in turn and opened it, then saved it to an existing folder, then dragged it from the folder to the desktop. On opening, I found each in the state it had been two days earlier. In other words, two days of work missing.
I looked online for information. Most pages advised opening the “windows.old” folder from File Explorer > Drive C. Nothing was in any of the document folders I reached via windows.old.
I have no idea if there was something I could have done to prevent this. I post in case it might help someone else, or in case it generates some advice that might be relevant.
I use it to get exactly what portion of the screen I want, give it the name I want, and put it into the folder I want, and be able to copy it right out of the tool into a document. Why would I ever use print screen?
What Exapno Mapcase said. I used Print Screen all of the time back in the day, when there were no better options. I love the Snipping Tool so much that I don’t even use Snagit anymore.
(Snagit’s main usefulness was being able to capture a scrolling window, but in previous versions of Windows that feature only ever worked in IE and now I can’t get it to work in Edge. One of these days I’ll uninstall it.)
IIRC that didn’t locate my driver issue. It did clean up some errors in the update process from the borked installation that potentially could have caused later issues when I retried.There was something like an advanced report hypertext on the message, like yours, with the failure that showed my actual issue.