this post was submitted on 16 Aug 2024
12 points (92.9% liked)

Windows 11

831 readers
8 users here now

Welcome to the community for Windows 11, Microsoft's latest computer operating system.

Rules:

founded 1 year ago
MODERATORS
 

There appears to be no straightforward way to permanently stop Windows 11 Home from rebooting on its own after installing updates. I looked for workarounds but so far I have only found a script that has to run on a schedule to block the reboot by changing "working hours". (Link.)

Is that really the best that is possible?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] JackbyDev@programming.dev 1 points 2 months ago (1 children)

I love this. Amazing. Imagine a mission critical server with an edited txt file just saying "DO NOT SAVE AND/OR EXIT!"

[โ€“] Ptsf@lemmy.world 1 points 2 months ago (1 children)

Or a proper gpo/registry modification as detailed: https://learn.microsoft.com/en-us/windows/deployment/update/waas-restart ๐Ÿคทโ€โ™‚๏ธ

[โ€“] JackbyDev@programming.dev 0 points 2 months ago (1 children)

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.

[โ€“] Ptsf@lemmy.world 0 points 2 months ago (1 children)

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.

[โ€“] JackbyDev@programming.dev 0 points 2 months ago (1 children)

Literally no need to be this condescending.

[โ€“] Ptsf@lemmy.world 1 points 2 months ago

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.