New snapshots missing from the Limine menu for hours after booting from Windows
The mechanism holds: #13367 and GitLab work item 17 describe it, and the registry command matches the Arch wiki System_time page word for word. What changed since the first pass: Zesko fixed it upstream in commit 6865e06d ('Fix #17'), released in limine-snapper-sync 1.32.1 on 2026-10-03, whose release notes read 'Do not ignore new snapshots with older UTC timestamps when the last UTC timestamp in the manifest is in the future'. A #13367 comment reports the same. Omarchy's stable repository (pkgs.omarchy.org/stable omarchy.db, fetched 2026-10-05) still ships limine-snapper-sync 1.31.0-1.1, which is also what is installed here, so the problem is current on Omarchy 4.0.4 but will end with a package update. The cause and fix now say so. Verified that omarchy update snapshots through omarchy-snapshot create, which uses snapper create -c number. Not exercised: no clock was changed and no snapshot was taken.
Symptom
On a Windows dual-boot machine, snapper -c root list shows the snapshot omarchy update just took, the journal says Saved: snapshots.json and Updated: limine.conf, but the Snapshots submenu in the Omarchy Bootloader has no entry for it or any snapshot after it. The entries appear on their own a few hours later, roughly your UTC offset.
Cause
Windows keeps the hardware clock in local time and Linux reads it as UTC. In a time zone east of UTC (a positive offset, such as most of Europe, Africa and Asia), Omarchy therefore starts after a Windows session with the clock ahead by the UTC offset until NTP corrects it. A snapshot taken in that window, such as the pre-update snapshot, carries a future timestamp. limine-snapper-sync up to 1.31.0 records the newest snapshot time as lastUTCTime and treats a later snapshot as new only if its time is later than that stamp, so every real-time snapshot afterwards is ignored until real time passes the bad stamp. The tool logs nothing about it. West of UTC the clock runs behind instead, the stray snapshot lies in the past and nothing is hidden. Reported upstream as limine-snapper-sync work item 17 and fixed in limine-snapper-sync 1.32.1 (2026-10-03), which also accepts a higher snapshot ID as new when the stored stamp is in the future. As of 2026-10-05 Omarchy's stable repository still ships 1.31.0-1.1.
Fix
Check which limine-snapper-sync you have:
pacman -Q limine-snapper-sync
Version 1.32.1 or later no longer hides the snapshots. It reaches Omarchy through omarchy update once Omarchy's repository carries it (on 2026-10-05 it still shipped 1.31.0-1.1). A wrong clock still stamps snapshots with the wrong time, so settle the clock convention either way.
Preferred: make Windows keep UTC. In an elevated Windows command prompt:
reg add "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation" /v RealTimeIsUniversal /d 1 /t REG_DWORD /f
Or make Linux read the RTC as local time instead:
timedatectl set-local-rtc 1
Until then, after coming back from Windows, wait for NTP before updating:
timedatectl show -p NTPSynchronized --value # wait for: yes
omarchy update
Snapshots already hidden reappear once real time passes the future stamp, or once 1.32.1 or later runs. They are intact in snapper -c root list in the meantime.
Verify
timedatectl shows the correct local time immediately after booting from Windows, and a fresh omarchy-snapshot create appears in the Limine Snapshots submenu on the next boot.
Sources
- https://github.com/omacom/omarchy/issues/13367
- https://gitlab.com/Zesko/limine-snapper-sync/-/work_items/17
- https://wiki.archlinux.org/title/System_time
- https://wiki.archlinux.org/title/Dual_boot_with_Windows
- https://gitlab.com/Zesko/limine-snapper-sync/-/commit/6865e06ddfbba3ab1165ed7743f4239c669ced66
- https://gitlab.com/Zesko/limine-snapper-sync/-/tags/1.32.1