The first post-launch update for Halo: Campaign Evolved is live on every platform. It carries no new content, just bug fixes, stability work, and a handful of enemy AI corrections. Console players will see it labeled as update 16.754.404, and it lands as build 2026.07.25.1112544.
Quick answer: Install the July 29 update, then check that the game shows build 2026.07.25.1112544. Before updating, finish any mission you are in, because the patch invalidates mid-mission saved progress. Unlocked Missions and Rally Points are kept.

Download size by platform
The file is larger than you might expect for a fixes-only patch. Steam gets the heaviest download at 21 GB, while the Xbox app on PC is the lightest.
| Platform | Download size |
|---|---|
| Xbox Series X|S | 13 GB |
| PlayStation 5 | 7 GB |
| Microsoft Store / Xbox app (PC) | 4 GB |
| Steam | 21 GB |
Join readers who trust AllThings.How
Add us as a preferred source on Google so our practical guides show up first next time you search.
Add to Google Preferences →Read this before you install: mid-mission saves reset
The update includes changes that force any mid-mission saved progress to be cleared when it installs. If you are partway through a level, you will restart that level from its beginning after updating.
Your broader campaign progress is safe. Every Mission and Rally Point you have already unlocked stays available, so you can jump back in near where you left off rather than starting the campaign over. To avoid losing ground inside a level, reach a checkpoint or complete the current mission before you apply the patch.
Gameplay and enemy AI fixes
The most noticeable change for combat is the Plasma Pistol correction. A charged shot from an enemy will no longer instantly kill you when you have full health and shields, on any difficulty. That removes one of the cheaper deaths players kept running into.
Several enemy encounters that were behaving incorrectly now trigger as designed. The table below lists the mission-specific AI and behavior fixes.
| Mission | What changed |
|---|---|
| The Truth and Reconciliation | Jackals in the hangar hallway now actively patrol instead of standing idle. |
| Assault on the Control Room | Spec Ops Elites near Rally Point Delta now engage you as intended. |
| Assault on the Control Room | Enemies no longer walk into the Control Room exterior. |
| The Silent Cartographer | The Hunter pair now consistently engages after you approach the cartographer’s entrance. |
Stability, performance, and PC driver warnings
Much of the download weight goes toward stability. The mission Pillar of Autumn received general stability improvements, and The Maw is more stable when you watch or skip its opening cinematic while FSR is on with AMD graphics cards running driver versions 26.6.2 or 26.6.4.
On PC, every version now shows a warning at launch if it detects an AMD or NVIDIA GPU driver version with known problems, so you can update or roll back before you hit a crash. Players with large friends lists should also see less hitching on Windows PC, Steam, and PlayStation 5.
One account-linking annoyance is gone too. Xbox Gamertags now display throughout the linking flow for PlayStation and Steam players, rather than dropping out midway.
How to install the update and confirm it applied
Bugs that are still present
This patch does not clear everything. Several high-impact issues remain, and a few have workarounds worth knowing.
- Cinematics can stutter if your display refresh rate is not an even multiple of 30 Hz. Setting the display to 60, 120, or 240 Hz, enabling Game Mode, or turning off Variable Refresh Rate can reduce it.
- Audio and video can drift out of sync and briefly freeze if you pause and resume during a cinematic.
- In co-op, navigation markers do not advance until every Fireteam member passes them.
- On Two Betrayals, destroying the Banshee after the first generator can block progression.
- On PC, launching the game directly from the
HaloCampaignEvolved.exefile can start it without a Steam connection. Launch from the Steam library inside the Steam app instead. - Custom key bindings can reset after you close the game. When rebinding, move the existing key to an unused slot first rather than overwriting an active bind.
- NVIDIA RTX 50 series cards can crash on Keyes and The Maw with driver versions 610.47, 610.62, and 610.74. Updating to 610.88 or rolling back to 596.49 resolves it.
More patches are expected. If you hit a problem that is not already listed, you can report it to Halo Studios through the official Game Issue Report Form, which is how many of these fixes surfaced in the first place.





