• KubeRoot@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    1 day ago

    And then fuck it up by pointing Linux at your windows EFI partition, end up with neither system bootable and make things worse as you panic and try to rush a fix without understanding what you’re doing.

    If you’re new to how it all works and having a working machine is important, best to keep it simple and as separated as you can.

    I’m also not convinced that “Windows doesn’t know about the other partitions”, that sounds like the kind of thing that’s true until it isn’t and it overwrites your Linux bootloader.

    • BCsven@lemmy.ca
      link
      fedilink
      arrow-up
      1
      ·
      1 day ago

      I have run a dualboot for 8 years this way.

      Chainloading hands the boot over to Windows (from grub) but windows just thinks its a fresh boot. When windows does EFI changes its only to its own designated partition.

      You can even run windows update and when it prompts for reboot to install, you can launch Linux and do whatever, then boot back to windows and the install will continue like you didn’t interrupt it.

      The reason two drives works is same as what I mentioned, you have two EFI partitions that are separate.

      The only way you will wreck it is if you go into windows device manager and delete the unknown partitions.