Updated: August 19, 2026
The following list contains some of the high-impact known issues for the current release of Halo: Campaign Evolved:
Global
- Cinematics may occasionally stutter during playback if the display refresh rate is not an even multiple of 30 Hz.
- Workaround: If possible, set your display refresh rate to a multiple of 30 Hz (such as 60 Hz, 120 Hz, or 240hz), turn on Game Mode on your TV if available, or turn off Variable Refresh Rate (VRR), as it may contribute to cinematic stuttering on some setups.
- Audio and video may become out of sync, and the cinematic can briefly freeze, if the game is paused and then resumed during a cinematic.
- Players in a co-op fireteam may experience stability issues if the cutscene before the space section in Heavy Burden is skipped.
- Workaround: Allow the cutscene to play through to completion.
- Navigation markers do not progress until everyone in the Fireteam passes them.
- After the first generator in Two Betrayals, players will be unable to progress if they destroy the banshee.
- While playing The Truth and Reconciliation, you may hear brief popping or stuttering of audio during gameplay.
- For Keyboard & Mouse, the primary key bind for Grenade may reset to its default setting (G) after relaunching the game if it is assigned to a key that is used as the default binding for another action.
-
Example: Setting the primary bind for Grenade to R (default for Reload) or Q (default for Equipment) may cause it to default to G after relaunching the game.
- Workaround: Bind the secondary key bind for Grenade to the desired key. To use G for a different action, bind Grenade's primary key bind to a key not used by default for any actions, such as the letter L or number 8.
-
Example: Setting the primary bind for Grenade to R (default for Reload) or Q (default for Equipment) may cause it to default to G after relaunching the game.
XBOX
- Suspending the game during a cinematic may cause the last frame shown before suspension to remain on screen and overlap subsequent cinematics for the rest of the playthrough.
- If this occurs, fully restart your console to restore cinematics to normal.
PC
- Launching Halo: Campaign Evolved directly from the HaloCampaignEvolved.exe file in the Steam installation folder may cause the game to launch without connecting to Steam. When this occurs, you may be unable to sign in, experience severe performance issues, or encounter a game freeze that requires the application to be closed through Task Manager.
- Workaround: Launch Halo: Campaign Evolved directly from the Steam library within the Steam app itself.
- Some Intel 13th and 14th generation processors may crash on launch due to a pre-existing Intel microcode issue that can prevent affected systems from successfully starting certain applications.
- Players who have not updated their BIOS recently may be affected. If the game closes or crashes before reaching the splash screen, install the latest BIOS update available from your system or motherboard manufacturer.
- NVIDIA RTX 50 series graphics cards may crash on the mission Keyes when using driver versions 610.47, 610.62, and 610.74.
- Workaround: Update your NVIDIA driver to 610.88.
- AMD graphics cards using driver versions 26.6.2 or 26.6.4 will likely crash when skipping the introduction cinematic in the mission The Maw while FSR is turned on. Watching the cinematic to completion can reduce the likelihood of a crash.
- Workaround: Change your upscaling technique to DLSS, XeSS, or TSR, turn on Frame Generation while using FSR, or roll back to driver version 26.6.1.
- Players using the Low upscaling quality option for DLSS upscaling may notice visual grain, haze, or oversized lens flares when using Low graphics quality settings.
If you experience an issue not listed here, report it through Halo Support using our Game Issue Report Form.