Why won’t WARDOGS launch or connect?

2 October: the scheduled hotfix hour passed without a visible recovery post

BULKHEAD scheduled a hotfix for 08:00 UTC on 2 October to address minor security and stability issues affecting some players, with one hour of expected downtime. At 09:38 UTC, the complete Steam News feed and public @WARDOGSUpdates timeline still showed no start or recovery notice. That absence cannot diagnose a launch or connection failure and does not establish live service health; the notice names no error code, symptom, build, platform or region.

Read the hotfix scope and status boundaries →

25 September: services returning after security maintenance

WARDOGS Updates scheduled services offline from 11:00 UTC for around one hour while a small number of security updates were deployed. At 11:42 UTC, it said services were coming back online. No patch number, client download or technical security detail was published. If you were unable to connect during that window, wait for the service recovery before changing local files; the post does not announce a client-side fix.

Read the official recovery update →

24 September: non-EU services report network disruption

At 21:36 UTC, WARDOGS Updates said services were experiencing network disruption outside the EU, primarily in North America, and warned of connection issues while mitigation was underway. It published no cause, affected component, workaround or ETA. No dedicated recovery was visible at 00:46 UTC on 25 September. The later security-maintenance recovery does not say whether it closes this separate regional incident.

Read the official disruption notice →

24 September: an incorrect Steam build briefly affected the queue

At 09:18 UTC, WARDOGS Updates said an incorrect build pushed that morning had affected a small number of players. Anyone still in the queue was told to close the game and redownload it through Steam; the stated download was approximately 16 GB. At 09:29 UTC, the account marked the incident resolved. That instruction belongs to that eleven-minute incident window: the post does not establish a normal patch size, a new 16 GB requirement or a fix for WD-L020.

Read the official resolution →

Update 0.1.2 fixes the recent KB5124010-linked WD-L020 crash

BULKHEAD's 30 September Update 0.1.2 notes say the recent WD-L020 crash caused by Windows 11 preview update KB5124010 is fixed. That supersedes the earlier wait-for-a-fix status and makes updating WARDOGS through Steam the first step. Team17's older rollback path remains optional, at the player's own risk, and cannot explain WD-L020 reports made before KB5124010 existed.

WD-L020: the fix, boundaries and historical rollback warning →

Your error code is shorter than you think

The launch-day string is “Unable to launch WARDOGS. Error code: WD-L014-8725400ca4fe”, and searching that whole line finds nothing, because the tail is not part of the code. Four threads opened around 10 September carry four different tails on the same prefix — 8725400ca4fe, d6569f0f455f, 474eb079e144 and 92aaf20d6e21 — and one player reports the tail changing on every attempt while nothing else did. So the code is WD-L014; the hex after it identifies your attempt, which is what the message means when it asks you to give support “the provided error code”. What WD-L014 stands for has not been published by anybody, and this page is not going to guess.

WD-L014 on its own page, with the four hex tails →

• Search WD-L014, not the full string with your hex on the end
• Keep your own hex — it is what support has to work from

The one failure BULKHEAD explained itself

If you could not get in on launch day, the queue is the part with an answer. In its 11 September launch recap BULKHEAD says the wait itself broke the login: a player’s Steam login ticket expired while they queued, so arriving at the front was not enough. The studio describes sending 100 login requests a second while 10 succeeded, and says Hotfix #1 changed the client to obtain a fresh ticket at the front of the queue instead of presenting a stale one. Admission then proceeded in 10,000-player waves until the launch queue reached zero. That is a dated account of one incident, recorded about 19 hours after release — not a reading of whether anything is healthy now.

What happened on launch day →

Every string with a public report, and when it appeared

The dates are the most useful column here and the one nobody else prints. Two of the five most-searched WARDOGS errors were first reported during the August closed beta, three weeks before the paid game existed, and one arrived on 5 September with an anti-cheat change. A page that presented all five as launch faults would be wrong about three of them.

Every string with a page of its own →

The official terms rule out Easy Anti-Cheat

The 0xc0000142 thread from 21 August describes the failure arriving as the anti-cheat loads, and the players in it name Easy Anti-Cheat — they talk about deleting an EAC install and verifying files. Steam’s current WARDOGS listing names Elytra and labels it kernel-level. More decisively, the WARDOGS-specific terms say the game does not use Easy Anti-Cheat and that EAC references in the wider terms do not apply to it. The terms do not say when a historical change occurred or which component produced the August error, so the beta report remains a dated report rather than evidence of the current install.

What the anti-cheat disclosures name →

What players report having tried

Recorded as reports, because that is what they are. Every item below is a player on Steam’s board saying it helped them, none of it is a BULKHEAD instruction, and the last two change Windows security settings, which deserves saying out loud before anybody follows them. The most informative post in the launch-day thread is the one where none of it worked: that player lists an anti-cheat repair, a file verification, driver updates, running as administrator, a Windows downgrade and security-setting changes, and reports that the only thing that changed was the hex on the end of the code.

