If WARDOGS closes immediately with "Unable to launch WARDOGS. Error code: WD-L014" followed by a hyphen and a string of characters, you have hit the L-series launch failure. The trailing string is a per-attempt identifier, so yours will not match anyone else's and that difference means nothing.
This is an acknowledged problem, not a misconfiguration on your side. Team17 has publicly confirmed it is aware of launch crashes across WD-L006, WD-L014, WD-L004, WD-L020, WD-L010 and WD-L007 "and more", and stated that all of these crash errors are under investigation.
What the developers have confirmed
The statement comes from Team17_Assist, posting under a developer tag on the official Steam discussions. It names six codes explicitly — L006, L014, L004, L020, L010 and L007 — says the list is not exhaustive, and confirms that all of them are being investigated together.
Grouping them matters for how you should read your own code. People spend a long time hunting for what separates WD-L014 from WD-L006; the developers are treating them as one family of launch crashes, so a fix for one is likely to be a fix for the others.
No root cause and no fix date has been published. What exists is an acknowledgement and a recommended sequence of checks, reproduced below.
No root cause has been published for the L-series. Anyone presenting a single guaranteed fix is guessing — including the popular anti-cheat repair, which works for some players and not others.
The order Team17 recommends
This is the developers' own sequence, in their order. Work down it and stop when the game launches — running every step at once leaves you unable to tell which one mattered.
- 1 — Verify your game files through Steam: Properties, then Installed Files, then Verify integrity of game files.
- 2 — Update your GPU drivers from NVIDIA or AMD directly rather than through a utility.
- 3 — Restart your PC after completing the first two steps.
- 4 — Try a mobile hotspot, which rules out your network path and any local filtering.
- 5 — If you are on a Windows Insider build, disable preview builds.
- 6 — Disable virtualization features: Hyper-V, Windows Sandbox, WSL2 and Virtual Machine Platform.
- 7 — Disable any overclocking, on the CPU, GPU and memory alike.
- 8 — Disable the Intel integrated GPU in Device Manager.
- 9 — Allow the game through your antivirus and Windows Defender.
Why virtualization and overclocking appear on an official list
Steps six through eight look unrelated to a game that will not open, and they are the ones people skip. They are there because WARDOGS loads Elytra, a kernel-level anti-cheat, before the game itself starts.
A kernel driver has to be satisfied about the machine it is loading into. Hyper-V and the other virtualization features change how the kernel is presented, an unstable overclock makes early initialisation fail in ways that look nothing like a normal crash, and a second GPU can leave the driver binding to the wrong adapter.
This also explains the shape of the failure. You are not seeing the game crash — you are seeing it never reach the point of starting, because the layer beneath it refused to come up.
The Elytra repair, and an honest note about it
The most widely circulated community fix is to repair the anti-cheat directly. Open your Steam library folder, go to steamapps\common\wardogs\elytra, run Elytra-Setup.exe, choose Repair, then verify your game files and restart.
It is worth trying and it costs a few minutes. But the thread it comes from shows players reporting immediately afterwards that it did not work for them, so treat it as one candidate rather than the answer. If it fails for you, that is a known outcome and not a sign you performed it incorrectly.
Older advice tells you to delete an EasyAntiCheat folder first. That applied to the beta builds; the Early Access build ships Elytra instead, so there is nothing to delete.
When to stop troubleshooting and open a ticket
If you have worked through the official list and the game still will not start, further changes to your machine are unlikely to help and you are now contributing useful data by reporting it.
Team17 asks for DxDiag output with the report. Press Windows and R, run dxdiag, choose Save All Information, and attach the text file it produces along with your full error code including the trailing characters.
Submit it through the Team17 support portal. The per-attempt identifier on your error is the part that lets them locate your specific crash, so include it verbatim.
This is not the same as the other launch errors
An L-series code stops you before the game opens at all. That distinguishes it from every other failure people hit during the launch period, and it changes which fixes are even relevant.
If you reached a menu, a queue or a server browser, you do not have this problem and the steps on this page will not help you.
| What happens | Which fault it is |
|---|---|
| Game never opens, WD-L code shown | This L-series launch failure |
| Game opens, then fails at login with 1147405308 | Failed to authenticate with online services |
| Game opens, you wait with a queue position | The login queue |
| You reach the browser but cannot enter, code 1628505091 | Join timed out |
| You were playing, then thrown out | Removed from the match |
Launch failure questions answered
Short answers for the variations that bring people to this page.
- What does WD-L014 mean? — It is one of the L-series launch crash codes. Team17 has not published a root cause for it.
- Why is my code different from everyone else's? — The characters after the code are a per-attempt identifier. Only the WD-L part identifies the fault.
- Is WD-L006 a different problem from WD-L014? — The developers are investigating the whole L-series together as one family.
- Has it been fixed? — No fix has been announced. Team17 has confirmed only that it is investigating.
- Does repairing Elytra fix it? — Sometimes. Players report both success and failure with it, so try it but do not rely on it.
- Do I need to reinstall? — Verify your files first. A full reinstall does more work for the same result.
- What should I send to support? — Your DxDiag output and the complete error code including the trailing characters.