✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.

Switching a gaming PC from Windows to Linux rarely fails at the install screen. It fails a week earlier or a week later: earlier, when nobody checked whether the games that matter run, and later, when a formatted drive takes a save folder, a mod setup, or a peripheral configuration with it. The installation is the easy middle step of a longer move.

This site has already answered the whether question in its general Linux gaming explainer, which weighs Proton, anti-cheat, and distro suitability. This article is the how: a staged migration blueprint that starts with an audit of your library, hardware, and saves, runs both systems in parallel while you verify your real games, and only then moves your data across for good.

As an Amazon Associate, we earn from qualifying purchases.

Quick answer

Switch in stages, not in one wipe. First audit your Steam library on ProtonDB and the anti-cheat trackers, back up every save that Steam Cloud misses, then install Linux on a second drive and dual boot while you test your real games. Keep Windows until nothing you play needs it, and expect kernel anti-cheat titles to stay behind.

Step one: audit your library before you touch a disk

Make a list of the games you actually play, not the games you own, and sort them into three piles. The first pile is native Linux games and single-player titles with strong ProtonDB ratings; these move with you. The second pile is games whose multiplayer anti-cheat decides their fate: Easy Anti-Cheat and BattlEye both support Linux, but only when the publisher enables that support, so check each title on ProtonDB and the Are We Anti-Cheat Yet tracker rather than assuming. The third pile is everything tied to another launcher or store, handled in the inventory step.

Be honest about the second pile. If one blocked title is the game you play every night with friends, your plan is a dual boot, not a full switch, and knowing that now is the audit doing its job. Also note games that run with caveats in recent ProtonDB reports, so the parallel-run period can confirm them on your own hardware.

Step two: inventory your hardware and software

Walk your desk and your system tray and list everything that depends on Windows software. Gaming mice, keyboards, and headsets often store basic settings on the device but need a Windows suite for macros, lighting, or firmware updates; community tools such as Piper, Solaar, and OpenRazer cover many models, but coverage is partial, so check your exact devices against their supported lists. Devices with onboard memory are the forgiving kind: configure them under Windows before you move, and the settings travel with the hardware.

Then list the non-game software: capture and overlay tools, streaming setups, voice changers, work applications, and anything tied to a subscription. Note Game Pass separately, because the Xbox PC app is Windows-only; on Linux it is reachable through cloud streaming in a browser, not as local installs. Anything on this list with no Linux route becomes either a reason to dual boot or a farewell item, and it is better decided on paper than discovered after a format.

Step three: find and back up your saves before anything moves

Steam Cloud covers a large share of a modern library, but its gaps are exactly where long-running games live: titles that never enabled it, save files kept in the Documents or My Games folders, configuration files under AppData, emulator saves, screenshot libraries, and mod setups inside the game folder. Go game by game, find where each title keeps its progress on disk, and copy those folders to a portable drive. If the copy is incomplete, the loss happens here, quietly, before Linux is even installed.

State the risk plainly: formatting or repartitioning the Windows drive before this step is complete is the one unrecoverable mistake in the whole process. A distro can be reinstalled in an afternoon. A save folder that existed only on a wiped partition cannot. Keep the backup until the new system has opened the saves successfully.

Step four: run both systems in parallel

The parallel period is where the switch is decided. The safest layout is Linux on its own drive with Windows untouched on its; separate drives remove the whole class of accidents where one installer overwrites the other system. Install Windows first if you are rebuilding, then Linux, and turn off Fast Startup so Windows drives mount cleanly from the Linux side.

Use the parallel weeks for verification, not admiration. Play your top titles from the audit, including the caveated ones, check your peripherals under the community tools, and run your streaming or capture setup once end to end. Keep Windows updated and bootable: the exit decision is made by evidence, when a full cycle of your real gaming life has happened on Linux without a trip back. If a must-play game fails, you have lost nothing but time.

Step five: move the data and rebuild the library

With the audit proven, move in the order that protects you. Bring the save and configuration folders over first and confirm each game opens its progress. Then rebuild the library: the reliable route is fresh downloads from Steam onto a Linux-native file system. Copying game folders across can work, and Steam will verify the files, but sharing one NTFS library folder between both systems is a known source of breakage, because Proton prefixes and permissions differ. Keep separate libraries per system during the parallel period.

Non-Steam games come through Lutris or the Heroic Games Launcher, installed title by title from your existing store accounts. Expect this to be the slowest part of the move, and a few titles to stay behind on the Windows drive permanently. That is a normal outcome of a staged migration, not a failure.

What does not come with you

Honesty is the point of the audit, so here is the leaving-behind list in one place. Competitive titles whose publishers refuse Linux anti-cheat support stay on Windows: Valorant is blocked by its kernel-level Vanguard, Fortnite does not run on Linux through any supported route, and recent Call of Duty releases are listed as broken on the community trackers. Xbox Game Pass PC installs and Microsoft Store games do not transfer; only cloud streaming crosses over. Native Windows versions of creative and office suites stay behind, replaced by web versions or Linux alternatives. And some peripheral features, such as suite-only lighting effects or macro layers, may remain Windows-only even when the device itself works. None of this argues against switching. It argues for switching with the list written down.

The gear that makes the move safer

