• finitebanjo@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 month ago

    I’m sure a lot of people started taking unnecessary code executed at low levels a lot more seriously after the Crowdstrike fiasco.

    • Tux@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      ·
      1 month ago

      Well, Windows implemented kernel-level protection to prevent another Crowdstrike situation. lt actually makes kernel-level game anti-cheats to break.

        • far_university190@feddit.org
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 month ago

          Nope

          https://www.gamingonlinux.com/2024/09/microsoft-windows-kernel-changes-dont-suddenly-mean-big-things-for-linux-gaming/

          This new security platform, if vendors chose to actually go ahead and use it, could mean the oppositefor Linux gaming, and cause a whole bunch of new headaches when it comes to supporting it regardless of it being via Native Linux games, or Windows games through Wine and Proton. So if anything, I would say that rather than paving the way for Linux gaming to get better, it’s just going to be another hurdle. As annoying as that is.

          Just because some things may move out of the kernel-level, also doesn’t mean things will suddenly work on Linux (or get any easier to support via Wine / Proton). There will be various ways for developers to detect Linux, and continue to block it.

          Just look at Destiny 2 as the easy and simple example here, they very clearly check for and completely block Linux platforms from playing Destiny 2 via Proton with no way around it.

          Roblox is an additional easy example here to really make the point. Their latest anti-cheat is not kernel level, and completely blocks Linux. Something doesn’t need to be in the kernel to block Linux-based systems.

  • LovableSidekick@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 month ago

    Getting ready to go back to Linux, just waiting to get some other stuff out of the way. Taskbar autohide on my Win10 box stopped working this morning. Minor annoyance, I looked it up and found a simple fix - restart the Windows Explorer process. Okay, did that, autohide started working. Bur srsly, the taskbar is almost 30 years old, low-level shit like this SHOULD JUST WORK. Now 12 hours later I just noticed it’s not working again. What the Actual Fuck, guys? Unbelievable.

    • 0^2@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      1
      ·
      1 month ago

      chkdsk /scan If any errors found, stop and /f them

      Then:

      DISM.exe /Online /Cleanup-image /Restorehealth

      Finally:

      sfc /scannow

      • InFerNo@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        1 month ago

        Is that command line stuff? Hard pass for Windows users.

        Edit: I guess the Windows users didn’t like that joke

        • madeline@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 month ago

          yes, it is. those are pretty much the definitive windows commands to try to fix random stuff like this too, if they fail then it’s reinstall time lmao