• Harvey656@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      17 days ago

      The supposed update that fixed it (windows update) broke it worse than ever, took me quite awhile to figure it out.

  • palordrolap@fedia.io
    link
    fedilink
    arrow-up
    25
    arrow-down
    1
    ·
    18 days ago

    If you’re lucky, it’s still on the disk and you just need to “repair” the bootloader.

    If not, well, that traumatised Mr Incredible pastiche might be at least a circle of hell too pleasant.

    You have backups, right?

    • Matriks404@lemmy.world
      cake
      link
      fedilink
      arrow-up
      18
      ·
      18 days ago

      There’s no way Windows would just access non-readable partition, and do anything with it, let alone delete it. No operating system does this.

      Replacing the bootloader is of course much more likely, but the general rule is that if you can manage to install Linux, you probably can follow basic instructions to fix GRUB or whatever your bootloader is.

      • palordrolap@fedia.io
        link
        fedilink
        arrow-up
        10
        ·
        18 days ago

        There’s no way Windows would just access non-readable partition

        I knew that was true back in the day, but I haven’t tried dual booting in a long, long time. Also, I wouldn’t put it past Microsoft’s current incarnation to “accidentally” decide that that “empty” partition would be great for virtual memory and the hibernation image.

        • Klajan@lemmy.zip
          link
          fedilink
          arrow-up
          6
          ·
          18 days ago

          Oh Windows knows this is the EFI partition, there is a flag for that. Windows just doesn’t care when it decides to nuke your bootloader with its own…

          And yes, it’s still happening…

      • sykaster@feddit.nl
        link
        fedilink
        English
        arrow-up
        3
        ·
        18 days ago

        Installing Linux is so simple nowadays that fixing the bootloader is a level higher now

      • Jankatarch@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        18 days ago

        To be fair, windows does save its license key on ROM. It writes to the read-only memory. So it could.

  • xia@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    20
    ·
    18 days ago

    The trick is to have a second EFI partition. One for windows to destroy, and one for linux to enjoy.

    • bluesheep@lemm.ee
      link
      fedilink
      arrow-up
      7
      ·
      18 days ago

      I that why I never relate to this issue? I’ve had a dual boot setup for years by now and have always been able to choose either windows or Linux at startup, but they are on separate drives

      • MonkderVierte@lemmy.zip
        link
        fedilink
        arrow-up
        1
        ·
        17 days ago

        Gaming. Want a quick round in a pause? Mount error: go boot Windows to fix it. But i have multiple tools and sessions and stuff open…

        And Windows still can’t handle anything reliable.

    • tehn00bi@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      17 days ago

      With super cheap SSD’s and motherboards with multiple m.2 slots, there’s rarely an excuse not to have different drives anymore. Laptops might be an exception.

    • glorkon@lemmy.world
      link
      fedilink
      arrow-up
      12
      ·
      18 days ago

      I constantly tell people the remedy of the dangers of dual booting, using a separate drive for Linux. They sometimes listen and then have a dual boot system that doesn’t break.

  • Ephera@lemmy.ml
    link
    fedilink
    English
    arrow-up
    5
    ·
    18 days ago

    Can that actually happen like this? If Windows killed the bootloader wouldn’t that mean that you couldn’t boot into Kubuntu either? Or can it somehow kill the bootloader when the PC is turned off?

    • Don_alForno@feddit.org
      link
      fedilink
      arrow-up
      7
      ·
      edit-2
      18 days ago

      What definitely did happen to me is I booted into windows, shut down, on the next startup there was no more grub menu, just instant boot into windows. (Separate physical drives).

  • Sar@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    17 days ago

    Grub had/has this issue every time windows does a cumulative monthly update. Systemd doesn’t have this issue.

  • 0xf@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    17 days ago

    While microsoft has admitted to bugs causing exactly this scenario. I personally have a stabe 6 months with dual-boot. And only updating cachos once a month or every two weeks has been fine. The server and rog ally exclusively runs linux.