That’s not a thing it can do in grub. It could do it with UEFI entries, but these days windows is not the biggest culprit of that. I had it happen on a BIOS update, where it simply nuked all stored entries, and the windows one is always checked as part of the standard.
Yeah, I was gonna say I dual boot and I can’t recall the last time that Windows nuked my UEFI bootloader.
But back when Windows still did BIOS boot, it was like every major release without fail.
edit: Rewreading your post it sounds like you meant updating the BIOS as a whole and not BIOS boot, so that’s my bad. Yeah, I definitely haven’t seen your circumstance, I had that happen consistently before Microsoft embraced the UEFI style booting
So did I up until windows 10, which makes sense because my laptop that had run windows 8.1 had been upgraded from Windows 7 and had the issue every time it seems to have a version release. My windows 10 system was a factory install since I switched to a PC instead of a laptop at that time, and as such ran UEFI out of the box, I haven’t had any issue with windows nuking a boot partition since.
I’m assuming it’s because bios boot still uses an MBR which means the actual boot record is at the beginning of the disk, which windows also tries to use for recovery and its boot. With GPT setups like how UEFI requires, there’s a dedicated partition that is used instead for storing EFI files, so it allows for a much clearer co-existence.
Basically if you are running a UEFI system, there’s no excuse for Windows to actually nuke grub anymore, because the entire reason it was nuking it in the first place was it was overwriting the MBR at the beginning of the disk so the system no longer knew where grub was. With UEFI the system boot would be the UEFI loader -> windows loader or grub (or like how my system is brokenly setup UEFI -> grub -> windows because I like the traditional style of selecting windows from grub)
That’s not a thing it can do in grub. It could do it with UEFI entries, but these days windows is not the biggest culprit of that. I had it happen on a BIOS update, where it simply nuked all stored entries, and the windows one is always checked as part of the standard.
Yeah, I was gonna say I dual boot and I can’t recall the last time that Windows nuked my UEFI bootloader.
But back when Windows still did BIOS boot, it was like every major release without fail.
edit: Rewreading your post it sounds like you meant updating the BIOS as a whole and not BIOS boot, so that’s my bad. Yeah, I definitely haven’t seen your circumstance, I had that happen consistently before Microsoft embraced the UEFI style booting
I definitely had windows make some change at least twice that skipped grub on subsequent boots altogether.
So did I up until windows 10, which makes sense because my laptop that had run windows 8.1 had been upgraded from Windows 7 and had the issue every time it seems to have a version release. My windows 10 system was a factory install since I switched to a PC instead of a laptop at that time, and as such ran UEFI out of the box, I haven’t had any issue with windows nuking a boot partition since.
I’m assuming it’s because bios boot still uses an MBR which means the actual boot record is at the beginning of the disk, which windows also tries to use for recovery and its boot. With GPT setups like how UEFI requires, there’s a dedicated partition that is used instead for storing EFI files, so it allows for a much clearer co-existence.
Basically if you are running a UEFI system, there’s no excuse for Windows to actually nuke grub anymore, because the entire reason it was nuking it in the first place was it was overwriting the MBR at the beginning of the disk so the system no longer knew where grub was. With UEFI the system boot would be the UEFI loader -> windows loader or grub (or like how my system is brokenly setup UEFI -> grub -> windows because I like the traditional style of selecting windows from grub)