Five pieces of storage cover the whole blueprint: a fast stick for the installer, portable capacity for the backup and data move, and a dedicated internal drive so Linux never has to share a disk with Windows.

SanDisk Extreme PRO USB 3.2 Flash Drive 128GB (SDCZ880-128G-GAM46)

SanDisk Extreme PRO USB 3.2 Flash Drive 128GB (SDCZ880-128G-GAM46)

SanDisk Extreme PRO USB 3.2 Flash Drive 128GB (SDCZ880-128G-GAM46)

Check price on Amazon

The installer stick. A solid-state flash drive, so writing distro images and booting from it is quick, and the metal casing survives a drawer between installs.

  • Capacity: 128GB
  • Interface: USB 3.2 Gen 1, Type-A
  • Maker-rated speeds: up to 420 MB/s read, 380 MB/s write

Samsung T9 Portable SSD 2TB (MU-PG2T0B/AM)

Samsung T9 Portable SSD 2TB (MU-PG2T0B/AM)

Samsung T9 Portable SSD 2TB (MU-PG2T0B/AM)

Check price on Amazon

The move drive. Sized for a full save backup plus the game folders worth copying, and the natural permanent backup home after the switch.

  • Capacity: 2TB
  • Interface: USB 3.2 Gen 2×2, USB-C
  • Maker-rated speed: up to 2,000 MB/s sequential read

Crucial X10 Pro 2TB Portable SSD (CT2000X10PROSSD902)

The alternative move drive. A compact shell with dust and water resistance, suited to a backup drive that travels between machines rather than living on one desk.

  • Capacity: 2TB
  • Interface: USB 3.2 Gen 2×2, USB-C
  • Maker-rated speeds: up to 2,100 MB/s read, 2,000 MB/s write

Samsung 990 PRO 2TB NVMe SSD (MZ-V9P2T0B/AM)

Samsung 990 PRO 2TB NVMe SSD (MZ-V9P2T0B/AM)

Samsung 990 PRO 2TB NVMe SSD (MZ-V9P2T0B/AM)

Check price on Amazon

The dedicated Linux drive. Installed alongside the Windows drive, it gives the parallel period a clean home and becomes the main system drive when the switch is final.

  • Capacity: 2TB
  • Interface: PCIe Gen4 x4, NVMe, M.2 2280
  • Maker-rated speed: up to 7,450 MB/s sequential read

WD Black SN850X 2TB NVMe SSD (WDS200T2X0E)

WD Black SN850X 2TB NVMe SSD (WDS200T2X0E)

WD Black SN850X 2TB NVMe SSD (WDS200T2X0E)

Check price on Amazon

The second-drive alternative. A Gen4 gaming drive equally suited to the dedicated-Linux-drive role or to holding the consolidated library after Windows is removed.

  • Capacity: 2TB
  • Interface: PCIe Gen4 x4, NVMe, M.2 2280
  • Maker-rated speed: up to 7,300 MB/s sequential read

How to choose

Choose the run mode from your audit piles. If pile two came back empty and your software list is clean, a full switch on a fresh drive is reasonable. If anything you play weekly is blocked, dual boot on separate drives and revisit after each major game change. If the audit is mixed, the parallel period is the answer rather than a decision made in advance.

Choose the distro by temperament. Bazzite suits a gaming-first machine and switchers who want updates handled as system images with rollback. Linux Mint suits cautious switchers who want a familiar desktop and are willing to do a little more gaming setup by hand. Nobara and CachyOS suit tinkerers who want gaming tuning pre-applied and accept a faster-moving system. All four run the same Proton layer, so the choice is about maintenance style, not game compatibility.

Who should skip this

Skip the switch, or stop at dual boot, if your main game is a competitive title whose anti-cheat blocks Linux, if your library lives in the Xbox PC app, or if work software with no Linux route shares the machine. Also skip the full wipe if you have not completed the save backup step; that version of the move is a gamble, not a migration.

FAQ

Can I keep Windows and Linux on the same PC?

Yes, and this blueprint recommends exactly that during the parallel period. Separate drives are the safest layout: install Windows first, disable Fast Startup, then install Linux on its own drive and pick the system at boot.

Will my Steam library carry over?

Your purchases and most cloud saves carry over automatically. Games still need to be installed under Linux, either as fresh downloads or copied folders that Steam verifies, and each Windows game gets its own Proton prefix on the Linux side.

What happens to games with anti-cheat?

It depends on the publisher. Easy Anti-Cheat and BattlEye can support Linux when the publisher enables it, and many titles do. Kernel-level systems that refuse Linux, such as Vanguard in Valorant, keep those games on Windows only.

Should I wipe Windows on day one?

No. Wipe it only after the parallel period has covered your real routine: your main games played, saves opened, peripherals working, and nothing left that sends you back. Until then the Windows drive is your rollback plan.

Final verdict

A Windows-to-Linux switch succeeds as a logistics project, not as an act of enthusiasm. Audit the library and the desk first, protect the saves, run both systems until the evidence is boring, and the actual installation becomes the smallest step in the move. Do it in that order and the games, settings, and progress that matter arrive with you; skip the audit and the same switch becomes a story about what got left behind.

Explore Our Guides & Free Tools