Games Not Working on Steam? Fixes for Windows in 2026

The short version: work through Steam fixes in a strict order, starting with the free 30-second checks and only moving to the slow, drastic ones if those fail. Most Steam launch problems on Windows come down to a corrupted download cache, an out of date GPU driver, or Windows Defender blocking a file it shouldn't. Skip the order and you'll spend an evening reinstalling a 90GB game for a problem that a driver update would have fixed in five minutes.

Why order matters more than most guides admit

Most "fix Steam games" articles list ten things and let you pick your favourite. That's a bad system. Some of these fixes take ten seconds. Others take three hours and can wipe your saved progress or your entire game install. If you reinstall a 60GB game before you've checked whether your antivirus is quarantining the launcher, you've wasted an evening and your broadband allowance for nothing.

So here's the order I'd work through, cheapest and fastest first, most disruptive last.

1. Restart Steam, not just the game

Close Steam completely, not just the game window. Right-click the Steam icon in the system tray, choose Exit, wait for it to fully close in Task Manager (check the Processes tab, look for steam.exe and steamwebhelper.exe), then reopen it. A huge number of "game won't launch" reports on the Steam community forums are solved by this alone, because Steam's background client sometimes hangs onto a broken connection to a game process from a previous crash.

2. Check Steam's own server status

Before you touch a single setting, check Steam's own stats page or a third party status tracker. Valve's servers do go down, usually during huge sales or major updates, and when they do, downloads stall and games refuse to verify licences even though nothing on your PC is broken. I'd rather you spend two minutes confirming the problem isn't on Valve's end than an hour reinstalling drivers for nothing.

3. Verify integrity of game files

In your Steam library, right-click the game, choose Properties, then Local Files, then "Verify integrity of game files." This checks every file against Steam's records and re-downloads anything corrupted or missing. It takes anywhere from 30 seconds for a small game to around 15 minutes for something like Cyberpunk 2077's 70GB install.

Here's the uncomfortable bit almost nobody says out loud: this step fixes far fewer problems than its popularity suggests. It's the "have you tried turning it off and on again" of PC gaming, recommended by default because it's easy and harmless, not because it's statistically likely to work. If your game crashed once and launches fine the second time, fine, verify away. If it's crashing every single time on launch, this step is very likely to come back clean and you'll have wasted fifteen minutes confirming what you already knew.

4. Update your GPU drivers, not just Windows

This is the fix that resolves the most problems, and it's the one most people skip because it feels like more effort than it is. Go to NVIDIA, AMD, or Intel's own site (not Windows Update, which lags behind by weeks or months) and download the latest driver directly. NVIDIA's GeForce Experience app or AMD's Adrenalin software will do this automatically if you'd rather not hunt manually.

Say you run a small home office and use your gaming PC in the evenings to unwind. You installed a new game last week and it crashes to desktop within ten seconds of launching, no error message, nothing. Nine times out of ten in my experience talking to people about this, that's a driver mismatch between the game's engine and whatever driver version shipped six months before the game did. A fresh driver install, followed by a restart, clears it.

5. Run Windows Update, then restart twice

Windows Update handles more than security patches. It also ships updated versions of DirectX, Visual C++ runtimes, and.NET frameworks that games depend on silently in the background. Go to Settings, Windows Update, check for updates, install everything offered, then restart. Do it twice, because Windows sometimes needs a second restart to fully apply a cumulative update before it takes effect for games.

6. Check whether an overlay is the culprit

Discord's overlay, Nvidia's GeForce Experience overlay, and Steam's own in-game overlay all inject code into the game process while it's running. Any one of them can cause a crash, particularly straight after a Windows update changes how graphics APIs handshake with third party software. Disable them one at a time: Steam's overlay lives in Settings, In-Game; Discord's is under User Settings, Game Overlay; Nvidia's is inside GeForce Experience settings. Launch the game after disabling each one before moving to the next, so you know which one was responsible rather than guessing.

7. Run Steam and the game as administrator

Right-click the Steam shortcut, Properties, Compatibility tab, tick "Run this program as an administrator." This matters more than people expect on Windows 11 machines where User Account Control is set to a stricter level than default, which blocks a game from writing to its own save folder or registry keys it needs. It's not a habit I'd recommend running permanently, since it does increase what a piece of software can touch on your machine, but it's a legitimate diagnostic step.

