can't acces GRUB after reinstalling Win10 in DualBoot System

Hi,
I was forced to reinstall my Win10 installation in a Dual-Boot configuration. (Sadly i can't get rid of Windows......but that a dang long story.

so therefore the installation was in Order: encrypted Manjaro was already installed, but with an unencrypted own /boot/efi and an unencrypten /boot
I know my Laptop has the bug to always boot from the \EFI\Microsoft\Boot\bootmgfw.efi if it's available. So I renamed it, as i did last time (but there I installed Manjaro AFTER Win10) but now it doesn't get me to GRUB/Manjaro instead I get a weird error of the UEFI-(BIOS) Bootloader System from my Laptop itself stating it didn't find meantioned above bootmgfw.efi

Adding the grubx64.efi to the "allowed" secure Boot's doesn't chance/or even work.

Did I f*** up my GRUB install with plain re-installing (only formating the Microsoft Recovery, Microsoft EFI, and Microsoft Install Partition) Win10 into an Manjaro DualBoot?
How can I check upon that, an what's a save way to reinstall the GRUB if i messed it up?

Please note down if you need specific terminal output from the Live-Environment, lot thanks in advance

Take a look here.. But note you have a separate /boot (a separate /boot/efi is not relevant).
Main reference is here.

Is your laptop Lenovo ? HP or Asus or msi can be fixed by going to the bios-setup if defaults to booting only windows.

If needed, provide output as stated in second link (reference).

Hmm, thanks @gohlip

It was kind of weird my solution. Everything following up I did from the Live-Environment.
As already known I renamed the bootmgfw.efi from the Windows' EFI Partition. But somehow that wasn't enough for my Acer Aspire E5-553G to "realize" there are other available .efi 's to boot.

So I ran sudo efibootmgr -v and there was some strange-ish weird new entry. ==> Boot0001 which more or less obviously pointed to the bootmgfw.efi of Microsoft after I disabled that entry via efibootmgr -A and resorting the BootOrder to 0003,0013,2001,2002,2003 ===> NOW everything works and I can boot flawless into Manjaro as well as Windows.

[manjaro@manjaro EFI]$ sudo efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0002,2001,2002,2003
Boot0000* USB HDD: Intenso Alu Line	PciRoot(0x0)/Pci(0x10,0x0)/USB(5,0)/HD(1,MBR,0x0,0x3d26e8,0x2000)RC
Boot0001* Unknown Device: 	MemoryMapped(11,0xb5e68000,0xb66fbfff)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)RCkK..
Boot0002* Windows Boot Manager	HD(2,GPT,58143a7c-89ad-4049-ad65-388510aa8db1,0x109000,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot0003* Manjaro1	HD(5,GPT,779fb445-5ea8-41eb-9780-8e1bb8e0d345,0x9088800,0x100000)/File(\EFI\Manjaro\grubx64.efi)
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC

So after that working I did some more research and decided to completelly declutter my efibootmgr and removed the FilePointer Boot0001 & Windowds Own Boot Manager Boot0002 entirely.

Now everything work nice (and even Windows work "nice" so Thanks

You should take a look at this now that we know it is an Acer Aspire E5. It might work better than removing windows boot manager. Perhaps removing windows boot efi entry and having manjaro efi as the only entry has the same effect of moving manjaro entry to the top.

1 Like

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

Forum kindly sponsored by