: (
: (
: (
Arch moment
(no I will never forget that one time they borked the grub package and there was no notification of it in the newsfeed)
Seems familiar. Did you by any chance also not update the copy of grub in your EFI system partition since you installed it? Then you need to do that and afterwards everything works fine again.
While you are at it add a netboot.xyz EFI entry to fix that kind of stuff without a USB stick or your own network boot server.
I love my bootloader https://github.com/Lxtharia/minegrub-theme
grub> set root=(...) grub> linux /vmlinuz root=... grub> initrd /initrd.img grub> boot
Now draw the rest of the owl.
This post made by the windows gang
What I'm missing? Just do update-grub.
Time to break out the system rescue USB
Btw, rEFInd detects bootloaders by itself.
Honestly, when I learned that rEFInd supports loading dxe modules natively I swapped and never looked back (NVMe boot drives on ancient computers, my beloved)
Whenever i need to use windows, i leave it on a separate drive, and then just point a rEFInd entry to it. It really frustrates me, that Windows just expects full advocacy over your hardware, and performs changes like this without any warning
i've had both windows and linux mess-up dual boot setups.. so i started keeping them separate. either different systems, or run in a vm.
My issue is that when linux fucks up my bootloader it's usually by mistake / bug. If windows does it it's pretty much deliberate
VMWare workstation is well worth the £££. I work in a Windows VM that is fully compliant with all the business requirements and when I run it full screen I don't feel like it's a VM.
I dualboot with separate efi partitions. Does it happen that windows fucks up anothr efi partition?