8. Whitelist Steam in your antivirus and firewall

Windows Defender and third party antivirus software occasionally flag Steam's own anti-cheat components or a game's executable as suspicious, particularly right after a big update changes the file's signature. Open Windows Security, Virus & Threat Protection, check the Protection History for anything quarantined in the last few days. If you find the game's.exe there, restore it and add an exclusion for your Steam library folder. This is a common cause and one that's easy to miss because there's no obvious error message pointing at it.

9. Check your disk space and drive health

Steam needs headroom beyond the install size itself, usually an extra 5 to 10GB for temporary files during updates and shader compilation. If your drive is down to its last gigabyte, updates silently fail or corrupt partway through. Right-click your drive in File Explorer, Properties, and check free space. If it's a mechanical hard drive rather than an SSD, that alone can cause stuttering and load failures in modern games regardless of anything else on this list, because current titles expect SSD-level read speeds during load screens.

10. Reinstall as the last resort, not the first

If you've worked through everything above and the game still won't launch, uninstall it through Steam's Library menu (not by just deleting the folder, which leaves registry entries behind), restart your PC, then reinstall. This is the slowest fix on the list by a wide margin, and for a large modern game it can eat several hours of download time depending on your connection. Save it for last.

What to do while you wait for downloads or fixes

If a big game is stuck mid-download or mid-reinstall, that's often a good moment to have something lighter queued up so the evening isn't a total write-off. I'd rather point you toward how to choose downloadable PC games without wasting time than have you stare at a progress bar for an hour. And if your internet connection is the problem rather than Steam itself, it's worth keeping a backup list of games that work with zero data so a dodgy connection doesn't end your evening entirely. There's also a solid case for building a small library of games you can play offline specifically for the nights when Steam's servers or your own broadband decide not to cooperate.

A worked example, start to finish

Say you run a small graphic design business from home and use gaming as your wind-down after clients log off. You bought a new open world title on Steam, and the day after a routine Windows update it refuses to launch, the taskbar icon flickers for two seconds then disappears with no error at all.

• You restart Steam fully through Task Manager. No change.
• You check Steam's server status. All green, so it's local.
• You verify integrity of game files. Comes back clean after eight minutes, no files replaced.
• You update your NVIDIA driver directly from NVIDIA's site rather than relying on Windows Update, restart the PC.
• The game launches fine.

Total time from start to fix: roughly 25 minutes, most of it spent waiting on the verify step that turned out not to be the actual cause. That's the realistic pattern. The fix that works is rarely the first one you try, so having a fixed order stops you giving up halfway through.

The bit worth saying plainly

A lot of Steam troubleshooting content online is written to fill a page rather than to help, listing every possible cause with equal weight so nothing gets ranked by likelihood. The truth is that two fixes, a GPU driver update and clearing an antivirus quarantine, solve the vast majority of "game won't launch" problems on Windows. Everything else on this list exists for the smaller remainder of cases, and reinstalling Windows entirely, which some forum threads suggest as a genuine step, is almost never necessary and wastes an entire day for a problem a driver update would have solved in five minutes.

Frequently asked questions

Why does my Steam game say "preparing to launch" and never open?

This usually means the launcher process has hung, most often because an overlay (Discord, GeForce Experience, or Steam's own) is stuck injecting into the game. Disable overlays one at a time and restart Steam fully through Task Manager before trying again.

Do I need to reinstall Windows to fix a Steam game that won't launch?

Almost never. Reinstalling Windows is a last resort that fixes deep system corruption, but the overwhelming majority of Steam launch failures come down to an outdated GPU driver or antivirus quarantine, both of which take minutes to fix rather than a full day.

Why doesn't "verify integrity of game files" fix everything?

It only catches missing or corrupted files against Steam's own records. It won't detect a driver conflict, an antivirus block, or an overlay crash, which together cause more launch failures than corrupted files do, so a clean verify result doesn't mean your system itself is fine.

Should I keep Steam running as administrator permanently?

I wouldn't recommend it as a permanent setting since it gives the software wider access to your system than it strictly needs. Use it as a temporary diagnostic step to see if the problem clears, and switch it back off once you've identified the actual cause.