Launching the Battlefield 6 campaign on Steam is throwing a “Connection Lost” overlay for many players right now, often right on top of the opening cutscene. Multiplayer typically still connects, file verification hasn’t consistently helped, and the issue appeared after the 1.1.1.0 update. The team has acknowledged the problem and is investigating. Until a patch lands, the steps below outline workarounds that have helped some players, plus a few network checks worth doing so you don’t chase the wrong fix.

Symptoms and scope

Platform Mode Error Since What still works
Steam (PC) Campaign “Connection Lost” overlay during launch/cutscene Update 1.1.1.0 Multiplayer connects for many players

Battlefield 6 requires an active internet connection for all modes, including the campaign. A campaign launch failure can therefore present as a network error even if your internet is otherwise fine.

Quick fixes to try (Steam)

Work through these in order. Retest the campaign after each step.

  • Fully restart both apps: quit Battlefield 6, then exit Steam completely (system tray > Exit). Relaunch Steam, then the game.
  • Power cycle your network: unplug your modem and router for 30 seconds, power them back on, then reboot your PC.
  • Use Ethernet, not Wi‑Fi: a wired connection removes signal variability that can trigger handshake timeouts.
  • Disable VPNs and proxies: temporarily turn off any VPN, DNS proxy, or “secure” routing feature on your router or security suite.
  • Firewall allow‑list: ensure Steam and Battlefield 6 executables are allowed for both private and public networks in your firewall or security software.
  • NAT and UPnP: if you’ve disabled UPnP on your router or are using a strict NAT setup, re‑enable UPnP or test with a more open NAT profile.
  • DNS refresh: flush your local DNS cache and test alternative resolvers (for example, your ISP’s default versus a well‑known public resolver). If you change DNS in Windows, reboot before retrying.
  • Steam Beta Client: some players clear the error by switching Steam to its beta client. In Steam: Steam > Settings > Interface > Client Beta Participation > Steam Beta Update, then restart Steam.
  • Bypass the router: connect your PC directly to the modem to rule out router firmware or configuration issues. If the campaign launches, the router is the likely choke point.
  • Reinstall as a last resort: uninstall Battlefield 6, reboot, then install fresh to a local drive with ample free space.
Tip: Verifying game files and updating GPU drivers haven’t reliably resolved this specific campaign error for affected Steam users. Don’t spend too much time repeating those steps.

Why a single‑player campaign can show a network error

Battlefield 6 uses online services across modes, so a campaign launch still performs network checks and service handshakes. If the backend service path is failing—either broadly or for a subset of Steam users—you’ll see a generic connection overlay even if your internet is healthy and multiplayer works. That’s consistent with reports that the “Connection Lost” banner persists while the campaign cutscene plays in the background.

How to tell if it’s you or a broader issue

  • If multiplayer joins quickly on the same machine and only the campaign fails, that points away from a local outage and toward a mode‑specific service problem.
  • If bypassing your router fixes the campaign launch, your router is involved—check firmware, UPnP, and any QoS, security, or geo‑filtering features.
  • If nothing changes after all the steps above and you’re on Steam post‑1.1.1.0, you’re likely hitting the current campaign bug.

When to contact support

If you’ve tried the steps here and the campaign still shows “Connection Lost,” open a support ticket so the team can attach logs to the ongoing investigation. Start at EA Help and use the Contact Us flow for Battlefield 6. Include your platform (Steam), region, ISP, router model/firmware, whether Ethernet or Wi‑Fi, whether VPN/antivirus is installed, and a timestamp for the last failed attempt.

What to expect next

The issue is acknowledged and under investigation. A client hotfix or a server‑side update is the likely path to a permanent resolution. In the meantime, multiplayer remains available for most affected users, and the steps above are the best low‑risk workarounds until an official fix rolls out.