No boot entry after BIOS update

General system Kernel, boot, graphics & hardware
21

yes it is on a dual boot, in fact it’s not the bios update that messed up in my case, but a windows update.

so yeah, anyway, windows is working as expected, i just had to restore the windows boot manager after the steps we talked about (nuke /efi, reboot into bios, reboot live iso, bootctl kernels, make linux great again, and only after that take care of windows) and it was back like nothing ever happened.

edit:
and idk, but make sure you have a windows iso, or make one before killing the /efi if you don’t.

I would try to just move back the /Microsoft folder after you’re done dealing with linux, and see if that does it…

if it doesn’t then you’ll have to use the windows iso the take care of windows boot manager from there (which is kind of a pain, for me at least)

22

Now you’re talking about something else? :face_exhaling:

23

what, why ?

no i don’t think so (but always assume i don’t know what i’m talking about when talking to me :sweat_smile:)
I’m saying that after “restoring” linux boot entry, I had to do the same with windows one (cause after deleting /efi content none of them were in the bios anymore, neither linux nor windows)

24

It sounds like you mean you had to restore the Windows bootloader in Windows? :thinking:

25

I always thought that even the name was an oxymoron considering it is Microsoft BS. Yeah I forgot to disable Secure Boot on an update and spent thirty minutes doing a check on my phone screen to see if I could get an answer to what could have happened because I didn’t think about the Update resetting the defaults.

2 Likes
26

I did have to “restore” it indeed. (recreate?)

I did it from the windows terminal booting into windows iso.

I wonder if just restoring efi/EFI/Microsoft wouldn’t just do it

27

I’m just not sure. I use grub mostly. I do have systemd-boot with Windows on one laptop. Haven’t used it that much and it hasn’t caused me any drama.

28

is it with dual-boot as well ?

I only have this one experience with this one machine, so…

1 Like
29

Yes …i edited my post.

1 Like
30

Quick update:
I created a new boot entry as described here. The efibootmgr command listed it afterwards.
But when I restarted the machine it booted into windows right away again. The BIOS did not list that newly created option and when live iso + chrooted into the system again, the entry was not listed via efibootmgr anymore. No idea why it disappeared with the reboot.

I’ll now try the rm -rf /efi/* method (already copied the content to my ~).

31

I tried so many things of the wiki, as well as so many things from inside windows… as I said in the other thread, had I known the pain, I would have start with nuking /efi…

Well, best of luck :crossed_fingers:

32

OK, that worked. Thanks @linuxislife !
Nuking /efi and rerunning the commands again did the trick.

Here are the steps I took to get it running again:
0. Disable secure boot again after firmware update!

  1. Boot into live iso
  2. Mount respective partitions (/ and /efi)
  3. arch-chroot into it
  4. cp -r /efi ~/
  5. rm -rf /efi/*
  6. bootctl install (I restarted beforehand to make sure there’s no boot entry anymore, but I don’t think it’s required)
  7. reinstall-kernels
  8. Reboot and select BootOS in BIOS as first boot option
  9. (It booted into the linux system right away, no menu) Login to eOS
  10. cp ~/efi/loader/loader.conf /efi/loader/ (this brought back the boot menu, but w/o the Windows entry)
  11. cp -r ~/efi/EFI/Microsoft/ /efi/EFI/

After the last step Windows appeared again in my boot menu and booted w/o any issues.
The time in Windows was just off again. So, I had to sync it with a timeserver under windows and then under linux do timedatectl set-local-rtc 1 again to keep it from messing up the Windows time.

Thanks again for everybody’s help and especially to @linuxislife for the resolving tip!

2 Likes
33

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.