You've just spent good money on a new game and it flat-out refuses to open. No error code, or a vague one. Just nothing. The thing is, a game won't load in most cases for a handful of well-understood reasons, and you can work through them systematically in under an hour without touching a repair shop. This guide covers every tier, from a two-minute restart to advanced system file repair, in the order that actually saves time.
What Causes a Game Won't Load Problem?
The failure point isn't always where you'd expect. A game won't load for reasons that range from a single corrupt file to a Windows component that's quietly broken in the background. Understanding which category you're in makes the fix faster.
The most common culprit is a bad install. Downloads get interrupted, drives run out of space mid-write, or a shader cache fails to compile. The launcher thinks the game is installed, but one or more critical files are either missing or zero-byte. The game attempts to launch, hits the missing file, and closes silently or throws a generic error. This is why Verify or Repair is always the first real step.
The second category is Windows components. Games on Windows 10 and 11 increasingly depend on the Xbox Gaming Services package, DirectX redistributables, and Visual C++ runtimes. If any of those are outdated or broken, the game won't load regardless of how clean the install is. A Windows update that didn't finish properly can leave these components in a half-installed state that's genuinely tricky to spot.
Third: launcher and cache problems. Steam, the Epic Games Launcher, EA App, and the Xbox app all maintain local caches and service connections. A corrupted cache or a launcher that's stuck in an odd state can block every game it manages, not just the new one. Resetting or repairing the launcher itself often fixes this without touching the game files at all.
And then there's interference. Antivirus software, Discord overlays, GeForce Experience, and various other background apps can intercept a game's launch process. Some security tools quarantine game executables on first run because they look behaviorally unusual. A clean boot strips all of that away so you can see whether the game loads in isolation. If it does, you know the problem is a conflict rather than a corrupt install.
Finally, system file corruption. If Windows' own core files are damaged (from a forced shutdown during an update, a failing drive, or a botched driver install), apps that depend on those files won't launch. SFC and DISM are the tools for this, and they're more effective than most people expect.
Game Won't Load: Quick Fixes to Try First
These take five to ten minutes and clear the majority of cases. Don't skip them to get to the advanced stuff faster. That's almost always a waste of time.
Restart, Update, and Verify Game Files Easy
- Restart your PC fully.
Not sleep, not hibernate. A proper shutdown and restart clears stuck launcher processes, locked file handles, and temporary service states that silently block launches. - Close the launcher completely.
Check the system tray (bottom-right corner) and right-click the launcher icon to Exit or Quit. Just closing the window often leaves it running in the background. - Verify or Repair the game files.
In Steam: right-click the game, Properties, Local Files, Verify integrity of game files. In Epic: three dots next to the game, Manage, Verify. In EA App: three dots, Repair. In Xbox app: find the game in your library, three dots, Manage, Files, Verify and repair. Let it finish completely. - Install pending Windows updates.
Open Settings, Windows Update, Check for updates. Install everything, including optional updates. Restart when prompted. Missing updates can leave DirectX or runtime components behind. - Retest the game.
Launch normally first. If it still fails, try right-clicking the game executable or launcher shortcut and choosing Run as administrator before moving on.
More Game Won't Load Solutions
If the quick fixes didn't sort it, the problem is likely sitting in the launcher itself, a startup conflict, or a Windows setting that's interfering. These steps take fifteen to thirty minutes and have a solid track record on the problems that survive the first tier.
Repair or Reset the Launcher in Windows Settings Easy
- Open Settings and go to Apps.
Press Windows + I, click Apps, then Installed apps. Search for the launcher by name (Steam, Epic Games Launcher, EA, Xbox, etc.). - Open Advanced options.
Click the three dots next to the launcher and choose Advanced options. Not every launcher shows this (Steam doesn't, for example), but the Xbox app, EA App, and Microsoft Store games do. - Click Repair first.
This attempts to fix the app without wiping its data. Wait for it to complete, then relaunch and test the game. - If Repair fails, click Reset.
Reset wipes the app's local state and cache. You'll need to sign back in, but it clears corrupted cache data that Repair sometimes can't touch. This one often needs a second reboot before it sticks.
Disable Fast Startup and Check Account Sign-In Easy
- Turn off Fast Startup.
Open Control Panel (search for it in the Start menu), go to Hardware and Sound, Power Options, then Choose what the power buttons do. Click Change settings that are currently unavailable, uncheck Turn on fast startup, and save changes. Restart the PC. - Sign out and back into the launcher.
Some games validate your licence on launch by checking your account. If the session token has expired or the account is in a weird state, the game won't load even if the files are fine. Sign out, close the launcher fully, reopen it, sign back in, and retry. - Check your system clock.
Open Settings, Time and language, Date and time. Make sure Set time automatically is on. A wrong date or time causes SSL certificate validation failures that can silently block launcher connections and licence checks.
Clean Boot to Isolate Startup Conflicts Medium
- Open msconfig.
Press Windows + R, typemsconfig, press Enter. Go to the Services tab. - Hide Microsoft services and disable the rest.
Check the box that says Hide all Microsoft services, then click Disable all. This leaves Windows' own services running but stops everything third-party. - Disable startup apps.
Go to the Startup tab and click Open Task Manager. Right-click and disable every nonessential startup item (Discord, GeForce Experience, Razer Synapse, RGB software, etc.). - Restart and test the game.
If the game loads in a clean boot environment, a background app is the culprit. Re-enable services and startup items in small batches, restarting each time, until the problem returns. The last batch you enabled contains the conflict.
Overlays are a particularly common offender here. Discord's overlay, the Steam overlay running on a non-Steam game, and GeForce Experience's in-game overlay have all been documented as causing launch failures for specific titles. If you identify an overlay as the conflict, you can usually disable it just for that game rather than removing it entirely. For similar launch conflicts caused by software interference, our guide on Windows apps that won't open covers the same clean boot process in more detail.
Advanced Game Won't Load Fixes
These are the steps for when everything above has failed. They take longer, but they address root causes that the intermediate fixes can't touch: actual Windows file corruption and broken platform components.
Repair Windows System Files with SFC and DISM Hard
- Open Command Prompt as Administrator.
Search forcmdin the Start menu, right-click Command Prompt, and choose Run as administrator. - Run SFC.
Typesfc /scannowand press Enter. This scans protected Windows files and replaces corrupted ones from a local cache. It can take ten to twenty minutes. Do not close the window. According to HowToGeek's breakdown of the process, SFC handles most single-file corruption cases but can fail if the local cache itself is damaged. - Run DISM.
Once SFC finishes, typeDISM /Online /Cleanup-Image /RestoreHealthand press Enter. DISM pulls replacement files directly from Windows Update servers, so it can fix things SFC can't. This one needs an internet connection and can take fifteen to thirty minutes. The Microsoft documentation on DISM image repair explains exactly what it's doing under the hood if you want the detail. - Restart and retest.
Restart the PC after both commands complete. Test the game. If SFC found and fixed corruption, you'll see a message in the output saying it repaired files. If it says it found corruption but couldn't fix it, run DISM first, then SFC again in that order.
Reinstall Gaming Services or Check Event Viewer Hard
- Reinstall Gaming Services (for Xbox and Microsoft Store games).
Open PowerShell as Administrator and runGet-AppxPackage *GamingServices* | Remove-AppxPackage -AllUsers. Then open the Microsoft Store, search for Gaming Services, and reinstall it. This fixes a specific class of launch failure where the game won't load because the underlying Gaming Services component is broken or missing, even though the game itself appears intact. - Check Event Viewer for the faulting module.
Press Windows + X, open Event Viewer. Go to Windows Logs, then Application. Look at the timestamps around when you tried to launch the game. Find the error entry (it'll be marked with a red X). The detail pane shows the faulting application name, faulting module name, and an exception code. That module name tells you exactly what failed: a Visual C++ runtime, a DirectX component, a specific DLL. Search that module name to find the targeted fix. - Reinstall the game to a different drive or folder.
If the install path itself is damaged or the launcher's library metadata is broken, no amount of file verification will fix it. Uninstall the game completely, then reinstall it to a different drive or a fresh folder. Avoid paths with special characters or very long directory names, both of which can cause silent launch failures on some engines.
VCRUNTIME140.dll needs a Visual C++ Redistributable reinstall. One caused by d3d12.dll points to a DirectX issue. They're completely different fixes, and Event Viewer tells you which one you need. For deeper Windows stability problems that affect multiple apps, our guide to Windows crashing and instability covers the Event Viewer workflow in more detail.One more thing on the advanced tier: if the game is an older title (pre-2016 roughly), try compatibility mode. Right-click the game executable, open Properties, go to the Compatibility tab, and check Run this program in compatibility mode for. Try Windows 8 or Windows 7. Some older games use APIs that Windows 11 handles differently, and compatibility mode patches the gaps. It's not a fix you'd reach for on a modern release, but for anything from a back-catalogue sale it's a proper quick win. The Microsoft Windows Update FAQ also covers keeping components current, which matters for older game compatibility more than most people realise.
If the game uses anti-cheat software (Easy Anti-Cheat, BattlEye, Vanguard), check whether that component needs a separate repair or reinstall. Anti-cheat systems install their own kernel-level drivers and can fail independently of the game. Most have a repair executable in the game's installation folder, usually under a subfolder named after the anti-cheat. Running it as administrator often clears these failures without a full reinstall. For anything related to driver-level conflicts, our Windows driver troubleshooting guide has the steps for identifying and fixing problem drivers.
Preventing a Game Won't Load Problem in the Future
Most of these failures are avoidable. The single most effective habit is keeping Windows updated before you install or launch a new game. Gaming components like DirectX, Visual C++ runtimes, and Gaming Services are distributed through Windows Update, and a machine that's several updates behind is missing dependencies that new games assume are present.
Second most important: never force-shutdown the PC during a game install or update. A hard power-off mid-write is the fastest way to corrupt game files. If an install is taking too long, let it finish or cancel it cleanly through the launcher. Partial installs that get interrupted are a reliable source of game won't load problems on the next boot.
Keep enough free disk space. Windows and game launchers need room to write shader caches, patch files, and temporary data during launch. Running a drive below five to ten percent free space causes write failures that can corrupt files silently. It's a bit rubbish when this is the cause because it's entirely avoidable.
A few more habits that make a real difference:
- Add your game folders to your antivirus exclusion list. Trusted paths (Steam\steamapps, Epic Games, EA Games) should be excluded from real-time scanning to stop false-positive quarantines on first launch.
- Create a Windows restore point before major driver or launcher updates. It takes two minutes and gives you a clean rollback point if something breaks.
- Don't move game folders manually outside the launcher. Most launchers store absolute paths in their library metadata. Moving a folder in File Explorer breaks that reference and causes launch failures even though all the files are present.
- Limit startup apps and overlays. The fewer things fighting for resources at launch time, the fewer conflicts you'll see.
Game Won't Load: Summary
A game won't load for a short list of reasons, and they all have fixes. Start with a restart and file verification through the launcher. If that doesn't work, repair the launcher itself in Windows Settings, then do a clean boot to rule out background conflicts. For anything that survives those steps, SFC and DISM repair deeper Windows corruption, and Event Viewer tells you exactly which component failed so you're not guessing. The vast majority of cases where a game won't load are sorted within the first two tiers. The advanced steps exist for the stubborn ones, and they work. Keep Windows updated, don't interrupt installs, and use the launcher's verify feature any time a game starts behaving oddly after a patch.

