this post was submitted on 14 Jun 2025
929 points (98.0% liked)
memes
15612 readers
2825 users here now
Community rules
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 [email protected]
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.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- [email protected] : Star Trek memes, chat and shitposts
- [email protected] : Lemmy Shitposts, anything and everything goes.
- [email protected] : Linux themed memes
- [email protected] : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I have to use Windows for work. A few days ago I pressed the button to update and shut down as I started preparing to leave. I went away for a bit and when I came back to get my stuff, the computer was back at the login screen. It updated and restarted. Windows really does do that. I hate it.
I don't think I've ever had that happen - maybe it's a group policy thing or something?
Probably just misclicked and blames it on the OS.
"this has never happened to me, therefore this can't happen"
As an IT technician with a decade worth of user support and systems admin experience.
This is by far the most probable explanation.
I am not saying it 100% is the problem, just that user error is by far the most common issue I encounter.
I'm also an it technician with over a decade of experience, and I've seen this first hand, on multiple occasions.
I agree PICNIC is the goto in this scenario; it's not like shutdown commands are new, so why would it not work as intended? it was my initial assumption when faced with these reports; but having seen this occur multiple times, I can confirm it isn't. My running theory is it's KB related, as the issue is intermittent by device (though consistent with an affected device.. as in the device will exhibit this behaviour every time). It's also unique to windows 11.
Interesting, thank you for your thoughts, since I haven't seen it in person it is hard to get my head around it.
I completely understand. I'd be skeptical too had I not seen it firsthand