Error loading EFI + "installing Pop!_OS 22.04 LTS failed, possibly due to a hardware error" + Duel boot


New Member
Jul 25, 2023
Reaction score
I'm a complete noob with everything here, please help!

I have duel booted windows 10 and Pop!_OS 22.04 LTS (NVIDIA) a week ago and everything was doing great, until out of nowhere while trying to go from windows to pop_os by restarting, i got this error, although i only got it once (pic1-Error loading EFI)

and ever since then im unable to boot up pop_os, and got a black screen with option "reboot to firmware interface".

booting up windows is fine. I have a live disk containing pop_os which i used to maybe try re-install/format the boot partition, but it doesn't work and i got the installing error (pic 2), the download link for the /tmp/installer.log (

tomorrow i gonna buy an external hard drive to save up my important folders.

windows and pop_os have their own separate boot and root partitions, all four of them have enough space.

i'm using lenovo 5 15
CPU: AMD Ryzen 7 5800H

GPU: NVIDIA GeForce RTX 3050 Ti
hard drive size: 512 gb NVMe SSD
ram: 16 gb


  • pic1.jpg
    617.7 KB · Views: 333
  • pic2.png
    146.4 KB · Views: 297

your first image shows that the efi file isn't found. you could try repairing the bootloader to see if that helps. these are instructions from pop os about how to do that:

your image makes it look like you installed in efi mode so you would be looking at the systemd-boot instructions on that page. if that doesn't seem to want to work, you could also try boot-repair from your live disk:
Welcome to the forums
Ok. So you're new to this, so don't take offence,
Pop is a distribution made by system 76 for their own equipment, and so is built specifically for system 76 machines. If it works out of the box on other Kit that's great, if it doesn't then it's a pain in the rear to get and keep it working.
You said you are dual booting with W10
1] have you disabled windows quick start [fast boot]?
2]have you disabled secure boot?
If not, disable both and do a full re-start.
If you did but have since run a Windows update, check windows has not re-enabled them, if it has disabled and re-start.
Your machine is about 2 years old, so there should not be any driver problems.

Staff online

Members online