• Angry_Autist (he/him)@lemmy.world
    link
    fedilink
    arrow-up
    39
    arrow-down
    3
    ·
    1 day ago

    Microsoft deliberately fucks with your video and audio drivers before a big update so you have to reboot

    This isn’t a conspiracy, it is a proven fact.

    • LH0ezVT@sh.itjust.works
      link
      fedilink
      arrow-up
      2
      ·
      10 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
        ·
        3 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.

    • felsiq@piefed.zip
      link
      fedilink
      English
      arrow-up
      12
      arrow-down
      1
      ·
      1 day ago

      Does anyone have a source on this? It’s 100% believable but I’m not turning anything up and this seems like something worth knowing more about