Microsoft took a big bite out of GRUB, which is the utility that your motherboard uses to dual boot OSes. A Windows update basically borked it and set Windows as the mandatory default OS. It basically makes it so your motherboard can’t properly identify your Linux install(s).
Luckily, you can fix it directly in Windows Command Prompt. But still, it’s a dirty trick that Microsoft has been using recently. Windows has historically been a bad neighbor for other OSes, (for instance, the Secure Boot Module is basically an attempt to make booting other OSes difficult,) but this was the first time in recent history that they have outright prevented another existing OS from booting.
might be better to separate drives, windows has been known to fuck up Linux partitions recently.
This sounds like something I should be wary of, but it’s the first I’m hearing of it. Any other info?
https://arstechnica.com/security/2024/08/a-patch-microsoft-spent-2-years-preparing-is-making-a-mess-for-some-linux-users/
I haven’t booted into Windows since
It typically happens during updates. People have reported their grub screwing up. If you’re able I would honestly suggest separate drives
Microsoft took a big bite out of GRUB, which is the utility that your motherboard uses to dual boot OSes. A Windows update basically borked it and set Windows as the mandatory default OS. It basically makes it so your motherboard can’t properly identify your Linux install(s).
Luckily, you can fix it directly in Windows Command Prompt. But still, it’s a dirty trick that Microsoft has been using recently. Windows has historically been a bad neighbor for other OSes, (for instance, the Secure Boot Module is basically an attempt to make booting other OSes difficult,) but this was the first time in recent history that they have outright prevented another existing OS from booting.
only anecdotes unfortunately.
True once the day comes you can possibly do a raid config