WARDOGS Troubleshooting
Start with the access window, not the PC
The 21–24 August WARDOGS Closed Beta is over. If the Playtest now shows
“Access Denied” or error 1147405308, there is no active beta service to authenticate against;
reinstalling files or changing Windows security will not fix that. If an official access window is open,
separate a service incident from a local launch or graphics problem before changing the machine.
Jump to
Error code 1147405308: Access Denied
Current answer: the August Playtest is closed. The error appears with “Failed to authenticate with online services,” and the client no longer has an active beta service to use. During the open test, the same code was reported while the login queue and authentication service were overloaded. BULKHEAD has not published a public code dictionary, so do not treat an unofficial registry, firewall or network-filter recipe as an official fix. See the full WARDOGS error 1147405308 guide.
Known issues from the 21–24 August Closed Beta
| Issue | What the evidence says | First action |
|---|---|---|
| Login queue / 1147405308 | Login services were under exceptional opening-day load; after 24 Aug 02:00 UTC, the test was closed. | Check the official access window and service notices. |
| Crashes | The pinned known-issues thread says crash reports were being tracked. No single universal fix was documented. | Capture the crash details, then verify files and update the GPU driver. |
| One server region or no servers | Listed as a beta server-browser issue. | Check the pinned thread before changing the router or firewall. |
| Local voice chat | The pinned thread documented a test-build workaround. | Use the official workaround for that build, then verify the Windows input device. |
| Supporter Pack missing | The content was unavailable in the beta. | Do not repurchase; wait for the release build. |
WARDOGS won't launch
Use this checklist only when an official access window is open and the client itself fails to start. It is not a fix for a closed Playtest or a live service outage.
- Verify game files in Steam Right-click WARDOGS → Properties → Installed Files → Verify integrity. This is a low-risk way to replace an incomplete or corrupted download.
- Check Easy Anti-Cheat installed WARDOGS uses kernel-level EAC. If the anti-cheat service did not install or is not running, the game exits silently or never reaches a window. Reinstalling the EAC service is usually available from the game's Steam install folder. Full anti-cheat page.
- Disable overlays Discord, Steam, GeForce Experience, MSI Afterburner, RivaTuner and similar all inject into the game process. Injection plus kernel anti-cheat is a well-known source of launch failures.
- Update your GPU driver Not usually the cause of a total launch failure, but cheap to rule out and a common cause of the crash-immediately variant.
- Read the exact error before changing security settings Secure Boot, antivirus and firewall changes are not generic first steps. Use the anti-cheat guide only when the message actually identifies Easy Anti-Cheat or a documented requirement.
WARDOGS crashes on startup
If the game reaches a window and then dies, the causes shift away from anti-cheat toward the graphics stack:
- Out-of-date or bad GPU drivers. Install the current driver cleanly. Around a major launch, vendors typically ship a game-ready driver — take it.
- Corrupted shader cache. Clear the vendor shader cache (both Nvidia and AMD control panels expose this) and let it rebuild.
- Unstable overclocks. This is the underrated one. A CPU or memory overclock that is stable in every other game can fail under a simulation load like 100 networked players plus destruction. Reset to stock before reporting a bug — including XMP/EXPO memory profiles as a test.
- Overlays. Same as above.
- Insufficient VRAM at high texture settings. Drop textures a tier and retry. Settings guide.
Stuttering and frame drops
Distinguish three different problems that all feel like stutter:
| Symptom | Likely cause | Fix |
|---|---|---|
| Hitches while moving across the map, especially by helicopter | Terrain streaming from slow storage | Install on an SSD. A 256 km² map streamed at speed is a hard case for a mechanical drive |
| Stutter in the first match or two, then it clears | Shader compilation | Normal. Let the cache build; do not change settings mid-way, which invalidates it |
| Frame rate collapses specifically in big zone fights | CPU-bound simulation load | Lower view distance, shadows and volumetrics. GPU settings will not fix a CPU bottleneck |
| Regular periodic hitches everywhere | Background software, overlays, or thermal throttling | Close overlays, check temperatures and power profile |
High ping, packet loss and rubber-banding
These are different faults and are worth separating, because they have different fixes:
- High ping but smooth play — you are likely on a distant server region. Check whether the game exposes a region selector; if matchmaking placed you badly, that is the cause.
- Normal ping but rubber-banding and teleporting — that is packet loss, not latency, and the ping number will not show it. Test a wired connection; Wi-Fi is the usual culprit, particularly on congested 2.4 GHz.
- Everything fine until a big fight — could be server-side load in a 100-player match, which is exactly what Early Access is for. Check the server status page before assuming it is you.
Stuck in queue or matchmaking failing
On launch day, expect matchmaking pressure — WARDOGS passed a million Steam wishlists before release. Before troubleshooting your own machine, confirm it is not global: if the official channels are reporting an issue, there is nothing to fix locally. See server status.
If others are connecting normally and you are not, the cause is local: anti-cheat not running, a firewall blocking the game, or a VPN interfering with matchmaking.
Microphone and proximity voice chat
WARDOGS uses proximity voice chat, so audio problems have real tactical cost. Standard checks apply: confirm Windows has the right input device as default, check the app has microphone permission under Windows privacy settings, and confirm the in-game input device matches. If you can hear others but they cannot hear you, the fault is almost always the Windows input device or permission rather than the game.
Controller not working
This may not be a fault. Controller support in WARDOGS is officially described as limited. A missing prompt, an unmapped action or an input path that simply does not respond may reflect the current state of the build rather than a problem with your hardware. Steam Input can paper over some of it by mapping a controller to keyboard and mouse, but that is a workaround, not support. Mouse and keyboard is the intended input.
What remains unknown before Early Access
The beta established several service and client symptoms, but it did not establish every cause that will exist in the 10 September 2026 Early Access build. New entries will be added only with a dated reproduction, a developer response or a clearly labelled cluster of player reports. The absence of a public official error-code dictionary remains an explicit unknown.
Troubleshooting FAQ
What is WARDOGS error code 1147405308?
It appears with Access Denied and a failed online authentication message. During the beta it appeared during a login-service incident; after the beta it appears because the Playtest is closed. See the dedicated explanation.
Why won't WARDOGS launch?
First confirm an official access window is open. For a real client launch failure, verify files, read the exact error, then check Easy Anti-Cheat and overlays. Do not change firmware or security settings for an unrelated online-authentication code.
Why does WARDOGS crash on startup?
Usually GPU drivers, a corrupted shader cache, overlay injection, or an unstable CPU or memory overclock. Reset overclocks before reporting a bug.
Why is WARDOGS stuttering?
Traversal stutter points at storage — install on an SSD. First-match stutter is shader compilation and clears. Stutter only in big fights is CPU-bound simulation load.
Why is my ping high in WARDOGS?
Check your server region first, then test wired. Rubber-banding with a normal ping is packet loss, not latency.
My microphone isn't working in WARDOGS.
Check the Windows default input device, Windows microphone privacy permission, and the in-game input device. If others hear nothing, it is almost always one of those.
Why doesn't my controller work in WARDOGS?
Controller support is officially limited. This may be the build's current state rather than a fault.
Can I refund WARDOGS if it doesn't run?
Standard Steam refund rules apply — under two hours played, within fourteen days.
Sources: the official Steam store page (anti-cheat, proximity voice, limited controller support, storage), the official Steam announcements, and the pinned Closed Beta known-issues thread. Player-reported symptoms are labelled separately from official statements. Back to the PC hub.