How to Install Bazzite (SteamOS) on Any Mini PC: Step-by-Step
Bazzite turns almost any mini PC into a Steam-Deck-style console for free. This step-by-step guide covers the compatibility checklist, picking the right ISO image, flashing the USB, the installer, Secure Boot key enrollment, and the post-install fixes for Wi-Fi, NTFS drives, and anti-cheat games.
By GamepadSquire — October 7, 2026Verified
The five-minute version
Bazzite is a free, Fedora-based operating system that turns almost any mini PC into a Steam-Deck-style console: boot straight into Steam's big-picture game mode, navigate with a controller, and play a Windows library through Proton without ever touching a command line. It is the community answer to a gap Valve left open — official SteamOS only ships for a short list of devices, and a generic mini PC is not on it. Bazzite runs on AMD, Intel, and NVIDIA hardware, installs from a familiar graphical installer, and can keep Windows alongside it on the same drive.
The catch is that "almost any mini PC" hides a handful of hard requirements that ruin installs when ignored. The official documentation is thorough but scattered across a dozen pages; this guide condenses the whole path — compatibility check, image choice, USB flash, install, Secure Boot enrollment, and the post-install fixes most people need — into one place, with the failure modes called out before you hit them.
Budget about 45 minutes end to end: 10 minutes of prep, a 5–10 GB download depending on image, roughly 15 minutes of installer time on a modern NVMe drive, and the rest for first-boot setup.
Step 0: the compatibility checklist
Run through this before downloading anything. Every item below comes from Bazzite's official hardware compatibility guide, and each one is a hard stop, not a nice-to-have.
| Requirement | Minimum | Notes |
|---|---|---|
| Firmware | UEFI | CSM/Legacy boot is unsupported — old MBR-style BIOS booting will not work |
| CPU | 2 GHz quad-core, x86-64 | Effectively any mini PC from the last decade |
| RAM | 8 GB | 16 GB+ is the practical comfort zone for modern titles |
| GPU | Vulkan 1.3 capable | Check with vulkaninfo | grep 'Instance Version' from a live USB |
| Storage | 50 GB free on internal SSD | 120 GB recommended; SSD required, not HDD |
| Partition table | GPT | Installs to MBR disks fail; Microsoft's MBR2GPT tool converts existing Windows installs |
| Install USB | 16 GB+ flash drive | SD/microSD boot "may work" but most firmware refuses it |
Three compatibility traps account for most failed installs:
NTFS game drives do not work. This is the single most common heartbreak for people migrating from Windows. Bazzite (and Linux gaming generally) cannot run Proton games from an NTFS partition — not "runs slowly," but eventual data corruption, per the official docs. Secondary drives must be reformatted to BTRFS for SSDs or Ext4 for HDDs, which wipes them. exFAT and FAT32 are equally unsupported because they lack the symbolic links Proton prefixes need. Plan to move games off, reformat, and move back.
Secure Boot must be handled, not fought. Bazzite supports Secure Boot, but only after you enroll Universal Blue's signing key — otherwise you get a black screen with a bad shim signature error. The enrollment step is painless (covered in Step 6) but skipping it is the most common "Bazzite won't boot" report.
Vulkan version matters more than GPU brand. A GPU stuck on Vulkan 1.1 or 1.2 can still game through Proton-CachyOS with DXVK-Sarek, but it is a workaround with real limits — the maintainers explicitly warn against it for anti-cheat and multiplayer titles. If vulkaninfo reports 1.3 or later, ignore this entirely.
One more prep item that is easy to forget: back up the target drive. The installer wipes whatever disk you point it at, and the docs' advice to physically unplug other internal drives during install is worth taking — it removes any chance of choosing the wrong disk at the partitioning screen.
Step 1: pick the right image
This is where most guides wave their hands, and it is genuinely the most consequential choice you will make. Bazzite ships as separate ISOs per GPU vendor and experience, and picking wrong means a reinstall.
| You have… | You want… | Download |
|---|---|---|
| AMD or Intel graphics (most mini PCs) | Console-style boot-to-Steam | bazzite-deck (AMD) or bazzite-deck-intel |
| An NVIDIA mini PC | Console-style boot-to-Steam | bazzite-deck-nvidia — supported, with major caveats the maintainers openly acknowledge |
| Any GPU | A normal desktop that also games | bazzite (desktop image, Steam installed but no game mode) |
The -deck variants boot directly into Steam's controller-friendly Gaming Mode — the console experience — with a full KDE Plasma (or GNOME) desktop one power-menu click away. The desktop variant skips game mode entirely. For a mini PC under a TV, the deck image is the point; for a desk machine, the desktop image behaves like any other Linux with gaming preconfigured.
NVIDIA deserves one honest paragraph: the proprietary drivers are baked into the -nvidia images and work, but community consensus is that the experience trails AMD — the maintainers describe the caveats as "major" and largely out of their control. If you are buying a mini PC specifically to run Bazzite, choose AMD or Intel graphics and skip the issue. If you already own an NVIDIA box, it will run; just calibrate expectations around edge cases in game mode and HDR.
Two more decisions at download time:
- KDE vs GNOME: KDE Plasma is the default and matches SteamOS; GNOME suits touch-first users. Both are available on every variant.
- ISO vs rebase: The ISO is the normal path for Windows converts. If the machine already runs Fedora Atomic (Silverblue/Kinoite/Bluefin), you can instead rebase in place with
rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable— no USB stick required. Everyone else: ISO.
Download from the official portal at download.bazzite.gg. If the direct download crawls, the docs recommend a download manager such as Motrix — the ISOs are multi-gigabyte and a corrupted transfer wastes an evening. Verify the SHA256 checksum the docs provide before flashing; it takes thirty seconds and rules out the most confusing installer crashes.
Step 2: flash the USB
You need a 16 GB or larger flash drive and one of three tools, all free:
- Fedora Media Writer — recommended by the Bazzite team, available for Windows, macOS, and Linux
- Rufus — the Windows standard
- Ventoy — works, but requires extra steps for Secure Boot, so avoid it for this job if Secure Boot is enabled
Flashing is a single button in any of the three: pick the Bazzite ISO, pick the drive, write. The drive gets wiped in the process. A wired keyboard and mouse for the target machine are also strongly recommended — the installer needs real input devices, though an on-screen keyboard exists for edge cases.
Step 3: boot the installer
With the flash drive inserted, power on and hit the boot menu key. On mini PCs this is usually F7, F9, F11, or F12 depending on vendor — the official docs correctly note you may need to consult your manual or watch the splash screen hints. Change the boot order in BIOS only if the hotkey route fails, and switch it back afterward.
On handhelds the pattern is different: hold Volume Down and tap Power, release both at the startup chime, then pick your USB device from the Boot Manager.
If the machine refuses to boot the stick, two suspects: Secure Boot (disable it in BIOS for now — Bazzite's key enrollment in Step 6 lets you re-enable it later) or an MBR-partitioned internal disk (see Step 0).
The live environment that loads is a fully working Bazzite desktop. It is safe to poke around — but do not judge performance from it, and note that the live session runs a different kernel with less hardware support than the installed system, so missing audio or Wi-Fi here does not predict the installed experience.
Step 4: run the installer
Launch the installer from the live desktop. The flow is conventional:
- Language, region, keyboard layout — straightforward.
- Partitioning — select the target disk. This wipes it. Automatic partitioning is the only option on the current ISO, which is fine for dedicated machines.
- Dual-boot? If you are keeping Windows on the same drive: disable BitLocker and Fast Startup from inside Windows first, shrink the Windows partition with Disk Management to leave room, then let the installer's automatic partitioning do its thing, and finish with
ujust regenerate-grubin a terminal after first boot so Windows appears in the boot menu. Be aware of a known upstream installer bug: the "format as efi" button claims it will format the Windows EFI partition but actually just adds Bazzite to it. Also note the docs' guidance that dual-booting other Linux distros on the same drive is not officially supported — separate drives and the motherboard's UEFI boot menu are the sane approach there. - Disk encryption (optional) — LUKS is offered in the installer. If you use it, you will need a physical USB keyboard at every boot to type the passphrase. For a living-room console this is usually overkill.
- User account — create your username and password; skip the optional root account (the docs recommend against enabling one).
Installation itself takes on the order of 10–20 minutes from a decent NVMe SSD. Reboot when prompted and pull the USB stick as the machine restarts.
Step 5: first boot and the Secure Boot dance
On first boot with Secure Boot disabled, you land straight in your new desktop (or Steam Gaming Mode on deck images) and can skip to Step 6. The interesting case is Secure Boot enabled, where a blue MOK Manager screen appears:
- Choose Enroll MOK
- Continue, then enter the password:
universalblue - The password entry shows nothing as you type — invisible characters are intentional, not a frozen screen
- One non-QWERTY gotcha documented by the team: the enrollment prompt assumes an English QWERTY layout regardless of your physical keyboard, so AZERTY users must mentally transpose keys
- Reboot when asked; the key sticks across updates
If you skipped enrollment and hit the bad shim signature / you need to load the kernel first black screen, the fix is not a reinstall: disable Secure Boot in BIOS, boot Bazzite, run ujust enroll-secure-boot-key in a terminal (same universalblue password), reboot, and re-enable Secure Boot. The ujust bios command reboots straight into firmware settings on machines that support it. One documented quirk to remember: a future BIOS update can silently re-enable Secure Boot and resurrect the error — same fix applies.
Step 6: post-install essentials
First session priorities, roughly in order:
- Sign into Steam on deck images and let the shader pre-caching begin; the first few hours of any Linux gaming box are its roughest, and every hour of settling improves frame pacing.
- Open the Bazzite Portal. This first-run utility installs the ecosystem pieces people usually want within minutes: EmuDeck or RetroDECK for emulation, Decky Loader for game-mode plugins, ProtonUp-Qt for alternate Proton builds, LACT for GPU control, plus browser and launchers.
- Let it update. Updates are automatic and atomic — the OS, Flatpaks, and firmware arrive as complete images, not incremental packages. If an update ever misbehaves,
rpm-ostree rollback(or picking the previous image at the boot menu) reverts the whole OS in minutes. This rollback safety is arguably Bazzite's biggest practical advantage over a traditional distro, and it is worth knowing exists before you need it. - Fix those NTFS drives. Any secondary drive with Windows games on it must be reformatted BTRFS/Ext4 before use (see Step 0). Bazzite will nag about NTFS for good reason.
- Explore
ujust. Bazzite's task runner exposes dozens of safe, documented commands —ujust bios,ujust regenerate-grub,ujust enroll-secure-boot-key— and is the intended way to do system chores without copy-pasting forum commands.
The problems people actually hit
A pattern is visible across the Bazzite community forums and Reddit support threads, and it is worth setting expectations honestly:
Wi-Fi vanishing after install or update is the most commonly reported issue — threads about MSI boards and Intel wireless cards appear repeatedly. It is usually firmware or driver loading rather than a Bazzite defect, and typical fixes include a BIOS update, checking that the card is enabled in firmware settings, or using a compatible USB Wi-Fi adapter (the docs keep a list). If your mini PC's primary use is under a TV with no ethernet run, test Wi-Fi in the live environment first and keep a USB adapter as a plan B.
Games that refuse to launch trace back to two usual suspects: an NTFS-formatted game library (unsupported, see above) or anti-cheat. Games with kernel-level anti-cheat that blocks Linux — competitive titles with Easy Anti-Cheat or BattlEye configured against Proton — are the honest limit of any console-style Linux. Check a title's community status before assuming a bug.
Installer crashes or corrupted downloads are why the SHA256 check exists. Multi-gigabyte ISOs over flaky connections fail in creative ways; re-verify before anything else.
HDR and VRR ship enabled by default in Bazzite — a genuine advantage over most distros — but TV-side settings still need to cooperate, and the NVIDIA caveat from Step 1 applies doubly to HDR on game mode.
When you should install official SteamOS instead
Valve now distributes a SteamOS recovery image for generic PCs, and it is worth being precise about when that is the better call. Per Valve's official documentation, the devices that are officially "Powered by SteamOS" are the Steam Deck, the Steam Machine, the Steam Frame, and the Lenovo Legion Go S, with beta-tier support for the Legion Go, ROG Ally and Ally X, other AMD handhelds, and AMD discrete GPUs. The official image is wipe-and-install only, targets AMD hardware, and offers no dual-boot, no disk encryption, and no Secure Boot enrollment path. Valve's own support pages note that Steam Support has limited ability to troubleshoot PCs outside the official device list.
So the split is clean: running one of those named AMD devices, especially a Legion Go S — official SteamOS. Anything else, particularly NVIDIA or Intel graphics, a dual-boot plan, or encryption — Bazzite. Community discussion consistently lands on the same divide, with Bazzite praised as the "just works" option for the hardware Valve does not cover. For the full four-way comparison — including ChimeraOS and Windows — see SteamOS vs Bazzite vs ChimeraOS vs Windows.
FAQ
Is Bazzite really free? Yes — completely, including all preinstalled software. It is an open-source community project built on Fedora Atomic and Universal Blue tooling.
Can I keep Windows on the same drive? Yes. Disable BitLocker and Fast Startup in Windows first, shrink the Windows partition with Disk Management, install with automatic partitioning, then run ujust regenerate-grub after first boot. Separate drives are the lower-drama option.
How big should the USB stick be? 16 GB minimum per the official installer requirements. The recovery-style image does not fit smaller sticks.
Do my Windows games actually run? Most do, via the Proton compatibility layer Steam applies automatically. The persistent exceptions are multiplayer titles whose kernel-level anti-cheat blocks Linux clients. Single-player libraries convert remarkably well.
Can I game from my existing NTFS drive? No — and this is a data-integrity issue, not a performance preference. Reformat secondary drives to BTRFS (SSD) or Ext4 (HDD) and reinstall or copy games over.
What if the update breaks something? Roll back. Atomic updates mean the previous OS image stays on disk; rpm-ostree rollback or the boot menu's previous-image entry restores it in minutes. This is the core safety net of the whole architecture.
Does it work on old hardware? Down to the limits in Step 0: UEFI firmware, Vulkan 1.3, 8 GB RAM, internal SSD. Below Vulkan 1.3 you are in Proton-CachyOS/DXVK-Sarek territory — workable for single-player, discouraged for anti-cheat titles.
Where does the universalblue password get used? Only for Secure Boot key enrollment (MOK). It is not your user password and not a security boundary — it is the documented passphrase for Universal Blue's public signing key.
Verdict
Installing Bazzite on a mini PC in 2026 is a genuinely good deal: a free, console-grade gaming OS with automatic atomic updates, boot-to-Steam game mode, and hardware support that spans every GPU vendor — for the price of a 16 GB USB stick and an hour. The failure modes are known, documented, and almost entirely preventable with the Step 0 checklist: UEFI firmware, a real SSD, GPT disks, no NTFS game libraries, and a Secure Boot key enrollment you now know the password for. For hardware outside Valve's official SteamOS device list — which is nearly every mini PC on the market — Bazzite is not the fallback option; it is the mainstream one.
Related Guides
Buying Guide
SteamOS vs Bazzite vs ChimeraOS vs Windows: Which OS for Your Mini PC?
Four operating systems can run a gaming mini PC in 2026, and picking wrong is about ignored constraints, not performance. This comparison maps GPU support, dual-boot, Secure Boot, and encryption across official SteamOS, Bazzite, ChimeraOS, and Windows — with install links and a four-question decision path.
Buying Guide
Stick Drift Test: How to Check Any Controller in 5 Minutes
Free browser test measures your stick drift on a 0.00-1.00 scale in five minutes — plus per-console recalibration paths for PS5, Xbox, Switch and Steam Deck, and the fix ladder from free recalibration to Hall effect replacement.
Buying Guide
Best Mini PCs for Gaming in 2026: Compact Gaming PCs for Every Budget
From the $350 APU boxes that crush esports to the $1,599 ROG NUC 970 with desktop-class RTX 4070 power — the honest 2026 guide to mini gaming PCs. Covers the Beelink SER7, Minisforum HX99G, the ASUS-owned NUC line, what games actually run well on each tier, eGPU options via OCuLink and USB4, and the thermal reality most reviews bury.