The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
The worst I have had is my PC updated and rebooted overnight.
This happened to me the other morning...
You're in a dark cave looking out over a deserted beach...nevermind, just a 'scheduled' restart!
VS restarted the last two projects I had open, good.
Excel also restarted the half-dozen spreadsheets I had open (in recovery mode)...also good.
Multiple browser windows also opened, all to the home page...not great, but not that important either.
SSMS launches and waits for connection selection, but of course, none of the tabs I had open the previous night recovered...nothing lost really, but annoying to get back to where I was.
Notepad apparently has no ability to recover unsaved files...my scratch areas/notes from the previous day are just gone!...again, not terribly important by annoying nonetheless.
So, while I'm thankful that most applications I use can recover from these unattended restarts, it still costs me time and effort when I'm caught off guard.
I have tried multiple 'fixes' to prevent unattended restarts, but none have worked so far. I'll just have to be more diligent to make sure not to leave anything open/unsaved overnight that I can't stand to lose.
Booted up to the dreaded "don't turn off your computer, we are busy screwing it up" message. This was followed up by a large representation of the command prompt... eg: black screen. Nothing worked but task manager, who was not very busy.
After 3 reboots and a copious amount of 4 letter words, it is (almost) back to normal. Until we meet again. Fortunately, virtual machines are easy to back up. But then MS would just update it again.
Insanity: doing the same thing over and over expecting different results. <sigh>
Thanks for ignoring
Arguing with a woman is like reading the Software License Agreement. In the end, you ignore everything and click "I agree".
So you encounter problems when running Windows on top of Mint, while literally hundreds of millions of people have no problems when they do NOT run on top of Mint but on real hardware.
Then it MUST be the fault of Windows, not behaving the way Mint requires! That should obvious to anyone. Linux behaviour is an axiom that lies there as a basic foundation that cannot be questioned or challenged. By definition, it cannot have weaknesses: It is stated, not proved. Like the digit 1 - it simply is. Unarguable. The error is, by definition in the use of that digit. So it is with Linux: The error is not in Linux but in the use of it.
Except I've had no issues with Windows 10, updates or otherwise, but when I used Ubuntu last year, it was endless pain. (Early last year I installed Fedora on a system--vs VM--only to have it brick the system, which was odd since I've never had a single issue with it in VirtualBox [on the same system and others].)