No, it is almost impossible for an update to the kernel, Linux to render windows unbootable, as I don't see how a file being added to either a separate grub partition or directly into the UEFI partition would manage to trip up even the windows bootloader.
For legacy boot, there's even less of a chance, as the boot partition for systemd/Linux and windows are always separate.
Updating GNU GRUB without running grub-mkconfig+os-prober may result in windows not being listed as a boot option, but unless you've cut down the grub modules to only render systemd/Linux bootable, manually chainloading the windows bootloader from the grub shell will still be possible.
Power management, mobile and firmware developer on Linux. Security developer at Aurora. Ex-biologist. mjg59 on Twitter. Content here should not be interpreted as the opinion of my employer. Also on Mastodon.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Re: Why is it up to Microsoft to take care of MY computer's security?
Date: 2024-08-24 01:04 pm (UTC)For legacy boot, there's even less of a chance, as the boot partition for systemd/Linux and windows are always separate.
Updating GNU GRUB without running grub-mkconfig+os-prober may result in windows not being listed as a boot option, but unless you've cut down the grub modules to only render systemd/Linux bootable, manually chainloading the windows bootloader from the grub shell will still be possible.