Failed to Authenticate From External Provider PUBG Fix

Senior Writer — CS2 and Esports
failed to authenticate from external provider pubg

Few things sting more than clicking Play and getting hit with the failed to authenticate from external provider PUBG error while your squad is already loading in. The good news: this is almost always a handshake problem between Steam and the PUBG servers, not a ban or a broken account. Below we walk through the fixes that actually work, in the order that resolves it fastest.

What This Error Actually Means

The message shows up when the PUBG client cannot verify your Steam session with Krafton’s login service. Steam is the “external provider” in the message, and the game needs a clean token from it before it will let you into the lobby.

Common triggers include:

  • Steam is running in offline mode or the session has expired
  • A background Steam update or maintenance window
  • Corrupted PUBG login cache files
  • Region or network issues blocking the auth handshake
  • Third-party overlays or antivirus tools interrupting the token exchange

Bottom line: it is a login handshake failure, not a permanent account problem. You can almost always fix it yourself in under ten minutes.

Quick Fixes to Try First

Start here. These clear the error for most players without touching any files.

  • Fully close PUBG and Steam. Use Task Manager to end both processes, do not just click the X.
  • Restart Steam and sign in fresh. If Steam auto-launched offline, sign out and back in.
  • Launch PUBG from your Steam library, not from a desktop shortcut that may point to a stale executable.
  • Check the Steam status page. If Steam login services are down, no fix on your end will work until they are back.
  • Reboot your router. A fresh IP handshake often clears stuck tokens.

If the error is gone, you are done. If not, move to the deeper fixes below.

Verify the PUBG Game Files

Corrupted files inside the PUBG install folder are the second most common cause. Steam has a built-in tool to fix this.

  • Open your Steam Library.
  • Right-click PUBG: BATTLEGROUNDS and select Properties.
  • Go to the Installed Files tab.
  • Click Verify integrity of game files.

Steam will scan and re-download anything that is broken. This usually takes a few minutes, longer on a slow drive. When it finishes, launch the game again.

If you also hit a separate Steam-side startup error, our pubg failed to initialize steam walkthrough covers the sibling issue that sometimes appears alongside this one.

Clear the PUBG Auth Cache

PUBG stores login tokens locally. When one goes stale, the client keeps trying to reuse it and gets rejected by the server every time.

To clear it:

  • Close PUBG and Steam completely.
  • Open File Explorer and paste this into the address bar: %localappdata%\TslGame\Saved
  • Delete the Config folder (your keybinds will reset, so screenshot them first if you have custom binds).
  • Restart Steam, then launch PUBG.

The client will rebuild the folder with fresh files on first launch, which forces a new auth token from Steam.

Run Steam and PUBG as Administrator

Windows sometimes blocks the token handoff if either program lacks the right permissions.

  • Right-click the Steam shortcut, choose Properties, then Compatibility, and tick Run this program as an administrator.
  • Do the same for the PUBG executable inside the install folder.
  • Apply, then restart both.

This is a small change but it resolves the issue on a surprising number of setups, especially on Windows 11 machines with tight UAC settings.

Network-Level Fixes

If the quick fixes and file checks did not work, the problem is likely between your PC and Krafton’s login servers.

Flush Your DNS

Open Command Prompt as administrator and run:

ipconfig /flushdns


ipconfig /release


ipconfig /renew

This clears any stale DNS entries pointing at the wrong login endpoint.

Switch DNS Providers

Some ISPs route Krafton’s auth traffic poorly. Switching to a public DNS often clears it.

ProviderPrimarySecondary
Cloudflare1.1.1.11.0.0.1
Google8.8.8.88.8.4.4
Quad99.9.9.9149.112.112.112

Change these in your network adapter’s IPv4 settings, then reboot.

Check Region and VPN Settings

If you use a VPN, disable it before launching. If you recently moved regions or your ISP changed your assigned region, the login service may reject the token. Restart your router to pull a new IP, then try again.

For broader connection-side issues like rubberbanding and packet loss that can also surface as failed logins, our pubg lag fix guide is worth a read.

Disable Overlays and Background Apps

Overlays inject themselves into the login process and occasionally break it.

  • Turn off Discord overlay for PUBG.
  • Disable NVIDIA GeForce Experience overlay or AMD Adrenalin overlay.
  • Close MSI Afterburner, RivaTuner, and any capture software like OBS or ShadowPlay.
  • Temporarily disable third-party antivirus (Windows Defender is usually fine).

Launch PUBG. If it works, re-enable each one at a time to find the culprit.

Reinstall as a Last Resort

If none of the above clears the failed to authenticate from external provider PUBG error, uninstall the game through Steam and reinstall to a clean directory. Back up your replays folder first if you keep any.

This is time-consuming on a slow connection, so save it for last. It resolves edge cases where deep file corruption survives a Verify pass.

The Bottom Line

Right now, the fastest path to a fix is: restart Steam and PUBG, verify game files, clear the TslGame config folder, then flush DNS. That order clears the error for the large majority of players. If Steam itself is having a login outage, no local fix will help until services are restored, so always check the Steam status page before spending an hour on your own machine.

Once you are back in queue, brush up with our pubg tips and tricks roundup or dig into the pubg best weapons and attachments breakdown so you drop in ready. New to the game entirely? Start with our pubg beginner guide and the full pubg map rundown before you pick a hot drop.