WARDOGS crashing: which crashes the patch notes fixed, the anti-cheat 'access denied' error, the login queue, and what to try in order

A crash is the game closing mid-session or during load. A refusal is the game declining to start with a message — the changelog says startup now has 'clearer messages when something fails early and a route to recovery', so read the message. The queue is the game running but holding you at a login screen; on 10 September that affected hundreds of thousands of people and was not a fault on your machine.

The community's own sorting shows in the Steam guides that were trending on 13 September: 'Fix 1147405308 Error Access Denied', 'ОДНО ИЗ РЕШЕНИЙ ОШИБКИ WD-L004' (one solution for error WD-L004), 'How to bypass the WARDOGS queue', and a cluster of Russian-language guides about 'zapret' — a DPI-bypass tool — and 'вход из РФ' (logging in from Russia), which are connectivity problems specific to that region rather than crashes.

From the Season 1 changelog, 9 September 2026, under Performance and stability: 'Fixed two crash paths in the frame generation pipeline.' 'Fixed a crash caused by network calls scheduled off the game thread.' 'Fixed a crash when closing a chatbox entry tooltip.' 'Fixed a crash involving buildables.' 'Fixed a crash when firing a weapon whose owner had left.' Plus: 'GPU crash reports now carry more detail, so we can act on them faster.' 'Removed a legacy graphics dependency.' 'Improved startup reliability, with clearer messages when something fails early and a route to recovery.'

Then patch 0.11, 12 September: 'More GPU crashes addressed', delivered in the 14 September maintenance. If your crashes match one of those descriptions — a crash while building, in chat, when a gunner leaves, or with Frame Generation on — the launch build or 0.11 is supposed to have fixed it, and being fully updated is the first check.

BULKHEAD documents none of its error codes. The Steam forum does, thread by thread, and where a developer account posted we say so. 1147405308 — 'Failed to authenticate with online services' / 'Access Denied'. During the 21 August beta a player thread titled '(RESOLVED) pre-purchased, but access denied? error 1147405308' traced it to login overload, quoting the studio's Discord message: 'The login queue is getting HAMMERED… we are seeing a new issue we didn't see in the Closed Alpha due to the sheer volume of logins.' On launch day a 'Failed to Authenticate With Online Servers' thread tied the same code to backend services being taken down for the hotfix. A Russian-language community guide (ZufyC) offers a client-side cause for the cases that persist: a broken WinHTTP proxy — check with `netsh winhttp show proxy`, reset with `netsh winhttp reset proxy` — and notes that its fix 'does not fix all possible causes'. 1147405316 — 'Failed to join server. Server queue is full.' A 'Server queue is full' thread from launch week; the developer 'Dev Updates' thread explains the underlying cause on 10 September: 'Currently rate limited and working with Valve directly to resolve this.' 1628505091 — 'Failed to connect to server in a reasonable time' / 'Join Timed Out': two launch-day threads; players report retrying or restarting Steam. 'The anti-cheat service refused the game executable' — a 4 September thread (player MoJo) attributes it to Elytra's kernel driver failing under Windows driver enforcement; other players in the thread blamed conflicting anti-cheat software (Riot Vanguard, FaceIT) and corrupted files, and fixed it by deleting the Elytra folder and the game's AppData folder then verifying files, or by removing the conflicting software. No BULKHEAD reply appears in that thread.

The enforcement policy on wardogs.com describes what runs alongside the game: 'client and server side detection, monitoring applications running on your machine during gameplay, analysing input and gameplay patterns for anomalies, and validating that the game and your hardware haven't been tampered with.' A refusal at launch with 'Access Denied' and the code 1147405308 is, going by the community guide's title, an anti-cheat refusal; WD-L004 appears to be a launcher-side code. Neither is documented by BULKHEAD in the Steam feed or on wardogs.com, so we cannot tell you what each means officially — only that guides exist and what the policy says the software checks.

What the policy makes clear is what not to do: 'Interfering with the anti-cheat software, blocking it, spoofing what it reports, or preventing it from running' is bannable, and 'the account holder is responsible for any infraction on the account'. Any 'fix' that disables or modifies the anti-cheat is a ban risk, not a fix.

