Steam: Game Running But Not Opening Fix

Interactive troubleshooting

Fix Progress

Try the steps in order. Open each step, follow the instructions, then mark the step that solved the problem.

0community fixes

What worked for other readers

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Steam can display Running even when no game window is visible because the client has detected an active game-related process. That process may be the main executable, a launcher, an anti-cheat service, a crash reporter, or a frozen child process. The repair depends on which stage failed: window placement, process startup, file loading, or graphics initialization.

Quick Fix

Use Alt+Tab, then press Alt+Enter to test whether the game is open outside the visible desktop or stuck in full-screen mode.
Open Task Manager with Ctrl+Shift+Esc, end only the game-related processes, exit Steam fully, and relaunch once.
Clear every custom Steam launch option and disable the Steam Overlay for that game.
Run Verify integrity of game files under Properties > Installed Files.
Close capture, monitoring, RGB, controller-remapping, overlay, and overclocking tools before the next test.

What “Running But Not Opening” Means

The Steam status confirms that a process associated with the game is still registered. It does not prove that the game created a usable window, initialized its renderer, loaded required runtime libraries, or reached the main menu. A visible process with no window is usually a startup hang, silent crash chain, hidden-window state, or launcher handoff failure.

Find the Relevant Check

What the Status Means
Match the Symptom
Repair Steps
Advanced Checks
Common Questions

Why Steam Says the Game Is Running

Steam tracks the launch state through the process chain started for the selected app. Many games do not move directly from steam.exe to one game window. They may start a publisher launcher, anti-cheat bootstrapper, prerequisite installer, crash handler, or helper executable before the main game process appears.

If one part of that chain remains alive, Steam may keep showing Running or Stop. Valve notes that an “app already running” state often follows an improper close, a silent crash, a failed launch, or a process running under another operating-system account. [✅Source-1]

Process state and window state are separate. A game can consume memory and appear in Task Manager without creating a taskbar button. It can also create a window on a disconnected monitor, fail while switching to exclusive full screen, or wait indefinitely for another launcher component.

Match the Symptom Before Changing Settings

What You Observe	Likely Failure Point	First Check
Game audio plays, but no picture appears	Hidden window, wrong monitor, full-screen transition, HDR, or display mode	Alt+Tab, Alt+Enter, Windows+Shift+Arrow
Game process stays in Task Manager with little CPU or GPU activity	Frozen startup, launcher wait, anti-cheat wait, or blocked dependency	End the full game process chain and relaunch once
Steam changes to Running, then returns to Play within seconds	Startup crash, missing runtime, bad mod, invalid configuration, or driver fault	Verify files and read the newest Application Error event
A publisher launcher opens, but the game does not	Launcher handoff, account session, anti-cheat, or child-process permissions	Close both launchers, remove custom options, and start from Steam
The problem started after changing monitors or resolution	Saved window coordinates or unsupported display configuration	Move the window by keyboard or reset only the display configuration
Only one Steam game is affected	Game files, game-specific runtime, mods, anti-cheat, or local settings	Verify that title, test a clean configuration, then use its support channel
Many games fail in the same way	Graphics driver, overlay, security tool, Windows component, or system instability	Update the system, disable shared hooks, and perform a clean boot

Do not treat one Task Manager reading as proof. A loading screen may briefly show low CPU use, and an idle menu may show little GPU use. Watch the process for 20–30 seconds and note whether memory, CPU, disk, or GPU values change.

Repair Steps in the Safest Order

Recover a Hidden Game Window

Start here when you can hear menu music, see a taskbar preview, or find the game under Alt+Tab. Windows may be drawing the window outside the visible desktop after a monitor was removed, a laptop was undocked, display scaling changed, or the game saved old coordinates.

Press Alt+Tab until the game is active.
Press Windows+Shift+Left Arrow or Windows+Shift+Right Arrow to move it between monitors.
Press Windows+Up Arrow to maximize the active window.
Press Alt+Enter once to switch between full-screen and windowed mode when the game supports that shortcut.
If the game remains invisible, close it and temporarily set Windows to show only the primary display before launching again.

Microsoft documents Alt+Tab for switching between open windows and Windows+Shift+Left/Right Arrow for moving the active window between monitors. [✅Source-2]

Reset Only the Display Configuration

Some games store resolution, monitor number, full-screen mode, and window coordinates in a configuration file under Documents, AppData, Saved Games, or the game’s own profile folder. Do not delete the whole folder. First back it up, then rename only the display or graphics configuration file so the game can create a default copy.

Keep save data separate. Files named save, profile, slot, or progress may contain local game progress. Rename a graphics configuration only when its purpose is clear or the developer identifies it in official support instructions.

End the Full Game Process Chain

