Quick answer

When a Steam game flips from Running to Syncing and back to Play with no window, start by verifying installed files in Steam Properties, then launch the game executable directly from File Explorer to expose hidden DLL errors. Check Windows Event Viewer Application logs, repair x64 and x86 VC++ Redistributables, and test without overlays.

Contents

At a glance

Class
Gaming

Provenance

  • Nov 14, 2026Published

You click green Play in your Steam library, the status badge turns blue Running for three seconds, flashes Syncing, and drops right back to Play. No splash screen appears. No crash dialog pops up. Nothing stays in Task Manager.

First, confirm which Steam symptom is sitting in front of you right now.

This guide fixes individual games exiting silently when the Steam client itself is open and responsive — whereas if the Steam client window never appears when you click the desktop icon you should jump to our Steam not opening on Windows 11 guide, and if a game update halts mid-patch with a file-lock warning you need our Steam content file locked fix. Stop reinstalling 90 GB games blind when two quick Windows checks expose the exact crash cause in under two minutes so you only repair the library or hook that broke.

Diagnostic ClueExact Cause It Points ToJump To
Explorer .exe launch pops up VCRUNTIME140.dll, MSVCP140.dll, or xinput1_3.dll missingUninstalled or broken Visual C++ or legacy DirectX June 2010 runtimeStep 3
Explorer .exe or Event Viewer logs exception 0xc000007b32-bit vs 64-bit DLL mismatch or corrupt runtime binaryStep 2 & Step 3
Event Viewer Faulting module name names RTSSHooks64.dll, DiscordHook64.dll, or GameOverlayRenderer64.dllFrame-rate limiter or chat overlay hook crashing DX12 / Vulkan initStep 5
Brand-new install exits in 1 second before creating a folder in Documents\My GamesWindows Security Controlled Folder Access blocking write accessStep 4
Event Viewer or splash points to EasyAntiCheat or BEServiceKernel anti-cheat service or Secure Boot prerequisite failureStep 6
Game opens a black window briefly, then logs DXGI_ERROR_DEVICE_REMOVED or nvlddmkm / amdwddmgCorrupt shader cache or unstable GPU clock/driver stateStep 5

Step 1: Launch the .exe from File Explorer to unmask hidden pop-ups

When Steam launches a game child process, Windows loader dialogs are frequently suppressed behind the client or swallowed when the launcher wrapper exits. Opening the binary straight from Explorer forces Windows to print the raw loader error on screen.

  1. Right-click the broken game in your Steam Library and click Manage -> Browse local files.
  2. Find the main game executable (often inside the root folder or under Binaries\Win64\ on Unreal Engine titles) and double-click it.
  3. Note what happens:
    • A message saying Steam must be running or restarting through Steam is normal for SteamStub DRM games — move straight to Step 2.
    • A dialog naming VCRUNTIME140_1.dll, MSVCP140.dll, d3dx9_43.dll, or XAPOFX1_5.dll was not found hands you the exact missing redistributable on a silver platter (Step 3).
    • A dialog reading The application was unable to start correctly (0xc000007b) means Microsoft’s STATUS_INVALID_IMAGE_FORMAT triggered — almost always a 32-bit DLL sitting where a 64-bit game expects a 64-bit library, or a half-corrupted VC++ install. Never download loose .dll files from random DLL websites and paste them into a game folder; delete any loose runtime DLLs you pasted manually and repair the official Microsoft packages in Step 3.

While you have the game’s Properties menu open, run Valve’s Verify Integrity of Game Files check under Properties, Installed Files, and Verify integrity of game files, and delete anything typed inside General Launch Options so an old -dx11, -vulkan, or broken mod flag does not kill startup before the window initializes.

Step 2: Read the exact crash module in Windows Event Viewer

