Nobara used to treat every new version like a fresh start, and older guides still tell you to wipe your drive and reinstall from a new ISO. That advice is out of date. Since Nobara 42, released in May 2025, the project has officially been a rolling release, which means moving to a newer version happens through the system updater you already have, not through a reinstall.
The catch is that Nobara’s updater is not interchangeable with the tools Fedora users are used to. Run the wrong command and you can desync Nobara’s patched packages from its repositories. Below: the documented upgrade path, the pre-flight checklist that protects your data, and the recovery options if an upgrade goes sideways.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
Since Nobara 42, Nobara is a rolling release, so version upgrades arrive through the Nobara updater rather than a reinstall. Run DNF App Center or nobara-sync, let core updates apply offline at reboot, and never use plain dnf update or Fedora’s system-upgrade path. Back up your home folder and game saves first.
How Nobara version upgrades actually work
The single most important fact about upgrading Nobara is that the project maintains its own update machinery, and it expects you to use it. The Nobara wiki is blunt about why: the updater does more than download packages. It checks for changes to the system’s repositories, syncs installed packages to upstream versions, and can roll a package back if it is pushed and later pulled. Plain dnf update does none of that syncing, which is why the wiki states that dnf update is simply not enough on Nobara.
The rolling model changed what a version number means. When Nobara 42 launched, people still running Nobara 41 received the 42 package set through the system updater as rolling updates, and the project has kept that model since, including the current 44 line. A kept-up-to-date installation simply follows the project as its repositories move to a newer Fedora base.
There are two hard limits, both from the project’s own FAQ. First, the window is not open forever: when a new version is released, the old repositories are deleted within about six months, because the project cannot afford to host them indefinitely. An installation left un-updated for over a year has no upgrade path left and needs a clean installation. Second, this path only exists for Nobara itself. Converting a Fedora installation into Nobara by adding its repositories is explicitly not supported and will break the system.
The upgrade procedure, step by step
Start from a healthy, fully updated system. Open the Nobara Welcome app or the app menu and launch DNF App Center, Nobara’s graphical updater. Choose Select All and Update, which applies everything and runs the updater’s sync routines. If you prefer a terminal, or you are working over SSH or from a TTY, run nobara-sync instead. The –all flag also brings Flatpak packages along in the same pass.
Expect the process to behave differently depending on what is being updated. Ordinary application updates can install while you work. Updates that touch core components such as the kernel, the graphics stack, or the package manager itself are prepared during your session and then applied in offline mode at the next restart, before the desktop loads, in ordered groups, so the running system is never left half-updated. Let it finish, even if the machine sits at the update screen longer than expected. Interrupting an offline update is one of the few reliable ways to turn a routine upgrade into a recovery job.
When the system comes back up, run the updater once more to confirm nothing remains pending, then verify the basics: your display driver is loaded, Steam launches, and a game that worked yesterday still starts. Also re-check the Driver Manager afterwards, since driver packages may have been replaced by the new base.
Pre-flight checklist: back up before you touch anything
Rolling upgrades are designed to preserve your system, but designed to is not a guarantee. Treat any version-level move as an operation that can, in the worst case, cost you the installation, and make the backup before you start, on storage that is not the drive being upgraded.
Work through this checklist in order:
- Copy your entire home folder to external storage, including hidden folders. Your documents, desktop settings, and most application data live there.
- Back up your game saves explicitly. Steam Cloud covers many titles, but not all, and local-only saves sit inside each game’s Proton prefix under the steamapps compatdata folders. Copy those folders, not just the installs.
- Save a list of what you have installed: your Flatpak list, any extra repositories you added, and tools you installed by hand. A text file is enough.
- Keep a current Nobara ISO on a USB stick within reach. If everything fails, it is your route back to a working machine.
- Plug the machine into power and give the upgrade an uninterrupted window. Do not start it on a battery you cannot trust.
Be honest about what a backup cannot do: it cannot save an installation whose repositories have already been deleted, and it cannot make an unsupported Fedora conversion supported. It protects your data, the part that cannot be re-downloaded.
What carries over, and what does not
On a normal rolling upgrade, almost everything you care about carries over because the upgrade happens in place. Your home folder is untouched, your Steam library stays where it is, and your Proton prefixes survive, so per-game tweaks and in-prefix saves persist. Proton-GE and the rest of Nobara’s gaming stack are ordinary packages in this model, updated and synced by the same updater rather than reinstalled by hand. Flatpaks can update in the same pass, and your desktop configuration carries through.
What does not carry over is anything that depended on the old repositories. Once the project deletes an old release’s repos, packages pinned to that base stop receiving fixes, which is why staying reasonably current matters on Nobara more than on a fixed-release distribution. Manual edits that fight the package manager are also at risk: the sync step deliberately pulls drifted packages back to repository versions, so undocumented hacks can be reverted without asking. Note any deep manual changes before upgrading so you can reapply the ones you still need.
If the upgrade goes wrong
Most failed upgrades on Nobara are recoverable, and the project ships tools for exactly this situation. If an update transaction fails partway, the updater’s newer design can fall back at boot: the bootloader selects a previous system recovery entry, and a System Update Recovery tool explains what happened and can save a report with updater logs for support.
From a working terminal or TTY, two commands cover most repairs. nobara-sync repair addresses common updater and package-database problems, and nobara-sync retry-update is the documented follow-up after a manual repair: it validates the RPM database and dependencies and prepares a fresh transaction. If the graphical updater itself seems stuck, update the updater first with sudo dnf update nobara-updater –refresh, then run it again.
If the machine will not boot to a desktop at all, choose an older kernel entry from the boot menu if one is offered, and run nobara-sync from a TTY. The point of no return is a system so old that its repositories no longer exist; then the honest fix is a clean installation, and your backup becomes the thing that saves your data.
Storage worth having before you upgrade
The products below are the practical kit for this job: fast external storage for the backup itself, a quick internal drive if a clean install doubles as a hardware refresh, and a sturdy USB stick for installer media.
- Samsung T9 Portable SSD 2TB: a compact USB drive fast enough that backing up a home folder and game saves is a short job, not an overnight one.
- Crucial X10 Pro 2TB Portable SSD: another high-speed portable option, useful as a backup target you can unplug and store away from the machine.
- WD Black SN850X 2TB NVMe SSD: a fast internal drive for anyone pairing a clean install with a storage upgrade.
- Samsung 990 PRO 2TB NVMe SSD: a second strong internal option for a fresh installation with a growing game library.
- Samsung BAR Plus 128GB USB Flash Drive: a metal-bodied stick that holds the Nobara installer comfortably and survives being carried as recovery media.
How to choose
Choose the in-place upgrade if your installation is current or only a version behind, you update at least every few months, and your system is otherwise healthy. That is the path the rolling model was built for, preserving your setup with the least work.
Choose a clean installation if any of these apply: the machine has not been updated in over a year and its repositories are gone; you are coming from Fedora or another distribution; you have deep manual modifications you cannot account for; or you are replacing the system drive anyway. A clean install also resets accumulated quirks no updater can untangle.
If you are between those cases, a system a few versions old but still within the repository window, upgrade in place first and keep the installer USB ready. You lose little by trying the supported path before a wipe.
Who should skip this
Skip this guide if you are not running Nobara at all: Fedora users cannot convert an existing installation with Nobara’s repositories, and other distributions have their own upgrade procedures. Also skip the in-place path, and plan a clean install instead, if your Nobara system has been un-updated for more than a year, because the upgrade path for it no longer exists.
FAQ
Can I upgrade Nobara with dnf system-upgrade like Fedora?
No. Nobara does not follow Fedora’s system-upgrade path. The documented route is the Nobara updater, DNF App Center on the desktop or nobara-sync in a terminal, because it also syncs repositories and package versions in ways dnf does not.
I have not updated my Nobara install in over a year. Can I still upgrade?
Almost certainly not. The project deletes a release’s repositories within six months of a new version, and its FAQ states there is no upgrade path for installations left that long. Back up your data and clean-install the current version.
Will I lose my games and saves when I upgrade?
On a normal in-place upgrade, no: your home folder, Steam library, and Proton prefixes carry over. The exception is a failed upgrade that ends in a reinstall, which is why backing up your home folder and the compatdata folders in your Steam library matters first.
Why does the updater reboot into an offline update screen?
Core components such as the kernel and graphics stack are applied offline at restart so the running system is never left half-updated. Application updates install immediately during your session; system-level changes are staged and applied in ordered groups before the desktop starts.
Final verdict
Upgrading Nobara in its rolling era is mostly a discipline problem, not a technical one. Use the project’s own updater rather than Fedora habits, stay inside the repository window so the path never expires, and treat a real backup as part of the procedure. Do those three things and a version upgrade becomes routine maintenance. Ignore them, and it becomes a reinstall you did not plan for.











