The current answer
If WARDOGS closes to the desktop, first confirm the right Steam application finished updating, restart the PC and verify that application's files. Record where the crash happens before changing anything else. If Windows restarts or shows a stop code, use the system-crash branch below. These are diagnostic steps, not a confirmed universal WARDOGS crash fix.
- Current scope
- Beta symptoms and PC checks
- Early Access
- Scheduled September 10
- Launch-build repairs not yet confirmed
What happened when WARDOGS failed?
| Failure stage | Record this | First direction |
|---|---|---|
| Steam returns to Play before the menu opens | Any launcher, anti-cheat or missing-file dialog | Check the current application and its installation. |
| Loading or faction selection closes the game | The last screen, whether it happens every time, and any crash report | Use the file check, then test one non-essential app conflict at a time. |
| A match closes to the desktop | Server region, time in the match, action or location, and repeatability | Record a repeatable sequence instead of treating all match crashes as the same bug. |
| The whole PC restarts or Windows displays a stop code | The stop code, any named module and the time | Follow the Windows system-failure branch; a game restart is not a full diagnosis. |
| The game stays open but cannot authenticate | The full online error code and message | Check service availability and login help instead. |
- Check the public play window An unavailable session can be a scheduled closure rather than a crash.
- Error 1147405308 login help Use this when the client remains open and reports failed authentication.
Start with a clean, supported launch
BULKHEAD acknowledged crash reports during the Closed Beta. That acknowledgement does not mean every crash shares a cause or that every launch-build crash has already been repaired. Keep the date and build associated with any workaround you find.
Steam lists Windows PC for the coming Early Access release. An August test that ran on a particular system does not establish that a later client will launch or connect in the same way.
- Save other work, restart the PC, open Steam and allow pending WARDOGS downloads to complete.
- Check whether you opened WARDOGS or WARDOGS Playtest. Compare that entry with the current public play announcement.
- Compare the PC with the published requirements, including memory and available storage.
- Check Windows Update and the graphics-card vendor's supported driver channel. Note the existing and new versions if you install an update.
- Close non-essential capture, overlay or monitoring applications for one test, then restore them individually if the symptom changes.
- WARDOGS PC requirements Compare your hardware with the published Windows requirements.
Verify the affected Steam application's files
Run one check, note its result and retest. This checks the installation; it does not identify every driver, account or service problem. Valve notes that some local configuration files may fail verification without indicating a fault, so a repeated message is not a reason to loop through scans indefinitely.
- Close WARDOGS and open the affected game's Steam Library page.
- Open Properties, then Installed Files, and select Verify integrity of game files.
- Let the scan and any replacement downloads finish before trying the same launch or loading step again.
Loading crashes and crashes during a match
Write down the last successful action: reaching the menu, selecting a faction, joining a server, spawning or entering a particular area. If the game only freezes, also record whether Windows remains responsive and whether the game eventually resumes. A freeze and a crash to desktop are different observations.
After the basic checks, change only one relevant setting or non-essential application at a time and repeat the same action. Record whether the crash moved to a different stage or disappeared. If it continues, stop making unrelated changes and provide that short reproduction sequence to support.
When the game stays running but suffers low FPS or uneven frame delivery, investigate performance separately. Lowering a preset may change workload, but it cannot establish the cause of an authentication failure or a Windows stop error.
- Settings and performance checks Use this for low FPS or stutter when the game remains running.
If WARDOGS restarts the whole PC
A blue or black Windows stop screen, unexpected reboot or system freeze needs a different report from an application closing. Record the stop code and any 'What failed' module name when present. Windows, a driver, hardware or other software can be involved; the game being open at the time does not identify the faulty component.
For a repeated system restart, preserve the error details and stop repeating the same launch just to reproduce another reboot. Use Microsoft's stop-code guidance and the game's support route. Avoid removing Windows security updates, disabling security protections or deleting anti-cheat components based only on an old beta comment.
- Microsoft: unexpected restarts and stop codes Follow the system-level guidance for the Windows error you actually see.
Prepare a crash report that can be investigated
Use a private support request for logs or dumps when support asks for them, and check attachments for personal information before sending. Do not assume that an older guide's anti-cheat name, folder or repair command applies to the build shown in your own dialog.
- Date, local time and time zone; WARDOGS or WARDOGS Playtest; any visible build number.
- Windows version, CPU, GPU, RAM and graphics-driver version.
- The exact failure stage and a short sequence that reproduces it, including the server region for a match crash.
- The full launcher, anti-cheat, crash-reporter or Windows message; keep any report identifier shown.
- Which checks you completed and what changed after each one, including the result of Steam's file check.
- Team17 Player Support Send the failure details through the publisher's support portal.
- WARDOGS Steam support discussions Check for current developer guidance about the same symptom.
Direct answers
Frequently asked questions
Why does WARDOGS crash immediately on startup?
The failure can occur before the menu for several reasons. Preserve any launcher or anti-cheat message, confirm the correct Steam application finished updating, and use the clean-launch and file-check steps. There is no confirmed single repair for every startup crash.
Will verifying files fix crashes in a match?
It can repair missing or damaged installation files, which is why Valve recommends it for crashes. It cannot establish that every match crash is a file problem. Retest the same action once and keep a useful reproduction report if it persists.
Should I uninstall a Windows security update or disable anti-cheat?
Not as a general WARDOGS repair. An older player's workaround does not identify your system's cause. Use current official guidance for the exact Windows or anti-cheat message and keep security protections enabled.
What should I do if my entire PC restarts?
Record the Windows stop code, any named module and the time, then use the system-failure branch and official support. A repeated full reboot is different from the game returning to the desktop; repeatedly relaunching is not a diagnosis.
Are these confirmed Early Access crash fixes?
These are prelaunch checks and reporting guidance for the scheduled September 10 release. A specific Early Access crash repair needs to match the actual launch build and its current support information.