Every silent Running -> Syncing -> Play crash that reaches user-mode execution leaves a forensic receipt in Windows Event Viewer. I check it before touching drivers. Whenever I troubleshoot a game crash on my own Windows 11 desktop, Event Viewer tells me inside thirty seconds whether Windows rejected a DLL or a third-party overlay hooked the render thread badly.

  1. Right-click the Windows Start button and click Event Viewer (or press Win + R and run eventvwr.msc).
  2. Expand Windows Logs in the left tree and click Application.
  3. Reproduce the Steam launch failure once, then press F5 in Event Viewer to refresh.
  4. Click the newest red Error row marked Source Application Error (Event ID 1000) or informational Windows Error Reporting (Event ID 1001).

Read two lines inside the General tab:

  • Exception code: 0xc0000005 indicates an access violation (commonly overlay hooks, corrupt shader caches, or unstable RAM/GPU clocks); 0xc000007b indicates a 32/64-bit binary format mismatch; 0xe0434352 points to a .NET launcher exception.
  • Faulting module name: If this line names ntdll.dll or the game .exe itself, keep going through Steps 3–5. If it names a third-party DLL — such as RTSSHooks64.dll (RivaTuner Statistics Server), DiscordHook64.dll, OWClient.dll (Overwolf), or an old dxgi.dll / d3d11.dll left behind by ReShade or Special K — you just found the culprit without guessing. Remove that leftover .dll from the game directory or close the hooking app.

Step 3: Repair Steamworks Shared VC++ Redistributables and DirectX

Steam is supposed to run first-time setup scripts automatically, yet interrupted first launches, cloned SSDs, or Windows upgrades routinely leave Visual C++ or legacy DirectX registration half-broken.

As Valve’s Steamworks documentation on Common Redistributables explains, Steam consolidates shared installers inside a separate hidden library depot called Steamworks Shared rather than duplicating _CommonRedist inside every game folder.

Check that exact shared redistributable folder path on your primary Steam drive first.

C:\Program Files (x86)\Steam\steamapps\common\Steamworks Shared\_CommonRedist

Keep secondary NVMe Steam libraries in mind if you split installs across drives.

  1. DirectX legacy libraries (d3dx9, xinput1_3, xaudio2): Open _CommonRedist\DirectX\Jun2010\ and run DXSETUP.exe as Administrator. Windows 11 includes DirectX 12 natively, yet lacks several optional June 2010 helper DLLs that thousands of older and indie Steam titles still link against.
  2. Visual C++ 2015–2022 Redistributables (both architectures): Open _CommonRedist\vcredist\ — or download fresh installers straight from Microsoft’s supported Visual C++ Redistributable page — and run Repair (or Install) on both vc_redist.x64.exe and vc_redist.x86.exe. On 64-bit Windows, 32-bit launchers and older Steam games still require the x86 runtime alongside x64, and repairing both clears corrupt side-by-side DLL state cleanly. Reboot Windows once after repairing VC++.

Step 4: Check Windows Security Controlled Folder Access and Smart App Control

Many games write an initial configuration file and shader directory into %USERPROFILE%\Documents\My Games\ or Documents\ during the first half-second of startup, and poorly coded engines crash straight to desktop without an error handler if Windows denies CreateFile access there.

If you enabled ransomware folder protection in Windows Security, Microsoft’s Controlled Folder Access guards Documents by default and quietly blocks unrecognized game executables:

  1. Open Windows Security -> Virus & threat protection -> Protection history.
  2. Look for a recent Protected folder access blocked entry matching the timestamp you clicked Play. If present, click it and allow the game executable through Controlled Folder Access.
  3. On newer clean installs of Windows 11, also check App & browser control -> Smart App Control settings. Per Microsoft’s Smart App Control documentation, unsigned indie helpers, older launchers, or mod DLLs can be blocked before execution when Smart App Control is set to On.

Also verify you never ticked Run this program as an administrator on the game .exe’s Compatibility tab unless a legacy guide proved it necessary, because forcing Administrator elevation on only the child .exe while Steam runs unelevated breaks Steamworks IPC handshakes and overlay initialization on several modern engines.

Step 5: Strip overlay hooks and clear corrupt shader caches

