Halo Campaign Evolved PC Known Issues and Official Fixes
Updated 2026-08-02
On this page
Quick answer
Start Halo: Campaign Evolved from the Steam Library, not by opening HaloCampaignEvolved.exe directly. If the game warns that your GPU driver has known issues, treat that warning as actionable: compare your installed version with the official current issue list before changing graphics settings.
This page groups the official PC workarounds by symptom. It does not invent a universal crash fix or promise that a workaround resolves unrelated hardware faults.
Symptom-to-action table
| Symptom | Officially documented condition | First action |
|---|---|---|
| Steam sign-in failure, severe slowdown, or freeze | Game launched directly from HaloCampaignEvolved.exe | Close it and launch from the Steam Library |
| Crash before the splash screen on some Intel systems | Intel 13th/14th generation microcode issue and an outdated BIOS | Install the latest BIOS from the system or motherboard manufacturer |
| AMD crash on a high-refresh display | VSync enabled while the in-game maximum frame rate is set to 30 | Raise the frame-rate limit or disable VSync |
| RTX 50 crash in Keyes or The Maw | NVIDIA drivers 610.47, 610.62, or 610.74 | Move to an official recommended newer/rollback driver from the current notice |
| Game appears visually frozen with XeSS | XeSS Frame Generation enabled with an in-game maximum frame-rate limit | Disable that limit, disable Frame Generation, or use FSR/DLSS Frame Generation |
| Grain, haze, or oversized lens flares | Low DLSS upscaling quality together with Low graphics quality | Avoid that specific quality combination |
Launch through Steam, not the executable
The official known-issues post says launching directly from the executable in the installation folder may start the game without a Steam connection. The documented results can include:
- inability to sign in;
- severe performance problems;
- a freeze that must be closed through Task Manager.
Use this recovery sequence:
- close the affected game process;
- open the Steam client;
- open your Library;
- launch Halo: Campaign Evolved from its Library entry;
- confirm the Xbox account-linking flow shows your gamertag.
The July 29 update added Xbox gamertag display throughout Steam account linking, but it did not convert direct executable launch into a supported path.
Intel 13th and 14th generation launch crashes
Halo Studios attributes some pre-splash launch crashes on affected Intel 13th/14th generation processors to a pre-existing Intel microcode issue. The official direction is to install the latest BIOS supplied by your computer or motherboard manufacturer.
Do not flash a BIOS from an unrelated board model. Follow the hardware vendor's exact update procedure and power requirements. This article cannot determine whether a specific CPU has already degraded or whether another application crash has the same cause.
AMD high-refresh VSync crash
The documented combination is narrow:
- AMD graphics card;
- high-refresh-rate display;
- VSync enabled;
- in-game maximum frame rate set to 30.
Raise the maximum frame-rate setting or disable VSync. Do not treat this as evidence that all high-refresh AMD configurations are broken.
The July 29 update separately improved stability for the opening cinematic of The Maw when FSR is active on AMD driver versions 26.6.2 or 26.6.4. That improvement does not erase the distinct VSync/30 FPS issue above.
NVIDIA RTX 50 crashes in Keyes and The Maw
The official issue list identifies RTX 50-series crashes in Keyes and The Maw on driver versions 610.47, 610.62, and 610.74. Driver recommendations changed between official notices, so use the newest linked notice rather than freezing one version as permanent advice.
Before changing drivers:
- record the current NVIDIA driver version;
- confirm the crash occurs in one of the named missions;
- read the latest official issue list;
- install the current recommended update or rollback through an official NVIDIA channel;
- retest the same checkpoint.
XeSS Frame Generation freeze and cinematic artifacts
Two official XeSS combinations are documented:
- XeSS Frame Generation plus an in-game maximum frame-rate limit can make the image appear frozen with only occasional updates;
- Frame Generation with XeSS can produce graphical problems and restrict cinematic frame rates.
Official alternatives are to remove the in-game cap, turn off Frame Generation with XeSS, or use Frame Generation with FSR or DLSS instead.
If none of these symptoms match
Do not cycle through every workaround blindly. Record the platform, GPU, CPU, driver, mission, checkpoint, and exact symptom, then submit a Game Issue Report to Halo Support. Account problems belong with Microsoft Support; Steam-client problems that are not in-game issues belong with Steam Support.
Related guides
Sources
- Official Halo: Campaign Evolved Known Issues — PC launch, processor, GPU, upscaling and Frame Generation issues.
- Official July 29 Update — driver warning, account-linking display and launch stability changes.
Related Guides
Halo Campaign Evolved Cinematic Stutter and Audio Sync Fix
Apply the official refresh-rate, Game Mode and VRR workarounds for cinematic stutter, and avoid the documented pause/resume audio-video desync.
Halo Campaign Evolved PS5 Guide: Install, Accounts and Co-op
Current PS5 setup guide for Halo: Campaign Evolved, including digital or physical installation, Microsoft account linking, split-screen, online co-op and edition boundaries.
Halo: Campaign Evolved on Steam Deck – Verified Status
Halo: Campaign Evolved is Steam Deck Verified and SteamOS compatible. Review official compatibility, storage, controls, and honest performance boundaries.
Halo: Campaign Evolved PC System Requirements and Storage
Official Steam minimum and recommended PC requirements for Halo: Campaign Evolved, plus the 100 GB storage requirement and July 29 update download context.