Halo: Campaign Evolved First Update 16.754.404 Released on July 29
Halo Studios has released the first post-release patch for Halo: Campaign Evolved on all platforms today, July 29, and this brings stability on all platforms, adjustments to AI enemy behaviour and more.
Console gamers will see this download as Halo: Campaign Evolved update 16.754.404, and this is a chunky file for something that doesn’t bring new content.
For the complete info on what got changed, as well as each platform’s file size, read on.
Halo: Campaign Evolved Update on July 29 Brings Bug Fixes
File Sizes:
- XBOX: 13 GB
- PlayStation®: 7 GB
- Microsoft Store/Xbox app PC: 4 GB
- Steam: 21 GB
Resolved Issues
- Stability has been improved when watching or skipping the introduction cinematic in the mission The Maw while FSR is turned on with AMD graphics cards using driver versions 26.6.2 or 26.6.4.
- All PC versions now display a warning when Halo: Campaign Evolved is launched with an AMD or NVIDIA GPU driver version that has known issues.
- XBOX Gamertags now display throughout the account linking process for PlayStation® and Steam players.
- General stability improvements for the mission Pillar of Autumn.
- Jackals in the hanger hallway of The Truth and Reconciliation now actively patrol instead of remaining idle.
- On Assault on the Control Room, Spec Ops Elites near Rally Point Delta now engage the player as intended.
- On Assault on the Control Room, enemies no longer walk into the Control Room exterior.
- The Hunter pair now consistently engages the player after approaching the cartographer’s entrance on The Silent Cartographer.
- A charged Plasma Pistol shot no longer kills players who have full health and shields on any difficulty.
- Performance improvements have been made to reduce hitching for players with large friends lists on Windows PC, Steam, and PlayStation®.
While we did get a patch today, Halo Studios is aware of various gameplay-related bugs and issues, and we’ve included it in the article. No timetable has been given on when these will be fixed, but at the very least, the devs are aware of it.
Halo: Campaign Evolved Known Issues (as of July 29, 2026):
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.
- 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.
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.
- Custom key bindings may reset after closing the title.
- Workaround: When setting custom key bindings, do not overwrite a key bind.
- Example: If you want melee to be on spacebar, change jump to an unused key, then change melee to spacebar.
- Workaround: When setting custom key bindings, do not overwrite a key bind.
- 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.
- AMD graphics cards may crash when using high refresh rate displays if VSync is turned on and the maximum frame rate is set to lower than 1/4th of the refresh rate.
- Workaround: Raise the maximum frame rate limit to a minimum of 1/4th your refresh rate, or disable VSync.
- Example: Using a 180Hz display must be set to 45 FPS or higher in-game while using VSync. 240Hz must be 60 FPS or higher, 360Hz must be 90 FPS or higher.
- Workaround: Raise the maximum frame rate limit to a minimum of 1/4th your refresh rate, or disable VSync.
- 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.
- NVIDIA RTX 50 series graphics cards may crash on missions Keyes and The Maw when using driver versions 610.47, 610.62, and 610.74.
- Turning on XeSS Frame Generation while an in-game maximum frame rate limit is set can cause the game to become visually frozen, with only occasional frame updates.
- Workaround: Use FSR or DLSS with Frame Generation instead of XeSS, turn off Frame Generation when using XeSS, or remove the in-game maximum frame rate limit.
- Using Frame Generation with XeSS upscaling may cause graphical issues and limit frame rates during cinematics.
- Workaround: Use Frame Generation with DLSS or FSR, or disable Frame Generation while using XeSS.
Once more info about the new patch is out, we’ll let our readers know.
Stay connected to MP1st and the latest news by following us on Bluesky, X, Facebook, TikTok, YouTube, and Google News.
