How to Update Omarchy and Recover from a Bad Update
Use Omarchy's coordinated update path, understand stable and edge channels, and know exactly what a bootable snapshot can and cannot restore.
An Omarchy update is more than a package download. The documented update flow installs packages, applies Omarchy migrations and configuration changes, and makes a system snapshot before the upgrade. That is why the command you use matters when you later need to recover from a bad update.
This guide follows Omarchy’s updates and system snapshots manuals, checked on September 29, 2026. Recovery steps depend on the machine’s bootloader and filesystem state; these instructions describe the documented path rather than a tested recovery on a particular computer.
Update through Omarchy
Open the Omarchy menu with Super + Space and choose Update → Omarchy. The terminal equivalent is omarchy update. An update badge can also appear near the clock when a new release is available. Omarchy’s update manual says this flow handles the release and system packages together, including migrations and a pre-update snapshot.
Someone familiar with Arch may reach for pacman -Syu or yay -Syu. Omarchy’s update manual says those direct full-system upgrades miss its snapshot and migration work; Omarchy stops them by default and points back to its own update command. Installing a single package is a different task from upgrading the operating system.
Stay on the channel that matches your recovery tolerance
New installations begin on the stable channel. The manual describes RC, edge, and dev channels for people willing to test changes earlier, with edge following newer development builds and packages. Update → Channel changes the selection. For a beginner using the machine for everyday work, stable is the documented starting point; switching channels to obtain a feature also changes the kind of breakage you may need to handle.
Firmware updates have their own Update → Firmware entry. The manual says that flow may install fwupd the first time and that some firmware changes need a reboot. Treat a firmware prompt separately from a routine package update and read the device-specific instructions it presents.
If the update breaks the system
The snapshot manual says Omarchy creates a snapshot on every update. Restart and choose a snapshot from before the update in the Limine boot menu. The selected entry lets you boot the older root filesystem; once inside, the documented notification can start restoration, or the omarchy-snapshot restore command can do it.
If the machine boots directly to the decryption screen because Direct Boot is enabled, choose Limine from the firmware boot menu first. Snapshot boot and restoration are available only on installations using Limine; the manual says they are not available on GRUB or systemd-boot. When the boot menu is inaccessible or the system cannot reach a bootable snapshot, use the official troubleshooting path for diagnostics and further recovery rather than guessing at destructive commands.
Know what the snapshot does not contain
A system snapshot restores the root filesystem, not /home. Personal documents and the user configuration under ~/.config remain as they were after the update. That is good when rolling back packages but insufficient for recovering a deleted file or a broken personal configuration. It can also leave a new-format user config paired with older software, which the snapshot manual says you may need to resolve manually.
Keep separate backups for personal files and dotfiles. Before the next update, you should know both where your file backup lives and how to reach Limine. A snapshot is a recovery tool for a class of system failures, not a replacement for a file backup.
References
- Omarchy Updates documents the update command, channels, firmware, and direct-upgrade guard.
- System Snapshots defines the boot and restore path and its
/homeand bootloader limits. - Troubleshooting gives the official next steps when rollback is insufficient.