Microsoft said its update wouldn't install on Linux devices. It did anyway.
  • ExtremeDullard@lemmy.sdf.org
    4·
    5 months ago

    Windows is best run in a VM in Linux. Who knows what the hell it does when it’s running on bare metal. Do you trust Microsoft not to poke around in your Linux disks when you boot into Windows? I don’t.

    • Emotet@slrpnk.net
      1·
      5 months ago

      Windows, as any operating system, is best run in a context most useful to the user and appropriate for the user’s technical level.

      • Need to run Windows apps/games and aren’t afraid to tinker around if and when something doesn’t work as expected or your software simply isn’t supported? WINE/Proton.
      • Need to run mostly light Windows apps and don’t want to tinker around? VM.
      • Need to run Windows apps/games that don’t rely on Kernel-Level Anti-Cheat, want direct hardware access and aren’t afraid to tinker around, especially if you only have one GPU, and when something doesn’t work as expected? KVM
      • Need to run any Windows app/game without things constantly breaking or the need to tinker around and staying on top of things? Dual-Boot from different disks, utilize LUKS/FDE and be done with it.
    • tibi@lemmy.world
      1·
      5 months ago

      I actually tried it before for my TV PC that I wanted to also use as a miniserver, with gpu pass through and everything. It was painful to get it working properly, was like 30-40% slower. I also had constant problems with USB peripherals not connecting properly, or going in a sleep state and not waking. Many games didn’t work properly.

      Then I decided to just buy a cheap second second hand PC and never looked back.

  • Leaflet@lemmy.worldOPEnglish
    1·
    5 months ago

    The TLDR is that Microsoft released a secure boot update that blocked insecure versions of GRUB. This update was only meant to go out to Windows users since releasing it to dual booted users could break GRUB. However, it was accidentally also released to dual-booted users.

    The fix involves disabling dual boot, running a command to reset secure boot, then re-enabling.

    • Leaflet@lemmy.worldOPEnglish
      0·
      5 months ago

      Windows assuming it’s the only OS on the machine

      That’s not the case. The update was only meant to go out to Windows users. But Microsoft messed up and accidentally released to all users, or at least some who weren’t supposed to receive it. My guess is that Microsoft usually doesn’t update secure boot stuff for dual boot users and instead waits for the distro to push the update.