Halo: Campaign Evolved Early Access Known Issues and Workarounds
Halo Support lists workarounds for a Two Betrayals progression block, cutscene stutter, Steam launch problems, GPU driver crashes and XeSS Frame Generation.
Halo Support has published a list of high-impact issues affecting the current Halo: Campaign Evolved Early Access release. The page is a known-issues list, not a repair patch. It covers one campaign progression block, cutscene problems and several PC-specific crashes, with workarounds players can use now.
Do not destroy the Banshee in Two Betrayals
After the first generator in Two Betrayals, destroying the Banshee can prevent the mission from progressing. Leave that Banshee intact until the objective advances.
Co-op groups should also move through navigation markers together. Halo Support says a marker will not progress until every member of the Fireteam has passed it. If an objective appears stuck, check the position of the other players before restarting the mission.
Cutscene stutter and audio sync
Cinematics may stutter when the display refresh rate is not an even multiple of 30 Hz. Halo Support recommends using a rate such as 60 Hz, 120 Hz or 240 Hz where possible. Turning on the television's Game Mode or disabling Variable Refresh Rate may also help on affected setups.
Avoid pausing and resuming during a cinematic. Doing so can make the audio and video drift out of sync or briefly freeze the scene. On Xbox, suspending the game during a cinematic can leave the last frame over later scenes. Fully restarting the console restores normal playback.
Steam and graphics-driver problems
Steam players should launch the game from the Steam Library. Opening HaloCampaignEvolved.exe directly from the installation folder can start the game without a proper Steam connection, causing sign-in failures, severe performance problems or a freeze. If the game shows an ALPHA through MIKE code, use the login failed error-code guide to identify the matching account, network or service check.
Halo Support also lists two driver-specific crash cases:
- AMD driver versions 26.6.2 and 26.6.4 may crash while skipping The Maw's opening cinematic with FSR enabled. Watching the cinematic, changing the upscaler or returning to driver 26.6.1 are among the listed workarounds.
- NVIDIA RTX 5000-series cards may crash in Keyes and The Maw on driver versions 610.47, 610.62 and 610.74. Halo Support recommends updating to 610.82 or returning to 596.49.
Players using XeSS Frame Generation should remove the in-game frame-rate cap, disable Frame Generation or use DLSS or FSR instead if the image appears frozen. XeSS upscaling with Frame Generation can also cause visual problems and limit the frame rate during cinematics.
Where to report another problem
The official list does not cover every possible error. Halo Support asks players to submit unlisted game problems through its Game Issue Report Form. Account, purchase and storefront problems should go to the matching Xbox, PlayStation, Microsoft or Steam support service.
For hardware requirements and a repeatable settings order, see the PC settings guide. Mission routes are available in the campaign walkthrough.
Sources
Last reviewed: July 24, 2026