2 ms·
I've seen it do it as well and I'm pretty sure now that it's part of the "automatic repair" process that Windows does when it detects 3 (?) failed boots. What h
by franga2000 6y ago
I've seen it do it as well and I'm pretty sure now that it's part of the "automatic repair" process that Windows does when it detects 3 (?) failed boots. What happened pretty often to me is that I'd miss the boot screen and Windows would start booting (it's the default bc it's a shared PC) and in order to not waste time, I'd force a reboot. After a few times, next time Win would actually boot, it would go into rescue mode and start poking around the EFI partition and efivars doing god knows what that ended up in my GRUB not even showing up in the F11 boot menu.
- vladvasiliu 6y agoI've had this happen too, but I think it just changed something in the efivars, grub itself was still there and still operational, even though it didn't show up in the available boot options. The workaround for me was the "boot from file" boot option, where I would be able to walk the directories in the efi partition and start grub. Once this was done, it was back in the boot option list.
- franga2000 6y agoYeah, I've only had it remove the actual files once, when I had to use the recovery USB thing to fix a broken update. Unfortunately, my motherboard is from the very early days of UEFI and doesn't allow me to select files or even manage keys so I have to keep a microSD card with a bunch of bootloaders handy in case this happens (I still haven't gotten around to learning UEFI shell in order to manually boot).