Omarchy: Windows entry disappears from Limine after every update
The problem is real and precisely described. I read bin/omarchy-refresh-limine and it does sudo mv /boot/limine.conf /boot/limine.conf.bak then copies default/limine/limine.conf over it, and issue 7867's title confirms both the dropped Windows entry and the redundant ESP. The Limine syntax is valid (CONFIG.md confirms protocol: efi is the EFI-chainload alias and boot(N):/... selects partition N of the boot drive). But the fix has three defects. The cp /boot/limine.conf /etc/limine-windows-entry.conf.bak line saves the whole config under a name implying it holds only the Windows entry and is never used again. The re-apply script never runs limine-update, so the edited config may not be picked up. boot(1) is only correct when Windows sits on partition 1 of the *same* drive Limine booted from, and on the dual-ESP layout the record itself describes, that is exactly what is not true.
Editing /boot/limine.conf incorrectly (bad indentation, wrong boot() index) makes Limine drop to its own error screen. Keep a backup copy of the working file before editing, and never remove the Omarchy entries while adding Windows.
Symptom
You dual-boot Omarchy with Windows. You add a Windows entry to the Limine menu and it works. Then after the next omarchy update (or any run of omarchy-refresh-limine) the Windows entry is gone again and the only way into Windows is the firmware boot menu. On some installs the Omarchy installer also created a second, redundant 2 GB ESP (omarchy-efi) instead of reusing the Windows ESP, so the firmware never surfaces the Omarchy entry at the top level.
Cause
omarchy-refresh-limine overwrites /boot/limine.conf from a template that contains no OS entries, then runs helpers that only re-add Linux/snapshot entries. Any foreign-OS entry in the file is silently and permanently discarded. Tracked upstream as basecamp/omarchy#7867.
Fix
Find the Windows ESP, its partition index, and its GUID:
sudo blkid | grep -i vfat
lsblk -o NAME,PARTLABEL,PARTUUID,SIZE,FSTYPE,MOUNTPOINT
sudo ls /boot/EFI/Microsoft/Boot/bootmgfw.efi 2>/dev/null # is Windows on THIS ESP?
Add to /boot/limine.conf. If Windows is on the same drive Limine booted from, boot(N) works. N is the 1-based partition index, **not** always 1:
/Windows
protocol: efi
path: boot(1):/EFI/Microsoft/Boot/bootmgfw.efi
If Windows has its own ESP on another disk (the redundant-ESP layout in issue 7867), boot() cannot reach it, so use the partition GUID instead, which is stable across disk reordering:
/Windows
protocol: efi
path: guid(XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX):/EFI/Microsoft/Boot/bootmgfw.efi
(GUID = the ESP's PARTUUID from the lsblk output above.)
Apply it and re-append after every update:
sudo tee /usr/local/bin/readd-windows-limine >/dev/null <<'EOF'
#!/usr/bin/env bash
set -euo pipefail
if ! grep -q '^/Windows' /boot/limine.conf; then
cat >> /boot/limine.conf <<'ENTRY'
/Windows
protocol: efi
path: boot(1):/EFI/Microsoft/Boot/bootmgfw.efi
ENTRY
limine-update
fi
EOF
sudo chmod +x /usr/local/bin/readd-windows-limine
Edit the path: line in that script to whichever form you verified works. Run sudo readd-windows-limine after each omarchy update until #7867 is fixed. Note omarchy-refresh-limine leaves the previous file at /boot/limine.conf.bak, so you can always recover your entry from there.
Verify
Reboot. The Limine menu lists **Windows** and selecting it chainloads the Windows Boot Manager. Re-run omarchy update, then confirm the entry is still (or is again) present in /boot/limine.conf.