Two Betrayals Banshee Softlock
The highest-priority community blocker is on Two Betrayals. After you destroy the first generator, the mission expects a Banshee to remain available for the next leg of the level. If you destroy that Banshee—or it despawn from combat—you can softlock the mission with no clean forward path.
Tough Luck and Mythic Skulls make the problem worse because you still need the Banshee to progress on those routes. A second Banshee on the bridge sometimes spawns, but players report it is unreliable; do not plan your run around it. If you are stuck, reload your last checkpoint before the generator fight and preserve the first Banshee.
- After the first generator — do not destroy the Banshee
- Tough Luck + Mythic — Banshee is still required
- Bridge Banshee — unreliable backup; reload checkpoint if stuck
Official Issue List
Halo Support and Halo Waypoint track verified launch issues below. Patch 16.754.404 (July 29, 2026) fixed Plasma Pistol overkill, several campaign AI bugs, and parts of The Maw / Pillar of Autumn stability—see /patch-notes/ for the full changelog. This fan wiki mirrors community findings alongside the open list.
| Issue | Status / Workaround |
|---|---|
| Two Betrayals Banshee softlock | Still open — avoid destroying the first post-generator Banshee; reload checkpoint if stuck |
| Plasma Pistol charged shot instant kill | Fixed in 16.754.404 |
| Cinematic stutter at high refresh | Open — try 60 / 120 / 240 Hz, enable Game Mode, turn off VRR on display or GPU |
| Cutscene pause desync | Open — avoid pausing mid-cinematic |
| Suspend during cinematic overlap | Open — do not suspend mid-cutscene |
| Truth and Reconciliation audio pop | Open — brief popping during gameplay |
| Steam PC launch | Open — start from the Steam client library, not the .exe shortcut |
| AMD FSR + The Maw intro cinematic (drivers 26.6.2 / 26.6.4) | Partially improved in 16.754.404 — switch upscaler or roll back to 26.6.1 if needed |
| Co-op navigation markers | Open — markers wait for the whole fireteam; stick together |
| PC custom key bindings reset | Open — move old bind to unused slot before overwriting |
| XeSS Frame Generation + in-game FPS cap | Open — use FSR/DLSS FG or disable frame cap with XeSS FG |
PC & Platform Access
Nvidia RTX 50-series GPUs on driver builds 610.47, 610.62, and 610.74 can crash during Keyes and The Maw. Update to Nvidia driver 610.88 or roll back to 596.49 before a Legendary push—patch 16.754.404 adds a launch warning but does not remove the crash path.
Xbox “too early” lockouts from the Early Access window are resolved for entitled editions. On Steam, some players see Digital Story and Art Collection launching instead of the campaign—restart Steam or temporarily disable that DLC entitlement, then launch from the library. PS5 disc copies need the day-one patch before first play; offline play is fine once that patch is installed.
- RTX 50-series — update to Nvidia 610.88 or roll back to 596.49 if Keyes / Maw crash
- Xbox Early Access — “too early” lockouts cleared for Premium / Collector's
- Steam wrong app — restart client or disable Digital Story and Art Collection DLC
- PS5 disc — install day-one patch first; offline OK afterward
Support & Wiki Notes
For official status, patch timing, and entitlement help, follow Halo Support and Halo Waypoint first. This site is a fan wiki—we summarize verified reports so fireteams can plan around blockers, not replace 343 Industries or Halo Studios support channels.
When a hotfix ships, we update the Updates page and cross-link mission notes where a bug affects routing—Two Betrayals on the Missions page, driver workarounds alongside PC settings chatter. If something here looks outdated, compare against the latest Waypoint post before you wipe a checkpoint.