Destiny 2 isn't working: quick fixes before you reinstall

The trap is reinstalling first. Nine times out of ten the real fix is smaller, and a reinstall just costs you an hour of downloading.

Don’t blame your hardware yet

A crash is rarely your GPU’s fault. It is usually a server hiccup or a stuck update that never finished. Check the easy things before you touch drivers or settings at all.

Step one: check servers

Open the server status page and look for a live outage. If Bungie shows a known issue, you wait it out. You do not repair anything on your end during an outage window.

Step two: read the error code

Destiny throws named codes like Weasel or Baboon when it boots you. The code points straight at the cause. Our error codes guide decodes what each one means and the usual fix.

Step three: verify the install

A partial update breaks the launch sequence. Let your platform verify the game files and repair what is missing. On cloud setups, our GeForce Now guide covers the known quirks.

Step four: clear the cache

A corrupted cache stalls the login screen. Restart the client and the platform, then try again. If it still fails after that, our crashing fix guide goes deeper into the causes.

Step five: check the platform

Console and PC stores both push bad downloads now and then. Pause other downloads and retry the install. A clean reboot of the machine clears stuck background processes too.

Prevent it next time

Keep your client updated and avoid closing it mid-patch. Most “not working” cases trace back to an interrupted download. A clean shutdown saves the next session from the same headache.

When to contact support

If every step fails and others are playing fine, gather your error code and platform. Our server status guide is the first stop to rule out a wider outage before you open a ticket.