• dust_accelerator
    link
    fedilink
    arrow-up
    11
    ·
    edit-2
    8 months ago

    Beware of the W̷̞̬̍̌͘͜ĭ̴̬̹̟͕̒̆̈́n̸̢̧̙̈́̅̂̆̕͜ͅd̵̟̟̪͎̀̀ő̴̼̺̺́̐̂͘w̵̨͊̀s̵̡͎̭̊ ̸͔̬͔̜̊́̈́̌̈́ͅŬ̴͉͚̳̌̉͘͝p̸̼̅̆͐̃̑d̸̜͂ǎ̵̛̯̏͝ť̷̰é̸͇͝ as it can screw up/overwrite your other bootloader completely.

    Kinda sucks, when you’ve got a meeting/work and you find out that forced update made your system unbootable/partially unbootable and you now get to live boot in and go fixing the EFI partition manually, in the CLI.

    That happened to me once and that’s when I decided feature parity was less important than a reliable system that “just works” for getting things done on a schedule. (I removed windows completely, in case that wasn’t clear)

    Anyhow, make sure you install windows to a separate drive that can’t see any others during the windows install, then will keep the bootloader separate.

    • Senseless@feddit.de
      link
      fedilink
      arrow-up
      3
      ·
      8 months ago

      I ran into similar issues before. My plan was to install Linux on a separate M.2 so Windows won’t interfere and manually boot the OS I want to manually.