• Open the game’s local files, run the anti-cheat, choose repair, then verify integrity in Steam
• Restart the PC — reported as the thing that worked, immediately after the repair attempt failed
• Turn off the Steam in-game overlay in the game’s properties
• Player-reported, unconfirmed, and a security setting: turning off Memory Integrity under Windows Core Isolation, then verifying files
• Player-reported, unconfirmed: an input-method editor injecting a DLL into every process was named as a conflict in one thread

Check whether it is you before you change anything

A queue is not a fault on your PC, and neither is an authentication service that is refusing everybody. The cheap first move is to read the official announcement feed and the studio’s own channels for a live incident, because on 10 September the answer was there in writing within hours. Only then start on your own machine.

Where to check service status →

The third number in the family: 1628505085

Smaller than the other two and worth naming because the family is confusing enough without a gap in it. 1628505085 is reported as “Failed to initialise player session with online services” — a later stage than 1147405308, where the login succeeded and the session did not. Exactly one public source documents it, which makes it the thinnest-evidenced string on this page, and even that source's own advice is a caution rather than a remedy: do not reinstall before checking server and login status. That is consistent with everything else in the authentication family, and it is as far as the evidence goes.

The login family: 1147405308, 1147405309 and 1628505085 →

“Repair EAC” is not current WARDOGS advice

The August threads above name Easy Anti-Cheat and that is a historical record. The fullest WARDOGS error table on the public web today puts EAC in the “Most Likely Cause” column for three separate rows — 0xc0000142, 0xc000007b and the shader-compilation crash — and prescribes “Repair EAC” and “Reset EAC” against them. The current Steam listing names Elytra, and the WARDOGS-specific terms explicitly say the game does not use Easy Anti-Cheat. The table is published by a ping-booster vendor whose recommended first step for the login codes is its own paid product, and it is dated to the closed-beta window rather than the shipping build. None of that makes it malicious; all of it makes its EAC instructions historical or inapplicable, not a current fix.

What the anti-cheat disclosures name →

Why this page does not have a numbered fix list

Because one list would merge unrelated failures. BULKHEAD has an active, preliminary lead and a publisher-authored rollback path for WD-L020, and a separate first-hand explanation for the launch queue. The remaining strings are players describing what they saw and tried on dated threads. This page reproduces official steps only where the publisher published them, and does not let those steps spill over onto codes they were not written for.

Steam announcements still print no code; the service account now does

The complete Steam announcement feed still contains no numbered error code: Launch Stability Hotfix #1 names join failures, kicks and queue times, while Season 1, the launch recap and Patch 0.11 also use symptoms rather than codes. That stopped being the whole official record on 23 September, when the official WARDOGS Updates account and a pinned Team17 developer thread named WD-L020 and KB5124010 directly. The older screenshot remains evidence about the launch hotfix, not about every channel BULKHEAD uses today.

An empty server browser throws no error at all

Patch 0.11 separated Community and Official servers into two browsers on 14 September, each with its own filters, text search, persistent server IDs and empty/full toggles. A list with nothing in it is the one connection failure on this page that produces no message, no code and no dialog — which makes it easy to read as an outage when a filter or the wrong tab would look identical. Nothing published establishes a minimum number of community servers, so a short list has no official baseline to be measured against either.

What Patch 0.11 changed about the server browser →

When nothing failed to connect — the game simply closed

Everything above is a connection that did not complete: a queue, a timeout, a kick, a code. A crash is the other shape — no dialog, no number, and sometimes the whole machine. The 10 September hotfix that is cited on this page is often read as a crash fix and is not one; it addressed join failures, kicks and queue times.

Crashes, freezes and what Season 1 actually fixed →

When nothing failed at all — the icons are just lit

The third shape is the one with no message and no crash: a HUD network-status icon lights while the game keeps running. On 22 September BULKHEAD's official updates account published the legend: Server Performance, Packet Loss, High Ping, Connection Stalled, Ping Instability and Saturated Bandwidth. The post says each means a network-performance issue was detected; it gives no numeric threshold or colour scale. They carry no error number, which is why an error-code list does not contain them.

What the network symbols in the top right mean →

Kicked mid-match: “no valid heartbeat within window”

Being thrown out of a match you had already joined is a different failure from not connecting, and since 20 September it has its own message: “KICKED: no valid heartbeat within window.” Team17 support answered it on the game's own board the same morning with one step, a certificate check on the anti-cheat installer, and later told Linux players the game is not supported there. Neither reply explains what the heartbeat is. The step, the Linux answer and the one report that the step only half worked are on the string's own page.

“No valid heartbeat within window” — Team17's step and what is unknown →

Common questions