• LH0ezVT@sh.itjust.works
    link
    fedilink
    arrow-up
    2
    ·
    19 hours ago

    I think it is more that the update fucks with drivers? As in, updates bring updated stuff that probably interferes with still-running old stuff.

    • Angry_Autist (he/him)@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      12 hours ago

      If my experience is common, the update ‘pre-loads’ some non-locked system files as time goes on while the update is downloaded but not technically applied by the tool. So these files get changed without a reboot, and while you may not be using them at the time of overwrite, when you next load them, there are subtle incompatibilities with the previous version and your active data.

      Kind of like ‘The dll was replaced by the exe is still the old version’, and this causes a ton of small but annoying glitches, crashes, and odd audio behavior.

      Untill reboot, which happens less and less often now that windows doesn’t bluescreen every few hours.

      My conspiracy is that they are aware of it, and do not change it despite the risks it provides, to keep everyone in line with their update schedule, denying the user the rights to control their own hardware, again.

      • LH0ezVT@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        8 hours ago

        To be fair, the very same thing happens with Linux, when you install updates but don’t restart services (or, god forbid, the whole system). Really weird tiny issues accumulate until I am fed up and hit reboot.