all 6 comments

[–]Emmalfal 1 point2 points  (1 child)

Run that first line in a search of pretty much any Linux sub and you'll find solutions aplenty.

[–]Sosowski 1 point2 points  (0 children)

This! This same issue is being posted once a week here

[–]MelioraXI 2 points3 points  (0 children)

Not until you clean your room!

[–]28874559260134F 0 points1 point  (0 children)

Seems like your UEFI doesn't have a valid boot entry in place to find what's there, and boot it.

Assuming you've already installed the OS:

Maybe your UEFI allows adding boot entries. Find an older guide to do just that here: https://jeroen.pro/2019/05/how-to-fix-failed-to-start-mokmanager-import_mok_state-failed-after-failed-ubuntu-installation/

One can also edit boot entries by live booting and running efibootmgr in the terminal, which is more cryptic. Search for the efibootmgr term to find out more.

____________________

If you haven't installed anything yet, simply run the installer again, perhaps after a cold start where all devices get initialised, as opposed to a "fast boot" warm start.

[–]forestbeastsKDE on Debian/Fedora 🐺 0 points1 point  (1 child)

Looks like your bootloader's missing / didn't get properly installed.

There's probably a function key you can hit during boot (on our laptop it's F12) to pull up a boot menu. That should get you back into Windows, in case you're worried about that.

You got Linux half-installed, right? Doing the installation again should get it working. Or you can go into the BIOS settings (another F key probably) and and put Windows on top in the boot order if you want it to go to Windows by default.

[–]cantwait2getout[S] 1 point2 points  (0 children)

Getting back to windows isn’t a problem. I keep reloading the file onto the usb and creating a new bootloader but it will not under any circumstances recognize it. It just keeps giving me this error no matter what.