This works for windows servers and it's fucking stupid
Open notepad. Make a change in the notepad window and don't save the change.
For some dumbass reason, likely burried deep on legacy code, the notepad save prompt halts the shutdown process.
this post was submitted on 16 Aug 2024
13 points (93.3% liked)
Windows 11
844 readers
1 users here now
Welcome to the community for Windows 11, Microsoft's latest computer operating system.
Rules:
- Do not promote pirated content or grey market keys.
- Be civil. No rude, offensive, or hateful posts/comments.
founded 1 year ago
MODERATORS
Does this prevent other running programs from getting the WM_CLOSE signal (or whatever the signal sent when the computer tries to shut down is)?
Also, Windows 11 Notepad seems to have no problem closing with unsaved text. I think it saves it to a temporary location. Do I have to get legacy Notepad back? (I've found instructions for doing that.)
It doesn't work anymore (at least on win 10) as there was a new notepad released that keeps unsaved content just like notepad++ does
I know for sure as I had notepad opened unsaved the other night and woke up to a rebooted computer with notepad opened and the content restored when I logged in
Damn.
I love this. Amazing. Imagine a mission critical server with an edited txt file just saying "DO NOT SAVE AND/OR EXIT!"
Or a proper gpo/registry modification as detailed: https://learn.microsoft.com/en-us/windows/deployment/update/waas-restart 🤷♂️
I've heard so many horror stories about values getting reset by updates that I don't trust it. That is to say, if my boss or coworkers told me this was what was required to keep the critical server from actually restarting then I wouldn't test it.
That's. Fucking. Insane. Like, it's a documented registry fix from Microsoft themselves. If you have a gpo pushing it, it's not getting reset. Also you literally just disregarded the way 90% of software makes configuration changes to your system, the registry.... Please tell me you don't work in IT because if you do your coworkers and end users must hate their lives.
Literally no need to be this condescending.
True, I do apologize. As an industry guy who deals with nonsense like that all day I suppose it struck a nerve but there wasn't any reason to respond as harshly as I did.
• Run regedit to open Registry Editor.
• Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU.
• If the keys don’t exist, create them.
• Create a new DWORD (32-bit) Value named NoAutoRebootWithLoggedOnUsers and set its value to 1.
(https://learn.microsoft.com/en-us/windows/deployment/update/waas-restart)
A batch file with "shutdown /a" or is it "shutdown -a" running every 1 minutes....
It's worth mentioning that you probably can't stop the reboot after the update. You're better off searching how to stop the updates or stop rebooting all together (like the trick mentioned about editing a notepad file).