image caption: A Microsoft Windows screen showing “Active Hours” with start time set to 12 AM and end time set to 12 AM and an error that says “Choose an end time that’s no more than 18 hours from the start time”.

    • superkret@feddit.orgEnglish
      121·
      2 months ago

      Same goes for Linux and macOS, actually, but Linux will happily let you keep your machine vulnerable to getting hacked for months.

      Linux “reboots” every program and service it updates separately.
      So the only update that needs a reboot is one of the kernel, which doesn’t happen often.
      With Enterprise Linux, you can update the kernel without a reboot, too.

        • expr@programming.devEnglish
          1·
          2 months ago

          Obviously there’s a small handful of things that would require a reboot, but unlike Windows, the vast majority of programs in user space don’t require reboots on update.

          There’s also the fact that restarting Windows to update is a much slower and more disruptive experience than restarting Linux.

        • Kusimulkku@lemm.eeEnglish
          1·
          2 months ago

          That’s why Linux and software like Firefox constantly complain when you haven’t restarted after an update.

          Can’t confirm. Linux hasn’t complained and I don’t remember Firefox complaining. Maybe it doesn’t happen with the flatpak

            • Kusimulkku@lemm.eeEnglish
              1·
              2 months ago

              I have zypper ps -s as part of my update script so I personally notice through that when something needs to be restarted. It’s pretty rare to have to do an actual reboot. A lot of the software stores notify if you need to restart. I’ve seen it on Discover and GNOME Store (?) at least

      • corsicanguppy@lemmy.caEnglish
        2·
        2 months ago

        the only update that needs a reboot is one of the kernel

        Okay, that’s not true. Glancing at dbus sideways will result in a reboot. But in systems free of systemd and all its entourage of shit, that’s still true.

        • Something Burger 🍔@jlai.luEnglish
          1·
          2 months ago

          dbus is 4 years older than systemd, thus proving once again that systemd haters have no idea what they’re talking about.

        • superkret@feddit.orgEnglish
          1·
          2 months ago

          But in systems free of systemd and all its entourage of shit, that’s still true.

          OK my bad, I don’t run systemd.

    • azuth@sh.itjust.worksEnglish
      42·
      2 months ago

      ROFL

      If Microsoft really cares for more users keeping their system updated they should fix their update process.

      While some updates require a reboot on other OSes for them to take effect they don’t require work during the reboot maximizing the downtime.

      Which is on top of the work done before rebooting, on the background, unprompted, destroying system performance.

    • kautau@lemmy.worldEnglish
      42·
      2 months ago

      With windows pro you can use Group Policy to disable them completely actually, though it’s obv not a good idea

      Open Group Policy Object Editor. Navigate to Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Update. Set Configure Automatic Updates to Disabled.

    • Kusimulkku@lemm.eeEnglish
      11·
      2 months ago

      This is because many (most?) updates aren’t actually applied until you reboot. Same goes for Linux and macOS, actually

      Yeah no for Linux at least.

    • corsicanguppy@lemmy.caEnglish
      22·
      2 months ago

      Same goes for Linux and macOS, actually

      laughs in needs-restarting -s

      It’s weird that RPMs have been restarting apps affected by library updates for decades and you still haven’t clued-in. You new?

    • lightnsfw@reddthat.comEnglish
      22·
      2 months ago

      Mine doesn’t reboot on it’s own and I don’t recall ever changing any settings to prevent it other than messing with the thing OP is talking about which wouldn’t let me turn it off. I get nag screens daily after a while but it never actually restarts. Maybe one of my applications prevents it or something.