WARDOGS won’t launch: fixing error codes WD-L004 to WD-L020

Since the Early Access launch on 10 September 2026, many players report that WARDOGS closes right after the splash screen with an error code. The codes start with WD-L and a number such as WD-L004, WD-L006, WD-L007, WD-L010, WD-L014 or WD-L020, followed by a longer string. That string is generated on your machine and does not help with troubleshooting. Publisher Team17’s support team has pinned a thread in the Steam “Report a Problem” forum with a list of steps for these codes. We compared it with community feedback and put it into a sensible order. Status: 19 September 2026.

What the WD-L codes mean

There is no official meaning for the individual numbers. Support treats all codes the same and first asks for a DxDiag file. What the reports have in common is that the launch fails at the anti-cheat module. WARDOGS installs an “Elytra” subfolder in the game directory with its own driver that has to load at startup. Messages such as “The anti-cheat service refused the game executable” or a crash dialog that closes immediately belong to the same family of problems.

Before changing Windows settings, check two simple causes: is a Steam update still installing? Is a WARDOGS, launcher or Elytra process still running in the background? Both show up in Task Manager; end the processes and start the game again.

Step 1: Verify game files and repair Elytra

This is Team17’s official starting point.

• Steam: right-click WARDOGS, Properties, Installed Files, “Verify integrity of game files”.
• In the same menu choose “Browse local files” and open the “Elytra” folder.
• Run the Elytra setup file there and choose “Repair”.
• Restart the PC, not just Steam.

Several players with WD-L014 report that this combination is enough. Others write that the repair alone did not help; in that case continue with the next steps.

Step 2: Check your Windows build

A striking number of WD-L020 reports from mid-September came from machines on Windows Insider builds and fresh preview updates. First run “winver” to check whether your Windows is an Insider build.

• Insider Program: Settings, Windows Update, Windows Insider Program, “Unenroll this device from getting preview builds”, then restart. One user then did a clean install of Windows 11 25H2 from the official ISO.
• Preview updates: individual players report that removing KB5124115 or KB5124010 (Windows Update, Update history, Uninstall updates) restored the launch. The pinned thread also mentions KB5121003.
• Conversely, installing pending security updates was what fixed it for other players.

An uninstalled security update weakens the protection of your system. Treat it as a temporary measure and reinstall the update as soon as a WARDOGS or Elytra patch resolves the problem.

Step 3: Rule out conflicts with other software

A kernel-level anti-cheat is sensitive to other programs that reach deep into the system. The community specifically names:

• Other anti-cheat services such as Riot Vanguard or FACEIT: close them before launching or uninstall them for a test.
• VPN clients and packet filtering tools; the thread explicitly mentions Cisco services.
• Razer Synapse: end all Razer processes in Task Manager, launch the game, then reopen it.
• Input methods such as Sogou IME that inject a DLL into every process; switch to Microsoft Pinyin.
• Disable the Steam, Discord, NVIDIA, AMD and Xbox Game Bar overlays.
• A still-installed “WARDOGS Playtest” from the beta: uninstall it.
• Antivirus and firewall: add WARDOGS and Elytra as exceptions.

Team17 also advises temporarily switching off virtualisation features such as Hyper-V, Windows Sandbox and WSL2, and testing via a mobile hotspot to rule out your home network as the cause.

Step 4: Core isolation and Memory Integrity

Team17 lists turning off Memory Integrity as a further step: Windows Security, Device security, Core isolation details, Memory Integrity off, restart. We recommend this only as a test: the feature protects your system against manipulated drivers. If it makes no difference, switch it back on straight away. Many players also tried Secure Boot; in the WD-L014 thread it helped a few users, others report no effect.

Step 5: Drivers and system files

• Download the graphics driver directly from NVIDIA or AMD, not via Windows Update.
• As administrator in Command Prompt, run “sfc /scannow” and then “dism /online /cleanup-image /restorehealth”.
• Switch off CPU and GPU overclocking for the test; Team17 additionally recommends a 60 FPS cap.
• Launch Steam itself as administrator once and clear the download cache (Steam, Settings, Downloads).

If nothing helps: contact support

Document what you have already tried and create a DxDiag file: Windows key, type “dxdiag”, “Save All Information”. Upload the text to a service such as Pastebin and post the link in the Steam “Report a Problem” forum or through Team17 support. Support usually replies within a day and typically asks for a driver update and an sfc check. Several players confirmed that further launch problems were fixed after the hotfix on 10 September and Patch 0.11 on 14 September, so a new client patch can also solve the problem without any action on your part.

Our short checklist

• Steam update finished, all WARDOGS and Elytra processes closed.
• Game files verified, Elytra repaired, PC restarted.
• No Insider build; problematic preview updates removed or pending updates installed.
• Vanguard, VPN, Razer Synapse, overlays and old playtest install ruled out.
• Memory Integrity off only as a test, then back on.
• Vendor drivers, sfc and DISM, overclocking off.
• DxDiag to support if the code remains.