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?

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    3 months ago

    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.

    • ArbitraryValue@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      3 months ago

      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.)

    • Unforeseen@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      3 months ago

      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

    • JackbyDev@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      3 months ago

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

        • JackbyDev@programming.dev
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          3 months ago

          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
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            1
            ·
            3 months ago

            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.

              • Ptsf@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                ·
                3 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.

  • cooljimy84@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    3 months ago

    A batch file with “shutdown /a” or is it “shutdown -a” running every 1 minutes…

  • JackbyDev@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    3 months ago

    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).