The Dawn of War IV closed beta ran October 21–26, 2026 and has ended. As of November 2, there is no currently open beta established here. The October announcement's application deadline and participant instructions describe that completed test, rather than a way to join today.
The full Windows Steam release is planned for December 3, 2026. Commander Edition's early unlock begins November 30. Those release dates are separate from the closed-beta schedule.
The October beta schedule and playable modes
This October test has ended; the dates and modes describe that completed event.
| Test detail | October closed beta |
|---|---|
| Dates | October 21–26, 2026 |
| AI mode | 1v1 Skirmish against AI throughout the beta |
| Multiplayer mode | 1v1 during scheduled sessions |
| Multiplayer session times | Shared with selected participants |
| Entry | Limited selection, not guaranteed by applying |
| Current status | Ended |
The description of AI Skirmish being available throughout the beta applied within the test window. It did not promise continued access after October 26. The scheduled multiplayer sessions also belonged to that limited test, with no universal session timetable to reuse now.
The announced beta scope should not be expanded into a claim that campaign, co-op campaign, Last Stand, or other announced release features were part of this test.
How the completed application process worked
The October instructions separated applicants into three groups:
- Previous playtest participants were already on the testing list and were told to watch their inbox for next steps.
- Existing newsletter subscribers were told to expect an email containing the application survey and further instructions.
- New applicants were instructed to subscribe before October 18 and confirm their email address. Applications, a survey, and next-step information were being sent from October 12.
These are historical instructions. The deadline has passed, and completing those steps now should not be described as a current application route for the ended October beta.
Being on the testing list and being selected were also different states. Places were limited, and completing an application did not guarantee entry. A newsletter subscription alone was not an access entitlement.
The beta's discussion and media restrictions
Selected October participants were allowed to discuss their closed-beta experience only within the terms of the beta NDA. That permission did not allow recording, livestreaming, taking screenshots, or sharing gameplay footage from the test.
The test announcement also said there would be no private closed-beta Discord for this round. Participants were encouraged to discuss permitted experiences through the usual community channels and their own social media, subject to the stated restrictions.
Do not apply the rules from an older alpha announcement as if they were the October beta's exact terms. Each test's instructions need to be read for its own dates, build, and participant conditions.
Feedback and access problems
Selected participants were to receive customer-support contact details ahead of the beta, including guidance on information useful for investigating technical, account, or access issues. The team also planned a post-beta survey.
Those participant-specific support instructions should not be replaced with a guessed support address or an unofficial access workaround. If you were selected and need help relating to that test, use the details supplied with your invitation.
Read an old invitation in its original context
If you participated in the October test, keep the invitation and its dates with any support information you received. An email about next steps for that round is not a standing entitlement to every later test. The announcement established that previous participants were on the testing list; it did not publish a permanent access rule for all future builds.
The distinction also helps when reviewing an old access problem. During October 21–26, AI Skirmish and scheduled multiplayer had different availability. A multiplayer session being outside its scheduled window was a different situation from being unable to enter the test at all. The exact session times were provided to selected participants, so a public article cannot reconstruct a player's schedule from the overall beta dates alone.
For feedback on that experience, identify the mode, the part of the test and the behavior you observed. Follow the contact and information requests provided for participants. The stated support route existed to investigate technical, account and access issues, while the post-beta survey collected feedback on the experience.
For non-participants, public impressions can help explain what someone experienced in the limited test. Read them as reports about that build and its available modes. A discussion of 1v1 Skirmish cannot settle the quality of a campaign the writer did not describe playing, and a positive test report does not create a new way to join the ended event.
Where future testing opportunities are announced
Future test information is announced through the Dawn of War IV newsletter and official Discord community. The announced community identifier is discord.gg/dawnofwar4.
Following those channels is a way to receive announcements. It is not proof that another test is open, that your previous selection carries forward, or that any particular applicant will receive access. For a new opportunity, check the actual test dates, eligibility instructions, application deadline, and invitation conditions before treating an old sign-up article as current.