Arch Linux

Utkarsh

Member

Registered: 2026-01-22

Posts: 1

Stuck on boot loop because of secure boot.

I installed arch linux just fine and then rebooted to start the Os. When I click on linux boot manager, the screen blinks and then back again to the boot menu of systemd.
I don't know my bios password because the laptop belonged to one of my relatives.
So I can't disable secure boot.

Should I try to install grub instead of systemd.

At first I thought arch was tough so I can try cachyos to make myself comfortable and then I will go to the arch.

But then it gave me the error "insufficient memory minimum 2.5Gb needed"

I installed arch instead in anger and it was easy to install, just an hour of yotube tutorial and you are done.

So is there any solution for secure boot or should I just go back to my previous linux distro.

Last edited by Utkarsh (2026-01-22 06:54:44)

Skeleton2323

Member

Registered: 2024-09-14

Posts: 60

Re: Stuck on boot loop because of secure boot.

look up secure boot in the wiki. but if I were you, I'd first find a way to remove the bios password. Maybe remove the cmos battery for a while?

also
sorry but only installations done using the official guide are supported here.
https://bbs.archlinux.org/misc.php?action=rules

5hridhyan

Member

From: Asia

Registered: 2025-12-25

Posts: 304

Re: Stuck on boot loop because of secure boot.

Ultimately it’s your choice whether to switch back or not. Since you mentioned the laptop belonged to a relative, it might also be worth confirming that you actually have permission to change firmware/security settings like Secure Boot.

As for installation: if the wiki felt confusing or overwhelming, you don’t need to rely on long YouTube tutorials. The official "archinstall" script is a supported option and can simplify the process significantly while still following Arch guidelines.

Secure Boot itself is documented on the wiki, and systemd-boot can work with it, but it requires proper key enrollment; GRUB isn’t automatically a fix here.

edit: Removing the CMOS battery generally won’t clear a BIOS/UEFI password on modern laptops; those passwords are typically stored in non-volatile memory. It may reset time/date. This is intentional on most systems as a theft-prevention measure.

Last edited by 5hridhyan (2026-01-22 08:44:15)

---

I expect some mercy from my fellow humans! ^^
Keep your virtue sharpened in a kingdom of carrion, and the throne they offer will be built from your ribs.

Moo-Crumpus

Member

From: Hessen / Germany

Registered: 2003-12-01

Posts: 1,489

Re: Stuck on boot loop because of secure boot.

"I installed Arch Linux using only YouTube tutorials."

Bear in mind that a YouTube video about installing Arch Linux is primarily:
- Outdated: it is older than your current version of Arch Linux due to its rolling releases, which is important.
- Subjective: It depends solely on the hardware of the person who created the video, as well as their decisions.

I am not surprised by the outcome of your installation, but I am surprised by your opinion of it. I am also surprised that you think a Secure Boot problem can be solved by switching from Systemd-Boot to GRUB. You won't get any further without unlocking the UEFI, imho.

Do you want to?
disable Secure Boot in UEFI.
Disable Secure Boot, delete the keys and set Secure Boot to user mode.

In Arch Linux:
Create new ones yourself (including Microsoft's) using a tool like sbctl and write them to EFI.

In UEFI:
Enable Secure Boot again.

The wiki is your safe harbour.
https://wiki.archlinux.org/title/Unifie … with_sbctl

---

Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,593

Re: Stuck on boot loop because of secure boot.

The Arch ISO doesn't support SB, how were you able to boot it?

5hridhyan

Member

From: Asia

Registered: 2025-12-25

Posts: 304

Re: Stuck on boot loop because of secure boot.

yeah i never thought about it, so if it booted, Secure Boot is likely disabled, or the firmware allows unsigned EFI binaries. A locked BIOS doesn’t imply SB is enabled and the OP cannot/unable to confirm it's state. Given the behavior, a misconfigured systemd-boot entry (wrong kernel/initrd path or ESP layout) seems more likely than Secure Boot itself.

@OP https://wiki.archlinux.org/title/System … ot_manager
can help you, first confirm why, is the EFI system partition mounted correctly?, are your loader entries missing or misconfigured? etc.
once you know that, you can follow the Wiki’s steps to reinstall systemd-boot and restore the boot entries.

Last edited by 5hridhyan (2026-01-22 17:48:35)

---

I expect some mercy from my fellow humans! ^^
Keep your virtue sharpened in a kingdom of carrion, and the throne they offer will be built from your ribs.