So I have not booted my windows partition for fear that it would break my boot.

Is there a way to circumvent this before the bug hits my system yet?

Did windows ever fix that?

I am this close to just deleting the entire partition and adding it to my Linux partition as a data and or log drive instead

  • Varyk@sh.itjust.works
    1·
    19 hours ago

    sorry to be late, but I’ve been using a dual boot Linux windows for several years, I leave secure boot off.

    That’s easily toggled in the bios.

    I was worried about this dual boot problem too, but I’ve had no problem switching back and forth between Linux and windows like normal for weeks now, so I don’t think it’s a problem, especially if secure boot is disabled.

  • some_guy@lemmy.sdf.org
    231·
    10 days ago

    I think you should ask in the Linux sub to maximize expert advice. It’s fine that you asked here, but there’s more expert opinions there.

    • Crashumbc@lemmy.worldEnglish
      125·
      10 days ago

      The Linux sub, while knowledgeable, would be a bad place to ask this question.

      All the OP would get is ridicule still having windows partition.

      • palordrolap@fedia.io
        10·
        10 days ago

        What you’ve got to realise is that the Linux folks who don’t have Windows any more have literally no idea how to fix this problem because it’s not a problem they’ve ever had to face. Or if they have, it was a very long time ago and for some who realise their knowledge is stale, they decide to cover it up with bullying and a claim of superiority.

        Source: Am Linux with very stale Windows knowledge. I do not know the answer to OP’s question. This makes me feel inadequate. I will choose the true superior path of not being an ass about it. (Instead being an ass about those who would be, I guess. Hee-haw.)

      • metaStatic@kbin.earth
        21·
        10 days ago

        well it depends on how long it’s been. long enough and just deleting it is the correct choice.

    • PM_Your_Nudes_Please@lemmy.world
      2·
      5 days ago

      Yeah, the issue was with Windows doing funky things with GRUB during an update. GRUB is a popular bootloader, which detects which OSes you have installed, and presents them in a menu. But Windows has been setting Windows Bootloader to run instead of GRUB when it updates. And Windows’ Bootloader doesn’t automatically detect Linux installs. If you use your BIOS to choose your OS (instead of using GRUB) you’re fine.

      Even then, the fix is relatively simple in most cases. It’s just running a command in Windows’ Command Prompt, (the specific command is a little bit different depending on your specific distro) to re-enable GRUB after the update disables it.

    • metaStatic@kbin.earth
      6·
      10 days ago

      I do this with the default boot being linux and never had any drama, but they’re on different drives so can’t really speak on partition safety.

  • undefined@links.hackliberty.org
    9·
    10 days ago

    Are you talking about the old-school issue where it wipes out your boot loader or the more recent issue where Windows hoses Linux for whatever “security” reason?

  • Its_Always_420@lemmy.worldEnglish
    1·
    10 days ago

    I switched to reFind boot manager and had to run a boot repair on the Windows partition with the Win11 USB installer. But it looks like everything is functioning now.

  • NuXCOM_90Percent@lemmy.zip
    27·
    10 days ago

    So… Windows?

    I vaguely recall an extra worry a few min because. But my expert is that windows inevitably clobbers the boot loader eventually. So unless it is a laptop (where you are better off with a VM or wsl anyway) just give each os their own disc and use the BIOS for boot order.