How to Install Bazzite on a Gaming PC (Step-by-Step 2026)

To install Bazzite, download the image that matches your GPU from bazzite.gg, write it to an 8GB+ USB stick with Fedora Media Writer or Rufus in DD mode, disable Secure Boot (or enroll the Universal Blue key), boot from the stick and run the graphical installer. Budget about 20 minutes plus download time.

Bazzite is the default answer for anyone who wants a SteamOS-style experience on hardware Valve never shipped, and the install is simpler than most distributions because little needs configuring afterward. Here is the full process, including the BIOS settings that trip people up.

What Bazzite Actually Is

Bazzite is an immutable, Fedora-based image built on Universal Blue with gaming drivers, Steam, Lutris, Heroic and a tuned kernel already baked in. “Image-based” is the important part: instead of installing packages onto a system you assembled yourself, you boot a complete, pre-tested system image. Updates replace the whole image atomically, so an update either works or you reboot into the previous one.

Practically, the Mesa stack, NVIDIA modules, Gamescope, MangoHud, controller drivers and the Proton plumbing arrive already wired together. There is no “install drivers, break the desktop, reinstall” phase. If you have bounced off other Linux gaming distributions because a kernel update killed your GPU on a Tuesday, that is the problem this design solves. The trade-off: no casual dnf install into the root filesystem. Apps arrive another way, covered below.

Choosing the Right Bazzite Image Variant

This is the only decision that really matters. Picking the wrong image is the most common cause of a black screen on first boot, so match it to your GPU and form factor before downloading.

Two clarifications. The “Deck” images are not Steam Deck exclusive — they are the couch-gaming variant, so pick one if the machine plugs into a TV and gets used with a controller. For NVIDIA, newer architectures want the open kernel modules build; only cards the current driver branch has dropped need the proprietary image. If unsure, check your model against the current NVIDIA driver support tiers on Linux.

Step 1: Create the USB Installer

1. Download the .iso for your chosen variant. Expect roughly 4-6GB, so use an 8GB or larger stick.
2. Verify the published checksum. A truncated ISO produces installer errors that look like hardware faults and waste an hour.
3. Write it with Fedora Media Writer, Rufus in DD mode on Windows, or dd on Linux. Do not use Rufus in ISO mode — the hybrid image needs a raw write.

Ventoy works for many people but is a known source of odd failures with Fedora-derived images. If anything goes wrong, re-flash with a plain DD write first.

Step 2: BIOS and UEFI Settings

Reboot into firmware setup (usually Del or F2) and change four things.

Secure Boot

Bazzite ships signed kernel modules, but your firmware does not trust the Universal Blue key yet. Either disable Secure Boot, or leave it on and enroll the key after installation with ujust enroll-secure-boot-key, then enter universalblue as the MOK password at the blue prompt on the next reboot. Enrolling is the better long-term answer on a dual-boot machine.

SATA Mode

Set the storage controller to AHCI, not RAID or Intel RST. Prebuilts and laptops frequently ship in RST mode, and the installer simply will not see the drive. If Windows is already on that drive, boot Windows once in safe mode after the change or it will refuse to start.

CSM, Fast Boot and Memory Profiles

Disable CSM so you get a clean UEFI install, and disable firmware Fast Boot so the USB stick is detected. Leave Resizable BAR enabled. If you are also tuning XMP/EXPO, settle it now — unstable memory produces installer crashes that look like distro bugs. Same stability checklist as any new gaming PC build.

How to Install Bazzite: The Installer Walkthrough

1. Boot the USB from the firmware boot menu (F8/F11/F12). You land in a live desktop or straight in the installer.
2. Set language, keyboard and timezone. Timezone matters for the dual-boot clock issue below.
3. Select the destination. For a dedicated drive, use the whole disk. For dual-boot, shrink the Windows partition from inside Windows first (Disk Management → Shrink Volume), then install into the free space.
4. Leave the existing EFI partition alone if Windows is present. Bazzite installs alongside rather than replacing it. Deleting that partition is how people lose Windows.
5. Create your user account. Administrator rights are fine for a single-user gaming machine.
6. Install. It takes 5-15 minutes depending on your SSD speed. Remove the USB when prompted and reboot.

First Boot: Drivers, Steam and ProtonDB

• Run ujust update in a terminal. This pulls the newest image plus Flatpak updates in one pass.
• Reboot. Image updates only take effect after a restart — the single most common “it didn’t work” moment for new users.
• Sign into Steam, then confirm Steam Play is enabled for all titles under Settings → Compatibility.
• Check ProtonDB before buying or troubleshooting. Most single-player games run at Gold or Platinum with zero effort; the ones that do not are almost always multiplayer titles with kernel-level anti-cheat. See how Proton compatibility ratings work for reading those reports.