DirectX 12 and Vulkan games compile pipeline state caches on first launch and crash immediately on subsequent launches if an interrupted driver update corrupted that cache or an OSD hook intercepts the swapchain badly.

  • Clear Steam’s shader cache: Open Steam -> Settings -> Downloads (or the Shader Pre-Caching tab where applicable), toggle shader pre-caching off and back on, or delete the game’s numeric AppID folder inside steamapps\shadercache\<AppID>\.
  • Pause every graphics hook for one clean test: Valve’s interfering-programs list flags OSD and injection tools first. Fully exit RivaTuner Statistics Server (RTSS) / MSI Afterburner, disable Discord In-Game Overlay, disable NVIDIA App / GeForce Experience Overlay or AMD Radeon Overlay, and toggle Enable the Steam Overlay while in-game off in the game’s Steam Properties for one test boot.
  • Check for GPU device-hung resets: If the screen flashes black once before returning to Play and Event Viewer’s System log shows Display warning 4101, work through our DXGI_ERROR_DEVICE_REMOVED fix guide.

Step 6: Multiplayer titles — repair Easy Anti-Cheat or BattlEye

Competitive multiplayer titles such as Apex Legends, Elden Ring, DayZ, ARK, and Rainbow Six spawn an anti-cheat bootstrapper before the game executable ever runs. If that anti-cheat service fails signature verification or misses UEFI Secure Boot, the bootstrapper exits silently and Steam flips straight from Running back to Play.

Check the game’s installation folder for an EasyAntiCheat or BattlEye subfolder:

Frequently asked questions

Why does my Steam game say Running, then Syncing, then go back to Play?
Steam marks a game Running the instant it spawns the child executable, then runs Cloud Sync the moment that child process exits. When the button flips back to green Play within two to five seconds without ever drawing a window, the game executable crashed during early initialization — typically from a missing VC++ or DirectX DLL, a 0xC000007B bitness mismatch, Controlled Folder Access blocking save-folder creation, an anti-cheat failure, or a graphics overlay hook.
Why doesn’t Steam show an error box when a game fails to start?
Launching through the Steam library suppresses certain Windows loader pop-ups or closes helper launchers silently when the child process terminates with an exception code. Double-clicking the game’s .exe directly inside File Explorer (or inspecting Windows Logs -> Application in Event Viewer) reveals the exact missing DLL or exception code that Steam hid.
What causes error 0xc000007b when launching a Steam game from Explorer?
Microsoft defines NTSTATUS 0xC000007B as STATUS_INVALID_IMAGE_FORMAT. On 64-bit Windows 11, it almost always means a 64-bit game tried to load a 32-bit DLL (or a corrupted runtime DLL) that someone manually dropped into the game folder or System32, or a broken Visual C++ / DirectX runtime installation.
Where did the _CommonRedist folder go inside Steam game directories?
Valve moved shared Visual C++ Redistributables, DirectX June 2010 runtimes, .NET, and OpenAL installers out of individual game folders into a single shared depot named Steamworks Shared (steamapps\common\Steamworks Shared_CommonRedist) so Steam does not download duplicate installers for every title.
Can Windows Security block a Steam game without showing a virus alert?
Yes, in two non-malware ways. Windows Defender Controlled Folder Access routinely blocks newly installed games from creating their initial config or save directory inside Documents, causing an immediate silent exit on boot. Windows 11 Smart App Control can also block unsigned helper executables, mod loaders, or older game launchers.

Sources and corrections

Last updated
Methodology
See our methodology for research and review standards. It draws on 7 cited sources, listed below, each checked against the original page on the date above. Diagnostic order and operating-system error codes verified November 14, 2026 against Valve Steam Support documentation, Valve Steamworks Partner documentation on shared redistributables, and Microsoft Learn documentation for Visual C++ Redistributables, NTSTATUS 0xC000007B, Controlled Folder Access, and Smart App Control.
Corrections
Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.

About the author

Written by Lowell K. Wood IV, who builds and runs TechFuelHQ from St. Louis, Missouri.