A stuck process is the most direct explanation when Steam remains on Running after the game was closed or never produced a window. Press Ctrl+Shift+Esc, expand the game entry, and inspect its child processes. End the game executable and its clearly named launcher or crash reporter. Avoid ending unrelated Windows services.

Next, use Steam > Exit. Wait until Steam disappears from the notification area and Task Manager, then reopen it. If Steam cannot close because the game process is still present, restart Windows. A restart clears process handles, locked files, injected overlays, and pending launcher sessions without altering installed data.

Check Other Windows User Sessions

Steam’s official support notes that the process may be running under another operating-system account. Open Task Manager, select Users, and check whether another signed-in session has the game or launcher open. Sign out that session normally when possible. Do not terminate another user’s active work without saving it.

Clear Launch Options and Temporary Compatibility Flags

Old launch commands can force a renderer, resolution, monitor, language, executable, or debugging mode that no longer matches the current game build. Open the game’s Steam Properties and clear the Launch Options field completely for one test.

Do not stack guessed commands such as -dx11, -dx12, -vulkan, -opengl, and -windowed. Render flags are game-specific. Use one only when the developer documents it for that title. Valve provides the Steam path for adding launch settings used to diagnose video and display problems. [✅Source-3]

A useful test order: launch once with an empty field; test a developer-documented windowed option; test one documented render API; remove the option after the diagnosis. Changing several flags at once hides which setting helped.

Verify the Installed Files

Damaged executable files, incomplete patches, altered libraries, or removed assets can let a process start but stop it before a window appears. In Steam, open Library > right-click the game > Properties > Installed Files > Verify integrity of game files. Steam states that the scan may take several minutes. [✅Source-4]

Verification compares the local installation with the current Steam depot and reacquires files that do not match. It does not automatically fix data stored outside the installation folder, such as a damaged user configuration, mod loader, shader cache, or publisher-launcher profile.

What to Do After Verification

Launch the game before restoring mods or custom files.
Allow a prerequisite installer to finish if Steam starts one.
Recheck antivirus quarantine history if the same executable disappears again.
If verification repeatedly downloads the same file, inspect drive health, permissions, security filtering, and any tool that edits game files.

Disable Overlays, Injectors, and Monitoring Tools

Overlays and monitoring tools attach to a game process to draw counters, capture frames, remap input, apply filters, or read hardware sensors. A conflict can occur before the first frame is displayed. Disable the Steam Overlay for the affected title, then close other software that adds an overlay or hook.

Display and capture

Recording tools, streaming overlays, post-processing filters, screenshot utilities, and frame-rate displays.

Hardware and tuning

GPU overclocking, voltage control, fan control, frame limiting, sensor polling, and RGB control.

Input and access

Controller remappers, macro tools, virtual input drivers, accessibility overlays, and remote-desktop layers.

Valve lists software categories that may interfere with Steam and recommends exiting or disabling the suspected program, restarting Steam, and testing again. Some programs require a Windows restart before their drivers or services are unloaded. [✅Source-5]

Disable one category at a time when possible. If the game starts, re-enable the tools individually until the failure returns. This identifies the conflict without leaving useful software disabled.

Repair the Graphics and Display Path

A game may remain in the background while Direct3D, Vulkan, OpenGL, HDR, a shader cache, or a switchable-GPU decision fails. This is more likely after a graphics driver update, Windows update, monitor change, docking change, or move between integrated and discrete graphics.

Install pending Windows updates and restart.
Install the supported graphics driver from the GPU or computer manufacturer.
On a laptop or hybrid-GPU desktop, open Settings > System > Display > Graphics.
Add the game’s real executable, not only the publisher launcher.
Select Options, test High performance, save, and restart the game.
If the failure started after enabling HDR or windowed-game optimizations, switch that setting off for the affected executable and test again.

Windows 11 allows a per-game GPU preference and a per-app switch for windowed-game optimizations under Graphics settings. Microsoft directs users to restart the game after changing these options. [✅Source-6]

Driver date alone is not enough. A new driver may still be unsuitable for a particular game, while a laptop may require the computer maker’s package for switchable graphics. If the issue began immediately after a driver change, use the manufacturer’s supported rollback method rather than deleting driver files manually.

Repair Visual C++ and Legacy DirectX Components

Many Windows games rely on Microsoft runtime libraries installed beside the game or shared by multiple programs. A process can start and then close before drawing a window when a required runtime is missing, damaged, or the wrong architecture is present.

Visual C++ Runtime Clues

Check the crash entry for names such as VCRUNTIME140.dll, MSVCP140.dll, or another Visual C++ component. Open Settings > Apps > Installed apps, find the matching Microsoft Visual C++ Redistributable packages, and use Modify > Repair when available. A 64-bit Windows installation may need both x64 and x86 packages because many older games remain 32-bit.

