Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
4.0.2 free-space install registers no UEFI boot entry — boots straight to Windows
Reported by exergonic · filed Sep 7, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
System details
Omarchy 4.0.2 ISO (Balena Etcher) · Windows 11 24H2 (build 26100) · UEFI ·
Secure Boot OFF (Confirm-SecureBootUEFI = False) · BitLocker fully
decrypted (manage-bde: Fully Decrypted, Protection Off) · 50 GB
unallocated free space · free-space install, all defaults (LUKS + btrfs,
kernel 7.1.9-arch1-2, per the installed limine.conf cmdline:
`cryptdevice=UUID=b1bd598f-e43f-4e51-8499-b18348b18cc2:omarchy_root ...
rootfstype=btrfs`).
What's wrong?
The installer completes with no visible errors, but registers no
Omarchy/Limine entry in NVRAM. bcdedit /enum firmware from Windows shows
only Windows Boot Manager plus plugged USB sticks. The machine boots
straight to Windows; the Limine menu never appears.
Root-cause evidence
The OMARCHY_EFI partition is fully populated — only theefibootmgr --create registration is missing:
EFI/limine/limine_x64.efi(368,640 B) +limine_x64.bakEFI/Linux/omarchy_linux.efi(144,192,512 B, the UKI)limine.conf(fresh, Omarchy entry, machine-id present) +limine.conf.oldintel-ucode.img
So on the free-space path, file deployment succeeds while the NVRAM step is
silently skipped/failing. Workaround (manual efibootmgr --create for both
entries from the live USB) restores booting, which points at registration
rather than installation.
Secondary observation: the generated limine.conf contains Omarchy-only, no
Windows entry — the probing gap from #7270, seen in the wild.
Related
- #1719 (wrong default entry), #7270 (no OS probing), #5389 (EFI detection)
- r/omarchy "No Boot option on fresh install"; Luke Hsiao's "Fixing missing
Omarchy boot entries" notes fresh installs sometimes fail to set up entries
View raw text
## System details Omarchy 4.0.2 ISO (Balena Etcher) · Windows 11 24H2 (build 26100) · UEFI · Secure Boot OFF (`Confirm-SecureBootUEFI` = False) · BitLocker fully decrypted (`manage-bde`: Fully Decrypted, Protection Off) · 50 GB unallocated free space · free-space install, all defaults (LUKS + btrfs, kernel 7.1.9-arch1-2, per the installed `limine.conf` cmdline: `cryptdevice=UUID=b1bd598f-e43f-4e51-8499-b18348b18cc2:omarchy_root ... rootfstype=btrfs`). ## What's wrong? The installer completes with no visible errors, but registers **no** Omarchy/Limine entry in NVRAM. `bcdedit /enum firmware` from Windows shows only Windows Boot Manager plus plugged USB sticks. The machine boots straight to Windows; the Limine menu never appears. ## Root-cause evidence The `OMARCHY_EFI` partition is fully populated — only the `efibootmgr --create` registration is missing: - `EFI/limine/limine_x64.efi` (368,640 B) + `limine_x64.bak` - `EFI/Linux/omarchy_linux.efi` (144,192,512 B, the UKI) - `limine.conf` (fresh, Omarchy entry, machine-id present) + `limine.conf.old` - `intel-ucode.img` So on the free-space path, file deployment succeeds while the NVRAM step is silently skipped/failing. Workaround (manual `efibootmgr --create` for both entries from the live USB) restores booting, which points at registration rather than installation. Secondary observation: the generated `limine.conf` contains Omarchy-only, no Windows entry — the probing gap from #7270, seen in the wild. ## Related - #1719 (wrong default entry), #7270 (no OS probing), #5389 (EFI detection) - r/omarchy "No Boot option on fresh install"; Luke Hsiao's "Fixing missing Omarchy boot entries" notes fresh installs sometimes fail to set up entries
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 11:03 UTC