UEFI Boot Entries for Aeon killed by Windows Update

Hi, I dual boot Aeon with Windows 11 (big mistake, I know) because its the only way to properly use my VR equipment. By Dual Boot I mean select a different Boot Option in my Uefi.

Unfortunately, Windows thougt it would be funny to erase my Aeon boot entries with its update prcedure and somehow the entire EFI loader after checking with UEFI shell.

Now I’m stuck and backupping my Aeon home directory via the installer, just so I can reinstall afterwards. This is very annoying and I was wondering if anyone knows of a way to manually restore those boot options.

Things I tried:
Restoring them via Windows (Didn’t work because the EFI folder doesnt physically exist on the disk anymore)
Updating my Bios
Enabling and disabling probably every setting related to secure boot, fast boot etc.

So, can some kind soul please help me? ^^ The only way I currently have to run Aeon is via the installer medium. I would be very happy to not be forced to reinstall the entire OS.

My Mainboard is a MSI Pro X-670P Wifi if that matters.

You told long story without any facts, only your conclusions. Show what made you come to these conclusions.

Hi, so at first I tried out a tool for Windows which would write boot entries based on a partitions Boot sector. Each time I rebooted afterwards, the new label would just start Windows however. After checking in Windows again it confirmed to be reset. So I thought this might be some fallback machanism. Afterwards I read about using the uefi shell to manually run an Efi File. So I tried that and searched through every disk (e.g. FS1: followed by ls -la) In every tutorial I found it told me to just navigate tonthe efi folder, but for the linux drive there simply was none listed. Just to confirm that, I switched to the Windows disk and it HAD an efi folder. This made me think that there is no Efi folder or maybe it might be corrupted or something. Is there a way to check for sure?

I should also note if I haven’t made it clear that both OSes are on separate physical M.2 drives on my PC

That was probably a mistake. UEFI booting doesn’t work that way.

Your Aeon booting might be using the same EFI folder as Windows.

When starting the tool it already only showed just Windows, just like the boot options in the UEFI. The tools name is Bootice if anyone wants to look it up. Regardless, I think now it’s too late to save anything and I would need to write those boot records myself. Does anyone know which commands I’d need to run in the installer terminal to fix those? The disk tool tells me that “theoretically” the EFI partition would be still intact as well as the rest of the drive, but I don’t know how to mount/validate the EFI files are still on there or how to make it “readable” again to the UEFI.

I just double checked, the 2 EFI Partitions should be on separate drives and on the “Windows” Drive there is only one bootx64.efi file which launches Windows. So I think the EFI file is actually gone or rather not findable by UEFI.

It’s hard to help you when you provide so little information about your system.

As far as I know, Aeon uses systemd-boot for booting. I’m not sure what files it leaves behind.

Start by looking in the Windows EFI partition. Is there a subdirectory other than the Microsoft one? Give as much information as you can about that.

Perhaps download the Tumbleweed rescue CD and try to boot that or write to a USB for booting. Then we will at least know what tools you have to examine your system.

@Jan5676 Hi, there is no dual or multiboot support for Aeon because of the very reason you hitting… just saying :wink:

Maybe look at MicroOS instead?