Halo Campaign Evolved Known Issues and Fixes

This page is an official-issue snapshot of Halo: Campaign Evolved, read from the saved Halo Support Known Issues article on August 6, 2026, rather than a live service dashboard. An issue appearing here means it was visible in the captured official article, not that every player is affected or that the bug is still unfixed today. Before applying any dated workaround to another game version, confirm the current status against the official patch notes and Halo Support.

Snapshot date and status labels

Every entry below shares the same provenance: it was captured from the official Halo Support Known Issues article and re-checked against the visible body on August 6, 2026. No community incident reports, forum threads, or player-supplied reproduction URLs were saved during research, so this reference holds official evidence only. The upstream article's own visible "updated" date was not recorded in the capture, so it remains To be confirmed against the live page. Treat each status label as a snapshot reading, not a warranty that the bug still reproduces or that the listed workaround still applies.

Global cinematic and audio issues

Three global branches affect cinematics and audio on every platform. Two offer an official workaround, while the third is listed for awareness only. The same description applies across Xbox, PlayStation 5, and PC.

| Branch | Status | Official workaround | |---|---|---| | Cinematics may stutter if the display refresh rate is not an even multiple of 30 Hz | Officially confirmed | Set the display to 60 Hz, 120 Hz, or 240 Hz; enable TV Game Mode; turn off VRR | | Audio and video desync, with a brief freeze, if the game is paused and resumed during a cinematic | Officially confirmed | None provided | | Brief audio popping or stuttering during The Truth and Reconciliation | Officially confirmed | None provided |

Campaign progression issues

Two confirmed branches affect campaign progress and co-op flow. Neither ships with an official workaround in the captured article, so players should rely on official support until a fix lands. Both are tagged Global and apply across every platform.

| Branch | Status | Official workaround | |---|---|---| | Co-op navigation markers do not progress until every Fireteam member passes them | Officially confirmed | None provided | | In Two Betrayals, destroying the Banshee after the first generator blocks further progression | Officially confirmed | None provided (avoid destroying the Banshee) |

Xbox-specific issue

A single captured branch is scoped to Xbox Series X|S instead of every platform. Suspending the game during a cinematic can leave the last frame overlaid on later cinematics for the remainder of the playthrough. The official remedy is a full console restart, which restores cinematics to normal behavior. No fix date for the underlying suspension behavior was recorded in the snapshot, so it remains To be confirmed.

PC launch and input issues

Two PC branches concern how the game starts up and how custom key bindings persist, rather than graphics hardware. Both carry a concrete official workaround, and neither depends on a specific GPU vendor or driver version. They are reproduced here exactly as the official article describes them.

| Branch | Status | Official workaround | |---|---|---| | Launching from HaloCampaignEvolved.exe in the Steam folder can cause sign-in failure, severe performance issues, or a freeze needing Task Manager | Officially confirmed | Launch from the Steam library inside the Steam app | | Custom key bindings may reset after closing the game | Officially confirmed | Move the conflicting bind to an unused key first, then assign the desired key |

GPU, CPU, and frame-generation issues

Six confirmed PC branches tie symptoms to specific hardware, driver versions, or upscaling and frame-generation settings. Several carry a dated driver recommendation, so always match the fix to the exact version named rather than applying it universally. The recommended drivers shown by Halo Support on August 6, 2026 were NVIDIA 610.88, AMD 26.6.1, and Intel 32.0.101.8861.

| Branch | Status | Official workaround | |---|---|---| | Some Intel 13th and 14th gen processors crash on launch due to a pre-existing Intel microcode issue | Officially confirmed | Install the latest BIOS update from the system or motherboard manufacturer | | AMD GPUs crash with high refresh rate displays if VSync is on and max frame rate is below one quarter of refresh rate | Officially confirmed | Raise max frame rate to at least one quarter of refresh rate (180 Hz then 45 FPS, 240 Hz then 60 FPS, 360 Hz then 90 FPS), or disable VSync | | DLSS Low upscaling quality with Low graphics quality can show visual grain, haze, or oversized lens flares | Officially confirmed | Use a higher DLSS quality setting | | NVIDIA RTX 50 series cards may crash on Keyes with driver versions 610.47, 610.62, and 610.74 | Officially confirmed | Update the NVIDIA driver to 610.88 | | XeSS Frame Generation with an in-game max frame rate limit can leave the game visually frozen with occasional frame updates | Officially confirmed | Use FSR or DLSS Frame Generation, turn off Frame Generation with XeSS, or remove the max frame rate limit | | XeSS Frame Generation with XeSS upscaling can cause graphical issues and limit frame rates during cinematics | Officially confirmed | Use Frame Generation with DLSS or FSR, or disable Frame Generation while using XeSS |

How patch notes change status

Patch notes are the mechanism that moves a known issue from confirmed to fixed, so they change how a snapshot entry should be read over time. The captured record lists a launch on July 28, 2026 and a July 29 day-one patch, build 2026.07.25.1112544, which reset mid-mission saved progress while keeping unlocked Missions and Rally Points available. When re-read on August 6, 2026, the Release Notes still showed "Updated July 28, 2026" and no newer build number. The July 29 patch also carried the following fixes captured in the release record:

• Stability crash when watching or skipping the intro cinematic in The Maw with FSR on AMD GPUs (drivers 26.6.2 and 26.6.4).
• A new PC warning when the game launches with known-bad AMD or NVIDIA GPU driver versions.
• General stability improvements for Pillar of Autumn, plus several enemy behavior fixes across Truth and Reconciliation, Assault on the Control Room, and The Silent Cartographer.
• Reduced performance hitching for players with large friends lists on PC, Steam, and PS5.

The unresolved AMD FSR branch

One branch sits between the Known Issues article and the Release Notes, and the saved evidence preserves two dated statements that do not fully agree. The July 29 patch notes list The Maw FSR crash on AMD drivers 26.6.2 and 26.6.4 as fixed. The Release Notes body still displayed the same branch as a high-impact known issue on August 6, 2026, so its current status is best read as unresolved pending a newer build.

Report a problem

Players who hit a branch not captured here should report it through the official Halo Support game issue form rather than a community channel, since no community evidence is held against this snapshot. The same form feeds the official Known Issues article that this page summarizes, so a well-described report can move a future status label from confirmed to fixed. Always include the platform, driver or build version, mission name, and exact reproduction steps so the report matches a dated branch. Until the upstream article is re-captured, any new issue's confirmation status stays To be confirmed.