Halo: Campaign Evolved

Halo: Campaign Evolved server and login issues: how to actually get in

By the New Games Guide team · Last updated 2026-08-02

If Halo: Campaign Evolved will not get you past sign-in, the most valuable thirty seconds you can spend is working out whose problem it is. Launch-window connection errors are usually service-side, and every local fix you try during an outage is wasted effort that feels like progress.

This guide is ordered accordingly. The first section tells you whether to keep reading. The rest are the fixes that matter when the problem really is on your side, cheapest first.

First: is it you or is it them?#

Three checks, in this order. They take two minutes and they determine everything that follows.

1. Check the official service status page. Halo Support and Halo Waypoint publish service status, and the platform holders publish their own — Xbox Live status and the PlayStation Network status page. You need both: the game's own services and your platform's account service. A green game service with a degraded platform sign-in produces exactly the same error message as the reverse.

2. Check whether other people are failing right now. Player-reported outage trackers and the game's subreddit are crude, but a vertical spike in reports within the last hour is a strong signal. If thousands of people started failing at the same minute you did, it is not your router.

3. Test one other online game or app on the same machine. If something else signs in normally, your general connectivity is fine and the problem is narrower — either this game's service, or this game's specific configuration on your machine.

Fix 1 — Close the game properly, not just the window#

The single most common cause of a stuck sign-in after a failed first attempt is that the game process never exited. It is still holding a half-open session, and the new launch is queuing behind it.

• Windows: open Task Manager, go to the Details tab, and end every process belonging to the game. Alt-F4 and clicking the X frequently leave a background process running.
• Xbox: highlight the game on the dashboard, press the Menu button, choose Quit. Do not just press the Xbox button and open something else — that suspends the game, it does not close it.
• PlayStation: highlight the game, press Options, choose Close Game.

Then relaunch. If you were seeing an endless spinner, this alone clears a surprising share of cases.

Fix 2 — Refresh your account session#

The game does not sign you in; your platform does, and the game consumes that token. If the token is stale — which happens after a long suspend, a password change, or a service blip — the game gets a rejection it reports as a generic connection error.

1. Sign out of your platform account entirely (Xbox profile, PSN account, or the PC storefront you launched from).
2. Restart the console or the storefront client.
3. Sign back in and confirm you are signed in before launching the game.
4. Launch.

On PC specifically, if you use both the Microsoft Store/Xbox app and Steam, make sure you are signed into the Xbox app with the account that owns the game — a mismatch here produces sign-in failures that look like server errors.

Fix 3 — Power-cycle your network, properly#

"I restarted my router" usually means someone used the reboot option in its web interface, which does not clear the condition this fixes.

1. Unplug the router and the modem from power.
2. Wait a full 60 seconds. This is not superstition — it lets capacitors drain and forces the device to re-negotiate rather than restore its previous state.
3. Plug the modem in first, wait for it to fully sync (all lights steady).
4. Plug the router in, wait for it to fully come up.
5. Restart your console or PC, then try the game.

This resolves stale NAT table entries and lease problems that no amount of in-game retrying will clear.

Fix 4 — Change your DNS#

Your ISP's DNS resolver may be returning stale or slow answers for the game's authentication endpoints, particularly during a launch when those endpoints are being reconfigured under load.

Set these on the console's network settings or in your PC's adapter properties, then flush your resolver cache on PC:

ipconfig /flushdns

Retry the game. If it works, leave the DNS setting in place — there is no downside.

Fix 5 — Check NAT type and open the right ports#

A strict or Type 3 NAT will not usually block sign-in on its own, but it will block co-op and can cause the connection to fail after authentication succeeds.

Check your NAT first (console network settings will report it). If it reports Strict/Type 3:

• Enable UPnP on your router. This is the fix for most people and requires no port lists.
• If UPnP is unavailable or your router's implementation is unreliable, forward the standard platform ports to your console's reserved local IP address.
• Do not put your console in the DMZ as a first resort. It works, and it exposes the device more than necessary.

Fix 6 — Disable overlays and injectors (PC)#

