Destiny 2 Stuck on the Loading Screen? Diagnose the Hang Before You Fix It

Most "stuck on loading screen" guides start handing out fixes immediately, but the loading screen in Destiny 2 is not one problem; it is a sequence. When you hit "play," the game talks to Bungie's login servers, pulls your account state, checks the large shader and material cache your client keeps locally, and only then streams you into the world. A hang can happen at any of those steps, and the fix for a stuck server handshake is completely different from the fix for a corrupted cache. Reading the screen tells you where you are stuck.

One extra clue helps: when the hang is network-related, Destiny 2 often pairs it with an error code on screen. A Baboon or Weasel code means the network connection dropped; a Bee code points at login authentication. If you see those, skip the file checks and go straight to the network steps below.

Where exactly is it hanging?

The most useful diagnostic in Destiny 2 is the small text at the bottom of the loading screen. It changes as the client moves through stages.

• "Contacting Destiny 2 servers," spinning indefinitely with no progress past the first bar. This is a network or login-stage hang. The client cannot complete the handshake with Bungie. Fix the connection, not the files.
• Progress bar moves, then freezes near the end, often around the character select or "retrieving character" stage. This usually points at your local cache or saved data being corrupted or too large.
• Bar fills, you reach orbit or a planet, then it freezes on the planet load. Commonly a graphics-driver or corrupted-game-file issue, because the world stream is failing to render.

Match your symptom to one of those before touching anything. Doing a full file verification when the real problem is a dead handshake wastes time; doing a network reset when your cache is corrupt does nothing.

If it hangs at the server handshake (network)

This is the most common "infinite loading" case, and it is maddening because the game itself is fine. The handshake fails when your route to Bungie's authentication servers is unstable, when a firewall or antivirus is silently blocking the connection, or when Bungie's own services are degraded.

First, rule out the server side. Check Bungie's official server status page and the @BungieHelp social account; if there is a widespread outage, no local fix will help and you should simply wait. If status is green, the problem is your path to the server.

Steps to clear it:

1. Fully exit Destiny 2 and the launcher, Steam or Epic, not just minimize it.
2. Temporarily disable any third-party antivirus or firewall rule you recently changed; these frequently block the auth handshake after an update.
3. Restart your router to drop a stale connection.
4. If the hang persists only on Wi-Fi, switch to wired; the login handshake is sensitive to even brief drops.
5. For routing-related instability, a network optimizer such as GearUP Booster can re-route the connection through a steadier path to Bungie's servers, which often gets past the stuck handshake when ordinary tweaks do not. On console, this is done through the GearUP Booster plugin or router-side setup rather than a PC app, since the console cannot run optimization software natively. This helps only when the cause is the network path; it will not fix a corrupted cache.

If it hangs near the end (local cache)

Destiny 2 keeps a large cache of shaders, materials, and previously visited-world data on your drive. Over months of play this cache can grow huge or corrupt, and the loading screen freezes while the client tries to read it.

The safe, non-destructive step is to clear the CVARS and cache folders:

• Close the game fully.
• Navigate to your Destiny 2 install folder, open the bin folder, and delete the cvars.xml file; it rebuilds automatically on next launch.
• For a deeper cache clear, back up then remove the cache and cache2 folders inside the game's local app data directory; the game recreates them when it starts.

This does not delete your characters or progress; that lives on Bungie's servers. It only forces the client to rebuild local data. After this, the end-of-load freeze usually disappears.

One more local cause worth ruling out before you blame files: a nearly full system drive. Destiny 2 writes temporary state during the load, and if your boot drive is at 99 percent capacity the write can stall and look exactly like a freeze. Freeing even a few gigabytes, or moving the install to an SSD, often resolves hangs that nothing else would.

If it freezes on the world load (files or drivers)

When the bar completes but the planet never renders, the issue is usually with the game's own files or the graphics layer.

• Verify game files. In Steam, right-click Destiny 2, Properties, Installed Files, Verify integrity of game files. In the Epic Games Launcher, use the three-dot menu, then Verify. This replaces any corrupted asset without a full reinstall.
• Update GPU drivers. A driver left over from a previous GPU generation is a known cause of world-load freezes. Install the latest NVIDIA or AMD driver cleanly.
• Run as administrator. Some players resolve persistent load hangs by launching the game with admin rights, which prevents permission conflicts when the client writes temp data.

Console: the hard reset fixes most hangs

On PlayStation and Xbox the same logic applies, but the cleanest first move is a power-cycle that fully clears the cache.

• Xbox: Hold the Xbox button, go to Profile and System, Settings, System, Console Info, Reset Console. Choose "Reset and keep my games and apps" to avoid a reinstall. A full power cycle, holding the power button about 10 seconds until it shuts off, then restarting, also clears the cache that causes load hangs.
• PlayStation: Turn off the console, unplug the power cable, wait at least 30 seconds, then plug back in and power on. That 30-second window is what actually drains the cached state; a quick restart from the menu often is not enough.

What a successful fix looks like

After the right fix, the loading screen should pass the "retrieving character" stage within a few seconds and drop you into orbit or the destination without a second freeze. If it still hangs at the exact same stage after you have addressed that stage's cause, the remaining culprit is almost certainly Bungie-side; check server status again before repeating local steps.

As a last resort when every stage fails, a clean reinstall removes any deep file corruption the verify step misses, though it means re-downloading the full client. Treat that as the final move, not the first, because the staged diagnosis above resolves the large majority of loading-screen hangs without it.