Windows entry added by limine-scan panics with 'image not found'
#7906 is an open report of exactly this problem, and the reporter verified that correcting the casing fixed it. The manual's limine-scan step is on the quattro branch at manual/50-dual-boot-install.md. The record's statement that Limine's FAT lookup is case-sensitive is too broad. /usr/share/doc/limine/CONFIG.md from limine 12.8.0-1 on this machine says: 'On FAT volumes a name that fits the 8.3 short form is matched case insensitively ... a name too long for that form is matched case sensitively.' So BOOT and BOOTMGFW.EFI resolve in either case. The component that fails is MICROSOFT, nine characters, which does not fit 8.3 and so must match 'Microsoft' exactly. That is why the casing fix works, and it tells a reader which part matters. The cause has been rewritten. limine-entry-tool's changelog has 1.31.0 'Ensure correct case-sensitive path resolution', which is older than the 2026-08-23 issue and evidently did not cover --scan. omarchy-refresh-limine on this machine does overwrite /boot/limine.conf from the default, which supports the closing note. Not exercised: no Windows ESP here. Second audit confirmed the corrected text: Second audit of the corrected text. #7906 is open and its reporter verified that fixing the casing booted Windows. The quattro manual/50-dual-boot-install.md still tells users to run limine-scan. /usr/share/doc/limine/CONFIG.md from limine 12.8.0-1 says paths are case sensitive except that on FAT a name fitting the 8.3 short form matches case insensitively, so the rewritten cause about MICROSOFT being nine characters holds. /usr/share/omarchy/bin/omarchy-refresh-limine moves /boot/limine.conf aside and copies the default template, which supports the closing note. A hand edit of /boot/limine.conf is not undone by config checksum enrollment on a default install, because ENABLE_ENROLL_LIMINE_CONFIG is commented out (default no) in /etc/limine-entry-tool.conf and set nowhere in the drop-ins or /etc/default/limine here. Not exercised: no Windows ESP here.
Symptom
Following the Omarchy dual-boot manual, you run limine-scan and add Windows. Selecting **Windows Boot Manager** in Limine panics instead of starting Windows. The reported message:
image not found — is the path correct?
/boot/limine.conf shows the path in capitals:
/Windows Boot Manager
protocol: efi
path: guid(<esp-partuuid>):/EFI/MICROSOFT/BOOT/BOOTMGFW.EFI
Cause
limine-scan runs limine-entry-tool --scan, which takes EFI paths from efibootmgr. Firmware often reports the Windows loader path in upper case (\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI), and the scanner only turns backslashes into slashes. Limine 12's path rules (/usr/share/doc/limine/CONFIG.md) match a FAT name case-insensitively only if it fits the 8.3 short form. BOOT and BOOTMGFW.EFI fit, so their case does not matter. MICROSOFT is nine characters and does not fit, so it must match the on-disk Microsoft exactly, and the lookup fails. The reporter on #7906 verified that correcting the casing made Windows boot immediately.
Fix
Find the real on-disk casing and correct the path: line.
# Windows on the same ESP as Omarchy
sudo find /boot/EFI -iname 'bootmgfw.efi'
# Windows on its own ESP on another disk: mount it read-only and look
lsblk -o NAME,PARTUUID,FSTYPE,SIZE
sudo mount -o ro /dev/nvme1n1p1 /mnt # the other disk's vfat ESP
find /mnt/EFI -iname 'bootmgfw.efi'
sudo umount /mnt
Edit the entry in /boot/limine.conf so the path matches exactly, keeping the guid(...) prefix the scanner wrote:
/Windows Boot Manager
protocol: efi
path: guid(<esp-partuuid>):/EFI/Microsoft/Boot/bootmgfw.efi
A Windows entry hand-added to /boot/limine.conf is discarded whenever omarchy-refresh-limine runs. See omarchy-limine-windows-entry-wiped for keeping it across updates.
Verify
sudo grep -n -A3 '^/Windows' /boot/limine.conf shows the corrected path, and selecting the entry in Limine starts the Windows boot manager.