Remember the windows bug that would break Linux booting?
Remember the windows bug that would break Linux booting?
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
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.
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.
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.
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.)
well it depends on how long it's been. long enough and just deleting it is the correct choice.
I think (not positive) that if you launch windows from bios it can't break your boot.
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.
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.
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?
I asked this 2 months ago, but honestly I'm not really much smarter: https://sh.itjust.works/post/24120546
Gute Reise!
I don't have an answer, but this might be the issue if anyone has more info
https://www.theverge.com/2024/8/21/24225108/microsoft-security-update-windows-linux-dual-boot-errors
That’s not an issue if you boot via UEFI.
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.
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.