Skip to content
← All errors

Crash on launch

WARDOGS crashes on launch with no error

Published Updated Data as of Season 1 · 10 Sept 2026

This one is on your machine

Almost always an overlay, an anti-cheat conflict or a stale shader cache rather than your hardware.

What you see

The game closes instantly at startup. Either nothing at all happens, or a crash dump appears before you ever reach the main menu.

Also reported as: wardogs won't start · crash before menu · crash to desktop on startup · streamline · dlss crash

Fixes, in the order worth trying

Work top to bottom and stop when the game launches. Each step is labelled with how much evidence sits behind it, so you can skip the guesses if the first ones work.

  1. 01 Close MSI Afterburner, RTSS and every overlay

    Confirmed

    Afterburner and RivaTuner are the two most-reported culprits. Also switch off the AMD or NVIDIA in-game overlay from the driver control panel, not just from the game.

  2. 02 Delete the EasyAntiCheat folder, then verify game files

    Confirmed

    It is in your install directory. Steam rebuilds it during the verify pass.

  3. 03 Add your Steam and WARDOGS folders to Defender exclusions

    Reported

    Windows Security → Virus & threat protection → Manage settings → Exclusions.

  4. 04 Update your GPU driver, cleanly

    Reported

    A clean install matters more than the version. Display Driver Uninstaller in safe mode, then the current driver.

  5. 05 Run sfc /scannow and DISM, then install the latest Visual C++ redistributables

    Reported

    Open an admin terminal, run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, and reboot between the two.

  6. 06 Turn off DLSS, FSR, NIS and frame generation at driver level

    Reported

    Not in the game menu — in the NVIDIA app or AMD Adrenalin, where a global override outlives a reinstall. On AMD, switching FSR off was the only thing that worked for several people.

  7. 07 Disable Smart App Control and Hardware-Accelerated GPU Scheduling

    Reported

    Both need a restart to actually take effect, so reboot before deciding whether it worked.

  8. 08 If you are on the Windows 11 Insider channel, go back to stable 25H2

    Reported

    Insider builds are over-represented in launch crash reports by a wide margin.

Did this fix it for you?

Notes from other players who hit this code. Say what worked, what did not, and which region you are in — a fix that only works in one place is worth knowing about. Best-rated first, and there is no time limit: an answer from the first beta is still an answer.

No comments yet. Be the first to say whether this worked.

Work these in order. The first two account for most cases, and they are also the two that cost you nothing if they turn out not to be the problem.

If the game crashes but you do get a named module in the dump — platformcore.dll or kernelbase.dll — go to that page instead. Those have specific fixes and this general list will waste your time.

And check that it is a crash at all. If no game window ever appears and the launcher stops with Unable to launch WARDOGS. Error code: WD-L0xx, nothing here applies — that is the launcher failing before the game starts, and the WD-L codes have their own page.

On a laptop, check which GPU the game is actually using

A laptop with both an integrated Radeon and a discrete NVIDIA card is the configuration behind one of the uglier reports on this fault: a black screen on the first launch that needed a hard shutdown, and on the second, a crash whose dump named Unreal's DirectX 12 renderer — D3D12RHI, D3D12Viewport, error 0x80004004 — rather than any file belonging to WARDOGS.

A crash in the renderer on a hybrid-graphics machine usually means the game started on the integrated chip. Windows Settings → System → Display → Graphics, find WARDOGS, Options, High performance. Then update the discrete card's driver from the vendor rather than through Windows Update, and reboot.

If you are still on Windows 10, check the build as well. The DirectX 12 path Unreal Engine 5 uses needs version 1909 or newer, and a machine that has sat on an older build will fail here with hardware that is otherwise well inside the requirements.

Source

WARDOGS Discord, #beta-fixes ↗

If that did not do it