• dinckel
    link
    6210 months ago

    Whenever i need to use windows, i leave it on a separate drive, and then just point a rEFInd entry to it. It really frustrates me, that Windows just expects full advocacy over your hardware, and performs changes like this without any warning

    • ares35
      link
      fedilink
      1410 months ago

      i’ve had both windows and linux mess-up dual boot setups… so i started keeping them separate. either different systems, or run in a vm.

      • RandomLegend [He/Him]
        link
        fedilink
        English
        3010 months ago

        My issue is that when linux fucks up my bootloader it’s usually by mistake / bug. If windows does it it’s pretty much deliberate

      • lazynooblet
        link
        fedilink
        English
        610 months ago

        VMWare workstation is well worth the £££. I work in a Windows VM that is fully compliant with all the business requirements and when I run it full screen I don’t feel like it’s a VM.

    • @[email protected]
      link
      fedilink
      210 months ago

      I dualboot with separate efi partitions. Does it happen that windows fucks up anothr efi partition?

  • алсааас [she/they]
    link
    fedilink
    3510 months ago

    Arch moment

    (no I will never forget that one time they borked the grub package and there was no notification of it in the newsfeed)

    • @shadowintheday2
      link
      English
      1010 months ago

      I switched to systemd boot when that happened, and it’s been so smooth ever since

        • @shadowintheday2
          link
          English
          710 months ago

          It’s not exempt from happening; however, it rarely ever updates and has less complexity/functionality than grub, which makes it less prone to error happening (be it from the developers, or from the user like me trying to theme it :))

  • @[email protected]
    link
    fedilink
    2410 months ago

    Seems familiar. Did you by any chance also not update the copy of grub in your EFI system partition since you installed it? Then you need to do that and afterwards everything works fine again.

    While you are at it add a netboot.xyz EFI entry to fix that kind of stuff without a USB stick or your own network boot server.

  • Avid Amoeba
    link
    fedilink
    1910 months ago
    grub> set root=(...)
    grub> linux /vmlinuz root=...
    grub> initrd /initrd.img
    grub> boot
    
    • @[email protected]
      link
      fedilink
      5210 months ago

      Windows has a habit of deleting grub when it updates. Idk if it is just bad Microsoft programming or intentional.

        • ares35
          link
          fedilink
          1210 months ago

          windows ain’t done until nothing else runs.

              • rautapekoni
                link
                fedilink
                710 months ago

                What irritates me the most is they don’t even bother to ask what to do with the bootloader when installing Windows, or at least the option is hidden behind some guru magic not supported by the installer GUI. Leave an old windows boot drive plugged in while doing a fresh install on another drive, and the installer happily uses the bootloader on the old drive without ever even mentioning it. Since it is so easy to make this mistake you’d think Microsoft offered a tool to move the bootloader to a different drive, but nope.

  • THCDenton
    link
    1310 months ago

    This post made by the windows gang

  • ferret
    link
    fedilink
    English
    110 months ago

    Honestly, when I learned that rEFInd supports loading dxe modules natively I swapped and never looked back (NVMe boot drives on ancient computers, my beloved)