Linux machines don't crash unexpectedly, because if they do, it's your fault for configuring it wrong and you should have expected it.
Windows machines don't crash unexpectedly because it's Microsoft and you should have expected it.
Hum... Hardware does still fail at random.
Or you just decided to update all your packages like a madman whilst not running on a Debian based distro
Bruh, if a package update breaks something, I just roll back the BTRFS snapshot.
I saw that happen once in a big presentation.
There was a team of students presenting their work to ~200 people. Right in the middle, a pop-up says updates are finished and the computer needs to restart. It has a helpful 60-second countdown, but “cancel” is grayed out, so all they can do is watch.
I was only in the audience and I still have nightmares.
shutdown.exe -a should take care of situations like that. It's not an excuse for taking away your options on the UI though.
What about all those update skippers that start complaining to Microsoft when their system breaks because they don't understand that updates are crucial for a good running system?
I get why Microsoft forces it now on the Home editions.
Does that require admin access? It wasn't their machine, it was one the school provided for the auditorium.
By default a normal user can abort the shutdown. They could also configure group policy to prevent shutdown permissions which also prevents aborting a shutdown.
The GPO is Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment > Shut down the system.
I don't want to be that guy, because I still hate Windows, but... most people who have these problems just didn't set up updates properly. Well, that, or they never restart their computer.
Greyed out options like that almost always mean the person has been hitting cancel or delay for several warnings already.
This wasn't their machine, it was one the school provided for the auditorium.
And someone still had to configure that
Fresh memes just for this post
FR3SH
Unfortunately as a linux user you may get stuck-on-post syndrome but there are widely available immunizations and treatments available.
I've used Windows since the late 90s and I've had infinite blue screen loops before. probably a hardware issue but it's not like this fear is irrational.
Seemingly once a year my windows machine goes into an infinite loop of bluescreens. It's because of my wireless/bluetooth card everytime.
Windows will update the driver during one of it's bug updates, fail, then I have to go into safe mode and install the correct driver. Then it's business as usual.
Windows doesn't seem to care that I told it to never update my drivers, it'll still do it once a year.
For me, it's not that Windows updates my drivers during a big update. It's simply that Windows broke the driver while installing a big update.
I've had it happen where my Wi-Fi driver broke so it could only connect to an unprotected network. So I'd simply setup my phone as a hotspot and download the Wi-Fi driver from the manufacturer's website and reinstall it. That'd immediately fix the issue. Though, actually, that issue hasn't occured in years. The last time it happened, I think, was in the early years of Windows 10.
My kernel panics in fear of Blue Screen syndrome.
Those who know...
Wow, I'm having this issue right now. Forgot my current laptop at home, so I took out the old laptop which hasn't seen an update in months.
Now it has randomly crashed, as one does (reason why I asked for a replacement) and I'm here waiting for windows to install all the updates...
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
