The number identifies a reported error, not its root cause

The accompanying authentication text tells you which operation failed. It does not, by itself, identify a broken local file, a ban or a particular network fault. Keep the exact wording attached to the number when searching for a matching report.

The original Steam thread was opened on August 21 by a player who said they had both a pre-order and an invitation. Their error appeared when a login queue finished. The author later added a message attributed to Discord about heavy login demand. That is a player's repost of an update, not a developer diagnosis published in that thread. EVIDENCE / 02Original Steam report: Access Denied and 1147405308Open source (opens in a new tab)

This history is a reason to investigate the login stage before assuming you need to repair Windows. It is not evidence that every later occurrence comes from the same incident.

Compare a new occurrence with the historical report

Write down what happened immediately before the error. Note whether the client reached a queue, whether that queue finished, and whether you had already entered a match.

Then check the current test schedule. The August discussion contains later comments about that test having ended; those comments do not describe the current Closed Beta 02 window. EVIDENCE / 02Original Steam report: Access Denied and 1147405308Open source (opens in a new tab)

Use the Access Denied decision guide for the account and client checks. If the number differs by even one digit, retain the different code. Do not apply this page's historical report to another error without matching its full text.

What a file check can tell you

Valve's file-verification procedure checks the installation and is documented for missing game content or crashes. EVIDENCE / 03Steam Support: Verify Integrity of Game FilesOpen source (opens in a new tab)

Use it when you also have a reason to suspect the local installation, such as an interrupted update or a separate launch problem. A successful file check does not establish that the online service accepted the account. Record its result once; repeatedly running it gives little new evidence about the login refusal.

There is no code-specific basis here for deleting configuration folders, installing a replacement DLL or disabling network and security features. Those changes would introduce new variables before the failing stage has been explained.

Give support a report they can compare

Use your observations to fill in a report:

FieldUseful detail
Error1147405308 and the complete accompanying text
AttemptDate, time and timezone
ClientPlaytest or main game, plus build/version if visible
AccessPre-order or accepted invitation; whether the test entry is present
SequenceLast successful screen, queue behavior and when the message appeared
ScopeEvery attempt or intermittent; whether an earlier session worked
Checks already doneUpdate status, Steam restart, and any file-check result

Use WARDOGS' official community support route or the Team17 support page, which directs unlisted games to its general portal. EVIDENCE / 04Team17 Player SupportOpen source (opens in a new tab)

If an official update later changes the situation, add the new result and its time to the same report. That preserves the difference between the original failure and an attempt made after a service change.