Microsoft states that apps built with the Visual Studio 2015, 2017, 2019, and 2022 toolsets use the v14 runtime family and can use a newer supported v14 Redistributable. Download packages only from Microsoft. [✅Source-7]

Legacy DirectX Clues

Modern Windows includes DirectX, but some older games still require optional side-by-side libraries from the legacy DirectX SDK. Microsoft’s DirectX End-User Runtime provides components including D3DX9, D3DX10, D3DX11, XAudio 2.7, XInput 1.3, and XACT without replacing the DirectX version built into Windows. [✅Source-8]

Never download a single missing DLL from an unofficial DLL site. Install or repair the signed runtime package that owns the component. A loose DLL can be the wrong build, wrong architecture, altered, or placed in a path that masks the real dependency problem.

Check Security Blocking Without Removing Protection

Security software may quarantine a modified executable, block an anti-cheat driver, prevent a launcher from creating a child process, or restrict write access to a protected folder. Check protection history and quarantine first. Restore a file only when its location, digital signature, and game source are verified.

Prefer a narrow allow rule for the verified game executable or library folder over disabling protection for the entire PC. Re-enable any temporary setting immediately after the test. If the game works only with protection disabled, update the security product and submit the file to its vendor rather than leaving the system unprotected.

Keep Steam and the Game at the Same Permission Level

A launcher handoff may fail when Steam runs normally but the game executable is forced to run as administrator, or the reverse. Open the executable’s Properties > Compatibility and remove an old forced administrator setting unless the developer requires it. Then launch from Steam.

Avoid applying compatibility mode to every Steam executable. Anti-cheat components and publisher launchers may treat a changed compatibility or elevation state as a different environment. Use such settings only as a targeted test and record what changed.

Advanced Checks When the Basic Repairs Do Not Work

Perform a Clean Boot

A clean boot starts Windows with Microsoft services and a reduced set of startup software, which helps isolate a background conflict. It is different from Safe Mode because the normal Windows desktop and drivers can still load while non-essential startup items are controlled.

Press Windows+R, enter msconfig, and open Services.
Select Hide all Microsoft services before choosing Disable all.
Open the Startup section and launch Task Manager.
Disable enabled startup apps, noting each item you changed.
Restart Windows and test the game.
Restore normal startup after testing. If the game opened, re-enable items in groups until the conflict returns.

Microsoft warns that some functions may be temporarily unavailable in a clean-boot state and provides steps for restoring normal startup after the test. [✅Source-9]

Use Event Viewer to Separate a Crash From a Hang

Open Event Viewer immediately after a failed launch. Go to Windows Logs > Application, sort by time, and inspect entries created at the moment the game was started. The most useful fields are:

Faulting application name: identifies the process that ended.
Faulting module name: points to the executable, runtime, driver, overlay, or system module present at the failure.
Exception code: describes the crash class.
Faulting application path: confirms which copy of the executable ran.
Report ID: helps match related Windows Error Reporting records.

Microsoft identifies Event ID 1000 as the application crash event and notes that Event ID 1001 can appear with Windows Error Reporting. Its examples include 0xc0000022 for access denied, 0xc0000005 for access violation, and 0xc0000374 for heap corruption. [✅Source-10]

Log Result	What It Suggests	Next Targeted Action
Faulting module is the game executable	Game code, configuration, mod, or corrupted game data	Verify files, remove mods, reset only the game configuration, check developer notices
Faulting module names a GPU driver component	Graphics driver or render-path failure	Update or roll back the supported driver, change one documented render API
Faulting module is VCRUNTIME or MSVCP	Visual C++ runtime or a program using it failed	Repair the matching x86/x64 Redistributable and retest cleanly
Exception code is 0xc0000022	Access was denied somewhere in startup	Check security history, folder permissions, elevation mismatch, and anti-cheat status
No crash event; process remains alive	The game may be hung or waiting rather than crashing	Inspect child processes, launcher dialogs, network sign-in, overlays, and clean-boot results

A system DLL in the faulting-module field is not automatic proof that Windows is damaged. Modules such as ntdll.dll, kernel32.dll, and kernelbase.dll are used by many processes and may appear where an earlier error is finally detected. Match the module with the exception code, recent changes, and repeatable test results.

Inspect the Launcher and Anti-Cheat Chain

Games that use a second launcher or anti-cheat service can fail between authentication and game startup. Close Steam and the publisher launcher, then reopen Steam and start the game from the Library. Watch for a sign-in window hidden behind Steam, a browser-based authorization prompt, a prerequisite installer, or an anti-cheat repair dialog.

If Task Manager shows the publisher launcher but never shows the main game executable, repair or update the launcher through its official installer. If the main executable appears and closes, use the game log or Windows crash record instead. These are different failures.

Test Without Mods and Custom Configuration