Controllers, including Xbox wireless and DualSense, pair without extra drivers. HDR and VRR work on supported displays under KDE Plasma, and handheld images detect built-in controls automatically.

Living With an Immutable System

The root filesystem is read-only, so software arrives through one of three paths.

Flatpak (use this 90% of the time)

Open Discover, search, install. Flathub is preconfigured. Browsers, Discord, OBS, emulators and media apps are sandboxed and update independently of the system image.

Distrobox (for anything Linux-y)

Need an Arch or Ubuntu environment for a specific tool? distrobox create gives you a container sharing your home directory that can export apps to your menu. Developer tooling belongs here, not on the host.

rpm-ostree layering (last resort)

rpm-ostree install packagename adds an RPM to your next image build, applied after a reboot. Supported, but every layered package slows updates and adds conflict risk. Keep the list short — VPN clients and hardware-specific drivers are the legitimate cases; CLI tools belong in the bundled Homebrew.

Dual-Booting With Windows and the Clock Drift Gotcha

If you dual-boot, your clock will jump by several hours after switching systems. Linux stores the hardware clock in UTC; Windows reads it as local time, so each one “corrects” it and the other sees the wrong time.

Fix it on the Windows side by adding a DWORD named RealTimeIsUniversal set to 1 under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation. You can instead run timedatectl set-local-rtc 1 on Linux, though that handles daylight saving less cleanly.

Also disable Windows Fast Startup (Power Options → Choose what the power buttons do). It hibernates the kernel rather than shutting down, leaving NTFS partitions dirty so Linux refuses to mount them properly.

Troubleshooting Bazzite Install Problems

Black screen after install on NVIDIA

Almost always the wrong image. Re-check whether your card needs the open-module or proprietary build. To get in temporarily, press e at the boot menu and add nomodeset to the kernel line, then reinstall with the correct variant.

Secure Boot refuses the image

Disable Secure Boot in firmware, or boot with it off, run ujust enroll-secure-boot-key, reboot, choose Enroll MOK and enter universalblue. The enrollment screen appears before the desktop and times out — if you miss it, run the command again.

The installer cannot see my SSD

Storage controller is in RAID/Intel RST mode. Switch to AHCI in the BIOS, and on a Windows dual-boot machine boot Windows into safe mode once so it loads the AHCI driver.

Performance is worse than Windows

Confirm you rebooted after the first update, that the game uses Proton Experimental or GE-Proton, and that your refresh rate is set correctly. Enable MangoHud to see whether you are CPU or GPU bound first — same logic as tracking down a CPU bottleneck on Windows.

USB stick will not boot

Re-flash in DD mode, disable Fast Boot and CSM, and try a rear USB 2.0 port. Front-panel headers are unreliable during early boot.

Frequently Asked Questions

Is Bazzite the same as SteamOS?

No, but it is the closest practical equivalent on desktop hardware. SteamOS is Arch-based and built by Valve primarily for the Steam Deck; Bazzite is Fedora-based, community-built, and runs on ordinary PCs including NVIDIA systems that SteamOS does not properly support. The Deck images reproduce the Game Mode console experience, so daily use feels very similar even though the underlying system differs completely.

Should I move from SteamOS or Nobara to Bazzite?

If you want Game Mode on non-Valve hardware, Bazzite is the stronger choice because SteamOS installs outside the Deck are unofficial and driver support is narrow. Coming from Nobara, the difference is mutability: Nobara is a traditional Fedora system you maintain yourself, Bazzite is an image you receive pre-tested. Choose Nobara if you enjoy tinkering with the base system, Bazzite if you want it to stay working.

Can I install Bazzite without losing Windows?

Yes. Shrink the Windows partition from within Windows Disk Management, install Bazzite into the free space, and leave the existing EFI system partition untouched so both bootloaders coexist. A separate physical drive for each OS is safer still, since a Windows feature update can occasionally overwrite the bootloader on a shared drive. Always back up before repartitioning.

Does an immutable system stop me installing what I want?

Not in practice. Flatpak covers nearly every desktop application, Distrobox gives you a full mutable Linux environment for anything else, and rpm-ostree layering adds RPMs directly to the system image when you genuinely need them. The restriction is narrow: you cannot casually scatter files across the root filesystem, which is exactly the behaviour that breaks traditional installs.

Which Bazzite image do I need for an NVIDIA card?

Use the NVIDIA open-kernel-module image for RTX 20-series and newer cards, which covers nearly everything sold in the last several years. Older GTX 900 and 10-series cards fall on the legacy proprietary driver branch and need the corresponding proprietary image. Install the wrong one and the usual symptom is a black screen at the login manager rather than an error message, so verify your card model first.