When a game launches, shows a brief flash of a window or black screen, and then vanishes back to the desktop within seconds, that specific timing tells you a lot. In Unreal Engine 5 titles, this symptom almost always means the engine failed during its initialization sequence — somewhere between loading the .uplugin manifests, compiling or validating shaders, and creating the DX12 or Vulkan swap chain. The game never reaches the main menu renderer, which is why you see no splash screen fade, no menu music, and no crash dialog in many cases. You get the process appear in Task Manager, then disappear within two to eight seconds.
- Likely Causes
- Fix 1: Launch via Executable Instead of Epic Games Launcher
- Fix 2: Delete the Shader Cache Directory
- Fix 3: Update or Clean-Reinstall GPU Drivers
- Fix 4: Disable Antivirus Real-Time Protection for the Game Folder
- Fix 5: Remove Mods and Custom DLLs from the Game Root
- Fix 6: Delete or Rename the User Config Files
- Fix 7: Increase Virtual Memory or Check for RAM Exhaustion
- Fix 8: Verify and Repair Game Files Through the Launcher
- Fix 9: Disable Fullscreen Optimizations and Compatibility Mode
- If Nothing Works
- FAQ
Unlike a crash to desktop that happens during gameplay, an instant-close usually involves one of three subsystems failing: the GPU driver interface, the shader cache validation pass, or a mod/plugin loading before the game logic. Understanding which subsystem broke saves you from blindly reinstalling 80 GB of game data.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Corrupted or stale shader cache in the engine’s saved directory | Check %LOCALAPPDATA%\\[GameName]\\Saved\\ShaderCacheData\\ for recent .ushaderbytecode files; log contains “Failed to load shader” or “Invalid shader” |
Easy |
| DX12 device creation failure from outdated or conflicted drivers | Event Viewer shows kernel-PnP or display driver errors at launch timestamp; log reads “DX12: Failed to create device” | Easy to Moderate |
| Epic Games Launcher overriding game-specific config or forcing DX12 on incompatible hardware | Game runs fine when launched via .exe directly but not through Epic | Easy |
| Mod or plugin injecting during engine init (UE4SS, generic DLL mods) | File Engine\\Binaries\\Win64\\d3d11.dll or version.dll exists in game root; log shows “Loaded plugin” entries before crash |
Moderate |
| Antivirus or Windows Defender quarantining the executable or a DLL | Windows Security protection history shows blocked items matching the game folder; log abruptly ends mid-read | Moderate |
| Memory or VRAM insufficient for shader precompilation step | System has 16 GB RAM with integrated or low-VRAM discrete GPU; log stops at “Compiling shaders” without error | Moderate |
Fix 1: Launch via Executable Instead of Epic Games Launcher
How to check
Navigate to the game’s installation folder, typically C:\\Program Files\\Epic Games\\[GameFolder]\\[ProjectName]\\Binaries\\Win64\\[ProjectName].exe. Right-click the .exe and select Run as administrator. If the game reaches its main menu when launched this way but closes immediately when you press Play in Epic, the launcher is injecting an incompatible setting or passing a bad command line argument.
What to do
Create a desktop shortcut to the .exe. Open Epic Games Launcher, go to Settings, scroll to the game’s entry, and uncheck “Run with admin privileges” if enabled. Also try adding -dx11 to the shortcut’s Target line if the game supports fallback. For UE5 games that require DX12, this will not help, but some titles ship both renderers. Check the game’s README or Steam/Epic description for renderer options.
How to undo it
Remove the shortcut and relaunch from Epic. The executable shortcut causes no lasting changes to the installation.
Fix 2: Delete the Shader Cache Directory
How to check
Open File Explorer and paste %LOCALAPPDATA%\\[GameName]\\Saved\\ShaderCacheData\\ into the address bar. If this folder exists and contains multiple .ushaderbytecode files totaling hundreds of megabytes, a corrupted entry is likely causing the engine to hang or fault during the shader validation pass that occurs before the renderer initializes.
What to do
Close the game and Epic Launcher entirely. Delete the entire ShaderCacheData folder. Also delete %LOCALAPPDATA%\\[GameName]\\Saved\\Config\\Windows\\ if you want a fully clean config reset (note: this removes your keybindings and graphics settings). Relaunch the game. Expect a longer initial load as shaders recompile.
How to undo it
No undo needed. The engine regenerates the cache automatically on first successful launch.
Fix 3: Update or Clean-Reinstall GPU Drivers
How to check
Open Device Manager, expand Display adapters, and check the driver version against the latest available from NVIDIA (GeForce Experience or NVIDIA App) or AMD (Adrenalin). For a more targeted check, open Event Viewer, go to Windows Logs, System, and look for entries from the source “nvlddmkm” or “amdkmdag” at the same timestamp as your failed launch. These indicate the driver crashed while the game was requesting a device context.
What to do
If the driver is more than two months old, update it. If you recently updated and the problem started, perform a clean install using DDU (Display Driver Uninstaller) in Safe Mode, then install the previous known-good driver version. For NVIDIA, the Studio driver branch often resolves stability issues that the Game Ready branch introduces for UE5 titles.
How to undo it
Run DDU in Safe Mode again and reinstall the driver version you prefer. DDU leaves no residual state beyond the driver store.
Fix 4: Disable Antivirus Real-Time Protection for the Game Folder
How to check
Open Windows Security, go to Virus and threat protection, then Protection history. Look for items blocked within the last few minutes of your launch attempt. Also check third-party AV quarantine logs. A UE5 executable with embedded .pak files can trigger heuristic detection based on the packing method.
What to do
Add the entire game installation folder to your antivirus exclusion list. For Windows Defender: Virus and threat protection, Manage settings, Add or remove exclusions, add the folder. For third-party AV, consult that product’s documentation. Do not add exclusions for entire drive letters.
How to undo it
Remove the exclusion from the list. The game files are not modified by this step.
Fix 5: Remove Mods and Custom DLLs from the Game Root
How to check
Navigate to the game’s root folder and its Engine\\Binaries\\Win64\\ subfolder. Look for files that do not belong to the base game: d3d11.dll, d3d9.dll, version.dll, winhttp.dll, UE4SS.dll, xinput1_3.dll, or a Mods\\ folder. Open the engine log at %LOCALAPPDATA%\\[GameName]\\Saved\\Logs\\[GameName].log and search for “Plugin” or “Loaded” near the top. A mod that fails to initialize will halt the engine before the game menu appears.
What to do
Move all suspicious DLLs to a separate folder outside the game directory. Delete or relocate the Mods folder if present. Launch the game. If it starts, reintroduce mods one at a time to identify the culprit.
How to undo it
Copy the DLLs and Mods folder back to their original locations. Verify file integrity through Epic’s launcher to restore any game files the mod installer may have overwritten.
Fix 6: Delete or Rename the User Config Files
How to check
Open %LOCALAPPDATA%\\[GameName]\\Saved\\Config\\Windows\\. Look for GameUserSettings.ini, Engine.ini, and [ProjectName]Game.ini. If any of these reference a resolution, refresh rate, or rendering feature your GPU does not support (for example, a 4K setting on a 1080p panel, or ray tracing enabled on a card without RT cores), the engine will fault when applying them during init.
What to do
Rename the entire Config folder to Config_backup. Launch the game. The engine generates fresh defaults. If the game starts, copy individual settings from the backup file to the new one until you identify the offending entry.
How to undo it
Delete the newly generated Config folder and rename Config_backup back to Config. All your previous settings are preserved in the backup.
Fix 7: Increase Virtual Memory or Check for RAM Exhaustion
How to check
During a launch attempt, open Task Manager and watch the Memory column. If it spikes to 95% or higher before the game closes, you are hitting a physical memory limit. UE5 titles with large open worlds (typically 60 GB+) require a minimum of 16 GB system RAM, and 32 GB is the practical comfortable amount in 2026. Also check for VRAM exhaustion on cards with 8 GB or less if the game is configured for Ultra textures.
What to do
Set Windows virtual memory to system-managed if you have it locked to a fixed small value. On System, go to About, Advanced system settings, Performance Settings, Advanced tab, Virtual memory. Ensure your page file is on your fastest drive (NVMe SSD preferred) and sized at 1.5x your physical RAM minimum. Close background applications that consume RAM (Chrome with many tabs, video editing software, other game overlays).
How to undo it
Revert virtual memory settings to your previous configuration. No game files are touched.
Fix 8: Verify and Repair Game Files Through the Launcher
How to check
If the log file at Saved\\Logs\\ ends abruptly with a line mentioning a missing asset path like Failed to find object '/Game/Maps/LevelName' or Invalid package file, a .pak file is corrupted or missing.
What to do
Open Epic Games Launcher, go to Library, click the three-dot menu on the game tile, select Manage, then click Verify. This checks file hashes against the server manifest. For Steam-based UE5 titles, right-click in Library, Properties, Installed Files, Verify integrity of game files. The process may take several minutes for large titles. Do not cancel mid-verification.
How to undo it
Verification is a read-and-replace operation. It restores missing files and corrects corrupted ones. There is nothing to undo unless you had intentionally modified game files, in which case verify overwrites them.
Fix 9: Disable Fullscreen Optimizations and Compatibility Mode
How to check
Right-click the game’s .exe, select Properties, then Compatibility tab. If “Disable fullscreen optimizations” is unchecked, Windows may be compositing the DX12 swap chain in a way that conflicts with the engine’s frame presentation logic, causing a silent failure at the present call.
What to do
Check the “Disable fullscreen optimizations” box. Also try running the executable in Windows 10 compatibility mode if the game was tested against that API level. Apply and relaunch.
How to undo it
Open the same Properties dialog and uncheck the options. These are per-executable registry entries stored under HKEY_CURRENT_USER\\Software\\Microsoft\\Windows NT\\CurrentVersion\\AppCompatFlags\\Layers and can be removed with a single click.
If Nothing Works
Open the full engine log at %LOCALAPPDATA%\\[GameName]\\Saved\\Logs\\[GameName].log and read the last 30 lines before the file ends. The error string immediately preceding the cutoff tells you which subsystem failed. A line containing “Fatal error” followed by a module name (such as UE5Game.dll or NVAPI.dll) identifies the component. Post that line and your hardware specs on the game’s official support forum or the Unreal Engine AnswerHub. Hardware-level faults — a failing GPU, unstable overclock, or insufficient PSU power — can also produce this symptom under shader compile load, so stress-test with OCCT or FurMark to rule them out.
FAQ
Does this always mean my GPU is dying?
No. The vast majority of instant-close cases resolve with a shader cache deletion or driver reinstall. GPU failure typically produces additional symptoms like visual artifacts during gameplay, system-wide display driver resets, or crashes in multiple applications simultaneously.
Why does the game work fine when I launch the .exe directly but not through Epic?
Epic passes command-line arguments and sometimes overrides engine ini settings at launch. If the launcher is forcing a specific renderer, resolution, or graphics feature that your hardware does not support, the game will fail at the device-creation step before any UI appears.
How long should shader recompilation take on first launch after clearing the cache?
For a large UE5 title on a modern GPU with an NVMe SSD, expect five to twenty minutes depending on the game’s shader complexity and whether it uses Nanite. During this time the screen may remain black or show a progress indicator. If the process ends without completing and the game closes, the issue is not cache staleness but an underlying hardware or driver problem.
Can a Windows Update cause this symptom to appear suddenly?
Yes. A cumulative update can replace or alter the D3D12 runtime component, the Windows display driver model, or the DX12 Agility SDK headers that the game loads at init. If the problem started immediately after a patch cycle, check Event Viewer for kernel or D3D-related errors at that timestamp and consider rolling back the specific update through Settings, Windows Update, Update history, Uninstall updates.