Third-party overlays hook into the game process and are a recurring cause of both crashes and failed handshakes on PC. Turn all of them off, then test:

• Discord overlay
• GPU vendor overlays (NVIDIA app / GeForce Experience, AMD Adrenalin)
• Steam overlay, for this game specifically
• RGB and peripheral suites that inject overlays
• Recording and streaming software with capture hooks
• Third-party FPS counters and frame-limiters

Re-enable them one at a time afterwards if you want to know which one it was.

Fix 7 — Repair rather than reinstall#

Reinstalling is a two-hour download that rarely helps. Repair does the same job in minutes.

• Steam: right-click the game → Properties → Installed Files → Verify integrity of game files.
• Xbox app / Microsoft Store on PC: Windows Settings → Apps → the game → Advanced options → Repair, then Reset if Repair does not help.
• Console: there is no repair option; use the platform's "manage game" screen to remove and re-add only the failing component (campaign pack, language pack) rather than the whole title.

Fix 8 — Clear the local cache#

Stale local configuration and cached credentials cause sign-in loops that survive reinstalls, because reinstalling does not touch these folders.

On Windows, close the game and clear cached data under:

%LOCALAPPDATA%\Packages\   (Microsoft Store version — the game's package folder)
%LOCALAPPDATA%\<game folder>\Saved\Config

Rename the folder rather than deleting it, so you can put it back if this was not the cause. On console, the equivalent is a full power cycle: hold the power button for ten seconds until the console fully shuts down, wait thirty seconds, then start it again. This clears the persistent cache; a normal restart does not.

Fix 9 — Check for parental controls and account restrictions#

If the account is a child account or is part of a family group, online multiplayer and communications may be restricted at the platform level. The game reports this as a connection failure rather than a permissions error, which sends people down entirely the wrong path.

Verify on the platform's family settings page that the account has multiplayer and online access enabled, then sign out and back in for the change to take effect.

Fix 10 — Try a different network#

This is a diagnostic, not a fix, and it is the fastest way to isolate the problem. Tether the console or PC to a phone hotspot and try to sign in.

• Works on hotspot, fails on home network — the problem is your router, ISP routing or local firewall. Go back to fixes 3 and 5.
• Fails on both — the problem is the account or the service. Go to fix 11.

Fix 11 — When it is the account, not the machine#

If you have reached here and nothing has worked, and it fails on a second network and ideally a second device, the issue is account-side. At that point support is the correct next step, and you will get a faster resolution if you arrive with:

• The exact error code or message, photographed or copied verbatim
• Your platform and region
• The time (with timezone) it started
• What you have already tried, from this list
• Confirmation that it also fails on a different network

Vague reports get generic replies. A report with those five things gets escalated.

Error messages and what they usually mean#

FAQ#

Why does the game say the servers are down when the status page says they are up?#

Status pages are updated by humans and lag the actual incident by anywhere from a few minutes to an hour at launch. They also report regionally — a service can be healthy globally and degraded in your region. Treat a green status page as weak evidence, not proof, during the first week of a launch.

Can I play the campaign offline while sign-in is broken?#

You need at least one successful sign-in to establish your session. After that, offline behaviour depends on the release's implementation, and achievements and progress sync will queue until you reconnect. If you have never successfully signed in on that device, offline play is not a workaround.

Does reinstalling fix login issues?#

Almost never, and it is the most expensive thing you can try. Sign-in failures are network, account or cache problems, and a reinstall touches none of those — cached credentials and config folders survive it. Repair (Fix 7) and cache clearing (Fix 8) do the useful part in a fraction of the time.

Will a VPN help me connect?#

Occasionally, and unpredictably. A VPN can route around bad ISP peering, which genuinely helps some players during launch congestion. It can also break platform sign-in outright, add latency and trip anti-fraud checks on your account. Try it as a late-stage diagnostic, not an early fix, and turn it off once you are in.

My friend can play and I cannot, on the same connection. What is different?#

If you are on the same network, the variable is the account or the device. Test your account on their device — if it fails there too, it is the account (Fix 9, Fix 11). If your account works on their device, it is your device's cache or configuration (Fix 8).