Destiny 2 Error Code MARMOT Fix — Corrupted Files & Verify Loop
Destiny 2
Destiny 2 Error Code MARMOT — Corrupted Game Files & Endless Steam Verify Loop
You launch Destiny 2 and before you even get to orbit, a full-screen error hits: MARMOT. Bungie's own error description tells you game files are corrupted and need to be repaired. You click through, Steam's verify runs, it finds and replaces files — and then MARMOT comes back on the next launch. You're stuck in a loop: verify, launch, MARMOT, verify again. Sometimes it hits after a Destiny 2 update that didn't download cleanly. Sometimes it appears out of nowhere after weeks of the game running fine. The full-screen takeover and the word MARMOT are Bungie's error reporting system flagging a file hash mismatch between what's on your drive and what their servers expect to see. It's not always every file — sometimes it's a single package file inside Destiny 2's packages folder that keeps getting flagged. Steam's verify replaces it, but something prevents the replacement from sticking: a locked file, an AV quarantine, or a permissions issue on the folder. The loop continues until you address whatever's blocking the replacement. Windows 10 and 11 are both affected. It's Steam-exclusive on PC, so the fix is entirely within that ecosystem.
Deep Dive: Why This Error Occurs
MARMOT is Bungie's error code for a local file integrity failure — specifically, a mismatch between the hash of a file on your drive and the hash Destiny 2's launcher expects. Every .pkg file in Destiny 2's packages folder has an expected hash, and at launch the game checks them all. One bad file triggers MARMOT. The verify loop happens when the fix keeps undoing itself. Steam replaces the bad file correctly, but something on your system changes it again before the next launch. The two most common culprits are antivirus tools — which scan and quarantine the newly-downloaded file before Destiny 2 can read it — and file permission issues that mean Steam's replacement never actually writes to disk, even though Steam reports success. The drive health angle is less obvious but important. If the sector of your drive that holds a specific .pkg file is physically failing, any data written to that sector will corrupt again within seconds. Steam's verify will always report that it replaced the file — and technically it did — but the replacement is already bad by the time Destiny 2 checks it on next launch. Bungie patches their error code system regularly but MARMOT specifically is PC-side, not server-side. Bungie can't fix it for you — it's your local file system that's the problem.
Primary Root Causes
* **Partially downloaded or corrupted update package** — Destiny 2 updates frequently and its package files are large. An interrupted or failed update leaves one or more .pkg files in a bad state that triggers MARMOT on every launch. * **Antivirus quarantining replacement files during verify** — Steam replaces the corrupted file, AV scans it immediately and quarantines it again. MARMOT fires on next launch because the file is missing again. The loop is entirely AV-driven. * **Write permissions issue on the Destiny 2 packages folder** — if Steam doesn't have write access to \Destiny 2\packages\, it can't replace corrupted files even when verify identifies them. The verify says it fixed things, but nothing actually changed on disk. * **Corrupted Steam download cache** — Steam's own download cache can become corrupted independently of the game files, causing every download — including verify replacements — to land in a broken state. * **OneDrive or cloud backup tool locking game files** — OneDrive, Google Drive Backup, and similar tools that sync the Steam folder can lock .pkg files during upload, making them read-only at the moment Destiny 2 needs to write to them. * **Failing or fragmented drive** — a bad sector on the drive where Destiny 2 is installed will corrupt any file written to that sector, including fresh downloads during verify. The verify loop never ends because the replacement file corrupts again immediately. * **Shader cache conflict** — a stale or corrupted shader cache from a previous Destiny 2 version can trigger MARMOT on first launch after a major update, even if the actual package files are fine.
How to Fix This Error (Step-by-Step)
Add Destiny 2's full install folder to your antivirus exclusions before doing anything else. Go to Windows Security → Virus & threat protection → Manage settings → Exclusions → Add an exclusion → Folder and add C:\Program Files (x86)\Steam\steamapps\common\Destiny 2\. Check the AV quarantine vault for any .pkg files and restore them.
Run Steam as administrator. Close Steam fully, right-click the Steam shortcut on your desktop, select Run as administrator, then launch Destiny 2. This gives Steam the write permissions it needs to replace files in protected directories without silently failing.
Disable OneDrive sync for your Steam folder if OneDrive is active. Open OneDrive settings → Account → Choose folders and make sure your Steam directory isn't selected for sync. File locking from cloud backup tools is one of the most common causes of the verify loop.
Clear Steam's download cache. In Steam go to Settings → Downloads → Clear Download Cache. Steam will log you out and back in. This forces a fresh download pipeline for any subsequent verify operations.
Verify Destiny 2's files with admin Steam running. Right-click Destiny 2 in your Steam library → Properties → Installed Files → Verify integrity of game files. Let it complete fully, then launch immediately without closing Steam between verify and launch.
If MARMOT returns after verify, identify which file keeps getting flagged. Look in Steam's verify output for the specific file count being replaced — then navigate to C:\Program Files (x86)\Steam\steamapps\common\Destiny 2\packages\ and check if any .pkg file shows a date that doesn't match the others. Delete that specific file and re-verify to force a fresh download of just that package.
Run a drive health check on the disk Destiny 2 is installed on. Open Command Prompt as administrator and run chkdsk D: /f /r (replace D: with your drive letter). Schedule it for next reboot if prompted. A bad sector is the underlying cause when MARMOT returns after every single verify with no AV or permissions explanation.
Essential Troubleshooting FAQs
Is MARMOT always a local file issue, or can Bungie's servers cause it?
MARMOT on PC is always a local file integrity issue — it fires before Destiny 2 even connects to Bungie's servers. Server-side problems produce different error codes like BEAVER or WEASEL. If you're getting MARMOT, it's your drive or your AV, not Bungie's backend.
I've verified three times and MARMOT keeps coming back. Do I need to reinstall?
Not necessarily — full reinstall is a last resort. First confirm your AV isn't re-quarantining the file after each verify (check the quarantine vault after every verify run). If the quarantine vault is clean and MARMOT persists, run chkdsk on the drive. Only reinstall after confirming the drive is healthy and AV isn't interfering.
The verify says 0 files needed replacing but MARMOT still fires. What's happening?
This usually means the shader cache is the culprit rather than a package file. Go to C:\Users\YourName\AppData\Roaming\Bungie\DestinyPC\ and delete the prefs folder, then relaunch. If MARMOT still fires with a clean verify, reinstall the Visual C++ 2022 redistributables from Microsoft — a corrupted runtime can produce false MARMOT triggers in rare cases.
After fixing MARMOT, Destiny 2 crashes with a different error code. What now?
MARMOT is gone, which means the file issue is fixed. A new error code is a separate problem. Check Bungie's error code lookup at https://www.bungie.net/en/Help/Troubleshoot — their tool gives specific steps for each code. The new code will point you at the right fix.
How do I stop MARMOT coming back after future Destiny 2 updates?
Keep your AV exclusion on the Destiny 2 folder permanently. After every major Destiny 2 update, launch Steam as administrator before playing — write permission failures are most likely to happen right after an update replaces package files. If you're on an HDD, run chkdsk every few months to catch developing bad sectors before they cause the loop again.
Summary
The AV exclusion and running Steam as admin together fix MARMOT for the vast majority of players. Add the Destiny 2 folder to your exclusions, check the quarantine vault for any recovered .pkg files, then verify with Steam running as admin. That breaks the loop. If MARMOT survives that, clear Steam's download cache under Settings and re-verify. Check whether OneDrive is syncing your Steam folder — disable that if it is. For a loop that won't die after everything above, run chkdsk on your drive. A physically failing sector is the one cause no software fix touches. If chkdsk finds errors, that drive needs replacing — no amount of verify runs will fix a bad sector.