Voice going silent: the changelog fixed 'voice cutting out permanently after a failed join' and added 'a visible communication status' — check the indicator before restarting. Servers not appearing: before patch 0.11 the browser 'has been poor' in BULKHEAD's words; after 14 September there are two tabs, Community and Official, and the Official tab has no filters to set. Being kicked: the changelog says 'the kicked from server message now only appears if you were actually banned', so a kick message post-launch means a ban, not a bug. Regional blocks: several Russian-language guides cover 'zapret' and logging in from Russia, which are connectivity issues with no BULKHEAD statement.

None of these produce a crash log, and none are fixed by graphics settings.

The locked 'Dev Updates' thread on the Steam forum, posted by G_Medlin (tagged developer, Team17), is the only official minute-by-minute account, and it explains why most launch-day 'crashes' were not crashes. Initial post: thousands in the login queue, response 'significantly exceeded beta expectations', an apology for putting players to the back of the queue. 5 pm UTC: 'Currently rate limited and working with Valve directly to resolve this.' 6 pm: players filtering into matches, queue processing slowly. 7 pm: server restart for 'an unforeseen stability issue absent from beta'. 8 pm: Steam client update required; all players logged out and re-queued in waves. 8:30 pm: Launch Stability Hotfix #1 released. 11 pm: 135,000 players through the queue and in game. 12 am: 'Queue issues should have passed now! Thank you for your patience.'

Insider Gaming puts the unlock itself at 4 pm UTC, which means the rate limit hit within the first hour. If your problem was on 10 September between 16:00 and 00:00 UTC, it is documented above and it was not your PC.

On 10 September most 'not working' reports were the login queue. BULKHEAD's Launch Stability Hotfix #1 (20:20 UTC): 'All currently logged-in players will be forced to close WARDOGS and restart the game. You will then be prompted to download the latest client update. Once the update has been installed and you relaunch the game, all players will return to the login queue. We will then begin allowing players into the game in controlled batches.' It addressed 'players unable to join servers', 'players being unexpectedly kicked from servers during play' and 'extended login queue times'.

PCGamesN's account from inside the studio has the mechanism: login tickets were expiring in the queue, so 'out of the 100 players per second that should have been let through the gate, just ten of them were'; the fix was to issue 'a fresh ticket from Valve's login system' at the front of the queue, then admit players manually 'in sets of 10,000'. The queue reached zero that night. Two 'How to bypass the WARDOGS queue' guides trended afterwards; there is no sanctioned bypass, and BULKHEAD admitted to a queue jump only for 'about 11' streamers.

Also from PCGamesN's interview: UI/UX Director Howard Philpott says the zero-tolerance anti-cheat stance 'very, very quickly turned into banning our legitimate alpha testers', including streamers Shroud and Summit1g, and Executive Producer Joe Brammer describes a human moderator who 'banned Summit instead of the cheater in Summit's stream'. If your account was banned in the launch window and you did nothing, the enforcement policy sets out an appeal process ('what you can do if you think we've got it wrong'), and the studio has publicly acknowledged erroneous bans in that period.

1. Update. Patch 0.11 and the launch build carry the crash fixes above; Steam should update automatically, but the hotfix required a restart to apply. 2. Read the startup message. The changelog says early failures now report 'clearer messages… and a route to recovery'. 3. Turn off DLSS Frame Generation. It is the one component with two fixed crash paths and it now toggles live. 4. Lower shadow quality. The auto-benchmark already clamps it on fast machines; on slow ones, shadows are the expensive setting in UE5. 5. If it is an 'Access Denied' code, do not touch the anti-cheat; follow the community guide for that code and, if it persists, report through BULKHEAD's channels (Discord, X, YouTube are the ones the Steam Q&A names). 6. If it is the queue, wait — the developer controls admission rates and has said it will scale capacity, including 'increased server capacity in the Asian region' in 0.11.

For voice failures rather than crashes — the game runs but nobody can hear you — the changelog fixed 'voice cutting out permanently after a failed join', and a community guide covers low microphone volume. The settings page has that.

BULKHEAD asks for GPU crash reports, which 'now carry more detail', and the Steam Q&A says players can 'engage with developers via Discord, X, and YouTube'. The player-safety page describes the in-game report tool for player conduct, not crashes. For a crash, the useful details are the ones the community guides ask for: the error code if any, whether Frame Generation was on, what you were doing (building, in chat, firing from a vehicle), and the server. The studio fixed six named crash classes between beta and launch on that kind of report.