Problem: PC players can’t log in (or get random disconnects) in multiple games using Epic Online Services — tied to a Windows root certificate change

Published: 2026-01-29 00:12 (local time)

Quick Summary

Many Windows PC players report sudden login failures / connection errors in games that use Epic Online Services (EOS), even though their internet is fine.
Research points to a root certificate transition (“Starfield Class 2” to “Starfield Services Root G2”) starting October 1, 2025, where some PCs/games fail the trust check.
The most reliable fix is updating Windows fully (so the new root certificate is installed).
If you can’t update Windows, there are a few real-world workarounds (launcher update + launch once, fixing system time, clean network stack reset, testing a different network, etc.).
This problem is hard because it may look like a “game server outage,” but it can be a local trust/certificate issue that persists until your PC trusts the new certificate.

What’s happening

Over the past few months (especially since the certificate transition date of October 1, 2025), a recurring, widespread complaint from Windows PC players is that certain games suddenly cannot connect to Epic Online Services (EOS). The symptoms vary by game, but the pattern is consistent: you launch a game and get stuck on login/authentication, receive “unable to connect” style errors, or get disconnected shortly after connecting. Players often report that their other online games work, and that the issue can appear “random” across different titles.

This is particularly confusing because not all EOS-based games break for every person. Research suggests the impact depends on (1) whether Windows has the new trusted root certificate and (2) whether the game is using an older EOS SDK version. Third-party support documentation explicitly warns that Windows systems missing the new certificate may fail to connect, and that games using older EOS SDK versions are more likely to be affected.

Likely causes (what research suggests)

Windows trust store missing the new EOS root certificate

PLAION Player Support describes a planned EOS certificate update starting October 1, 2025, replacing “Starfield Class 2” with “Starfield Services Root G2.” If your Windows machine doesn’t have the new root installed (often because Windows updates are paused/blocked), EOS connections can fail.
Older EOS SDK versions inside specific games

The same documentation notes that Windows games using EOS SDK versions earlier than 1.17.1.3 are affected. That means two players on identical Windows builds might see different results depending on whether a given game has updated its EOS integration.
Local configuration issues that make certificate validation worse

Even when the underlying issue is certificates, “support-like” factors can amplify it: incorrect system date/time, cached launcher/session data, or a corrupted local networking stack can prevent a clean handshake. Community troubleshooting threads frequently converge on resetting caches and the network stack when basic steps fail.

Solutions & Workarounds

1) Fully update Windows (most effective)

Who it helps: Windows 10/11 PC players who can install updates (most users).

Close the game and the Epic Games Launcher.
Open Windows Update and install all pending updates (including “optional” cumulative updates if available).
Restart your PC (don’t skip the reboot).
Launch the game again and test login.

Risks / tradeoffs: Updates can take time and occasionally introduce unrelated issues (rare, but possible).

Stop and contact official support when: Windows reports it’s up to date, but EOS games still fail consistently; at that point, provide support your Windows version/build and the exact error text.

2) Update Epic Games Launcher and open it once (forces some mitigations)

Who it helps: Players with the Epic Games Launcher installed (even if the affected game is on another launcher).

Open Epic Games Launcher.
Let it update if prompted.
After updating, fully close it (exit from system tray), then reopen it once.
Try the affected game again.

Risks / tradeoffs: Minimal; mostly time cost.

Stop and contact official support when: You cannot update the launcher or it crashes repeatedly.

3) Verify system date/time and time zone (certificate checks can fail if time is wrong)

Who it helps: Any Windows user; especially PCs that dual-boot or have CMOS battery/time drift.

Windows Settings > Time & language.
Enable automatic time and automatic time zone (if available).
Click “Sync now,” then reboot.
Retry login.

Risks / tradeoffs: If you need manual time for niche setups, this may conflict.

Stop and contact official support when: Time settings keep reverting (possible admin policy / domain-managed PC).

4) Reset network stack (Winsock/IP/DNS), then reboot

Who it helps: Windows users seeing persistent EOS connection errors after updating Windows.

Open Command Prompt as Administrator.
Run: ipconfig /flushdns
Run: netsh winsock reset
Run: netsh int ip reset
Reboot your PC and test again.

Risks / tradeoffs: May reset certain network settings; VPNs and some enterprise configs might need reconfiguration.

Stop and contact official support when: Your PC is work/school-managed or you rely on custom network policies.

5) Clear Epic Launcher + game cache (reduces “stale session/token” problems)

Who it helps: PC players who suspect corrupted cached login/session data.

Exit Epic Games Launcher completely (system tray > Exit).
Back up then delete the launcher cache folder: %localappdata%\EpicGamesLauncher\Saved
For the game, back up then delete its Saved folder (location varies by game; many store it under %localappdata%).
Reboot, then sign in again.

Risks / tradeoffs: Can remove local settings; some games may rebuild shaders/settings on next launch.

Stop and contact official support when: The game uses cloud saves and you’re unsure what is safe to delete.

6) Test a different network path (mobile hotspot or different router) to isolate ISP/router interference

Who it helps: Players who can’t tell whether it’s certificates vs. networking.

Try connecting via a phone hotspot temporarily.
If it works on hotspot but not home network, reboot modem/router and disable custom DNS filtering temporarily.
Retry on the home network.

Risks / tradeoffs: Hotspots can use metered data; NAT type may be worse.

Stop and contact official support when: Only one network fails consistently—this points to router/ISP filtering, not the game.

Prevention (so it doesn’t come back)

Keep Windows updated so root certificates refresh automatically.
Avoid “debloating” tools that disable Windows Update or certificate services unless you fully understand the impact.
Keep the Epic Games Launcher updated (even if you mainly play on Steam) because it may include mitigations and updated sign-in components.
Keep system time set to automatic, especially on laptops and dual-boot systems.

FAQ

Q: How do I know if it’s an Epic outage vs. my PC?
A: If friends can log in and the official status page shows normal, but your EOS-based games fail consistently, it’s more likely local (Windows trust store/time/network stack). If everyone is failing at once, it’s more likely an outage.

Q: Why do only some games break?
A: Research suggests the risk is higher for games using older EOS SDK versions; newer integrations may be less affected.

Q: I updated Windows and it still fails—what next?
A: Reboot, confirm system time, then try the network stack reset and cache clearing. If it still fails, test a different network to separate local vs. router/ISP issues.

Q: I can’t update Windows (locked-down PC). Am I stuck?
A: You may need your administrator to allow updates or to install the required certificate trust changes. Epic’s guidance indicates updating Windows is the primary fix, with alternative certificate-related steps when updates aren’t possible.

Q: Does reinstalling the game help?
A: Sometimes, but it’s usually slower than fixing Windows/certificates/time/network stack. Reinstall only after you’ve tried the quicker steps.

Q: When should I contact official support?
A: When Windows is fully updated, time is correct, you’ve rebooted, and multiple EOS games still cannot connect—provide your Windows version/build, error message, and whether it works on a different network.