• MTK@lemmy.world
    link
    fedilink
    arrow-up
    11
    ·
    1 year ago

    It tends to happen if you are not using the windows bootloader (GRUB for example) but if you use the windows bootloader it should be fine

      • JackbyDev@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        I don’t remember if Windows updates would cause it but installing Windows second definitely would. Likewise, I think upgrading (from say Windows 7 to 10) might. Basically Windows is just like “this MBR? It’s actually mine, thanks.” With no option to not erase it.

        • Eufalconimorph@discuss.tchncs.de
          link
          fedilink
          arrow-up
          3
          ·
          1 year ago

          EFI systems don’t use the MBR. Windows will default to using the whole disk if you don’t use the “advanced” button, but so will most linux distro installers.

      • Ooops@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        In fact old BIOS systems are more resilient. With a separate bootload on another disk, starting from that disk and then chainloading Windows (on another disk) or Linux works very stable as Windows is not trying to change the boot order of BIOS.

        But Windows likes to also meddle with UEFI. Even with separate disks each with their own ESP it likes to change you EFI settings to make windows the default again instead of the boot menu on another disk (everything on the same single ESP is even worse, because then Windows can access and delete everything now Windows and you have to restore the boot loader/menu).

    • themusicman@lemmy.world
      link
      fedilink
      arrow-up
      10
      arrow-down
      1
      ·
      1 year ago

      Oh it just changes the bootloader? That’s not a big deal. Easy to fix from any live usb.

      Also, for any distro hoppers out there… Do yourself a favour and put Ventoy on a USB. You can thank me later