File verification may restore official game files but leave external mod managers, loaders, plugins, ReShade files, script extenders, and user configuration untouched. Disable the mod manager profile, move third-party files out of the game folder using the mod’s documented removal method, and test a clean launch.

Do not overwrite a modded installation with random files from another PC. Build a reversible test: back up the current configuration, rename the custom folder, launch once, and restore only after the unmodified game works.

Check Storage Only When the Evidence Points There

Repeated verification repairs, read errors, install files that keep changing, or games failing only on one library drive can point to storage or file-system trouble. Check free space, Steam Library folder access, and the drive’s Windows error status. Avoid moving or reinstalling a large game until verification and the system log show that the installation path is part of the failure.

When Reinstalling Is Reasonable

Reinstallation belongs near the end because it does not repair an off-screen window, conflicting overlay, broken shared runtime, GPU selection error, or launcher service conflict. Reinstall the game when all of these are true:

The problem affects one game.
Verification completes but the same game files or installer stage fail repeatedly.
A clean configuration and no-mod test still fail.
The Windows crash record points to the game installation rather than a shared driver or background program.
Local-only saves and configuration files have been backed up.

Before uninstalling Steam itself, test another game. If other games open, a full Steam reinstall is unlikely to be the first useful repair. If many games fail, investigate the shared graphics, runtime, security, and startup layers first. Valve’s general launch guidance also places Windows updates, driver updates, file verification, non-essential software checks, and system requirements ahead of game-specific support. [✅Source-11]

Repairs That Commonly Create More Problems

Do not download DLL files from third-party DLL sites. Repair the owning Microsoft runtime or the game installation.
Do not disable antivirus protection permanently. Check quarantine, use a narrow verified exception, and re-enable protection after testing.
Do not run every Steam component as administrator. Mixed elevation can break launcher handoff and anti-cheat startup.
Do not paste a long list of launch options. Test one documented option at a time.
Do not delete an entire AppData or Documents game folder without a backup. It may contain saves, profiles, screenshots, or control settings.
Do not reinstall Windows for a one-game failure. Use the crash module, clean boot, and unmodified-game test to identify the affected layer.

Information to Collect for Game Support

When the problem remains after a clean test, send the game developer a small, precise record rather than a general “it does not open” report.

Exact game name and Steam App ID, when available
Windows version and build
CPU, GPU, installed RAM, and graphics driver version
Whether the process stays open, closes immediately, or produces audio
Whether Alt+Tab shows a window
Whether file verification replaced anything
Faulting application, module, exception code, and timestamp from Event Viewer
Launcher or anti-cheat message
Result of the no-overlay, no-mod, and clean-boot tests

This separates a visible-window problem from a crash, hang, launcher failure, or blocked dependency and gives support staff a repeatable starting point.

Common Questions About a Steam Game Running but Not Opening

Why Does Steam Say Running When the Game Is Not Visible?

Steam has detected a game-related process, but that process may not have created a visible window. It may be a launcher, anti-cheat component, crash reporter, frozen game executable, or window located on another monitor.

How Do I Stop a Steam Game That Is Stuck on Running?

Open Task Manager with Ctrl+Shift+Esc, expand the game entry, and end the main game process plus any clearly related launcher or crash reporter. Exit Steam fully and reopen it. Restart Windows if the process cannot be ended cleanly.

Can a Steam Game Open Off-Screen?

Yes. Saved monitor coordinates can place the window outside the current desktop after a monitor, dock, resolution, or scaling change. Focus the game with Alt+Tab, then use Windows+Shift+Left Arrow or Right Arrow to move it to another monitor.

Will Verifying Game Files Delete My Saves?

Verification is designed to check installed game files and reacquire files that do not match the Steam depot. Save locations vary by game. Back up local-only saves before wider repairs, especially when configuration or save data is stored inside the installation folder.

Should I Run Steam or the Game as Administrator?

Not as a general repair. Steam, the publisher launcher, anti-cheat, and game should normally use compatible permission levels. A forced administrator setting on only one component can interfere with process handoff. Use elevation only when the developer requires it or as a controlled test.

Why Does the Game Appear in Task Manager but Use No GPU?

The process may be waiting before renderer initialization, frozen during launcher handoff, blocked by a runtime or security check, or using a different GPU. Watch CPU, memory, disk, and child-process activity, then inspect the crash log and Windows Graphics preference.

Does Reinstalling Steam Fix This Problem?

Only when the Steam client itself is damaged or many games fail because of a shared Steam component. Reinstalling Steam does not correct an off-screen game window, graphics driver fault, missing runtime, overlay conflict, or game-specific configuration problem.

What Does Exception Code 0xc0000005 Mean?

It is an access-violation crash class. The code alone does not identify the faulty component. Read the faulting application and module in the same Event Viewer entry, then compare the result with recent driver, mod, runtime, and security changes.

Steam: Game Running But Not Opening Fix – Causes & Steps