The "unable to open bigfile.000" error in Shadow of the Tomb Raider
typically indicates that a critical game archive is missing, corrupted, or being blocked by system permissions. Core Troubleshooting Steps Verify Integrity of Game Files This is the most effective fix for missing or damaged components. : Right-click the game in your Properties Installed Files
The "Unable to open bigfile.000!" error in Shadow of the Tomb Raider
typically indicates that a core game data file is corrupted, missing, or blocked by system permissions. Primary Fix: Force a Clean Re-download
Simply verifying files sometimes fails if Steam or Epic Games thinks the corrupted file is "correct". Manually deleting the problematic files forces the launcher to replace them. Locate the Game Folder:
Steam: Right-click the game in your Library > Manage > Browse local files.
Epic Games: Usually located in C:\Program Files\Epic Games\Shadow of the Tomb Raider.
Delete "Bigfiles": Find and delete bigfile.000.tiger through bigfile.011.tiger. Verify Integrity:
Steam: Right-click game > Properties > Installed Files > Verify integrity of game files.
Epic Games: Click the three dots next to the game > Manage > Verify. Secondary Troubleshooting Steps
If deleting the files doesn't work, try these steps in order: Shadow of the Tomb Raider won't launch : r/SteamDeckPirates shadow of the tomb raider unable to open bigfile.000
The "Unable to open bigfile.000" error in Shadow of the Tomb Raider
typically indicates that a core game file is corrupted, missing, or being blocked by system security.
These video guides provide visual walkthroughs for verifying game files and adjusting system settings to resolve bigfile errors:
Facing the "unable to open bigfile.000" Shadow of the Tomb Raider
often feels like a brick wall, but it is typically a symptom of one of three things:
data corruption, permission conflicts, or a hardware communication hiccup
Here is a deep dive into the most effective solutions gathered from community experts and technical logs. 1. The "Nuclear" Validation Method Standard file verification often skips over files it
are fine. To force a true refresh, you must manually intervene: Locate the Files : Navigate to your game installation folder (e.g., SteamLibrary/steamapps/common/Shadow of the Tomb Raider Delete the Culprits bigfile.000.tiger bigfile.011.tiger and delete them. Verify Integrity
: Return to your library (Steam/Epic), right-click the game, and select Verify Integrity of Game Files
. The launcher will see they are missing and download fresh, clean versions. 2. Bypass Permission & Security Blocks Windows Defender or third-party antivirus software like Bitdefender often flags these massive The "unable to open bigfile
files as suspicious or locks them during the game's startup sequence. Whitelist the Folder
: Add the entire game folder as an exception in your antivirus settings. Run as Admin : Right-click your game's file, go to Properties > Compatibility , and check Run this program as an administrator Disable Fullscreen Optimizations : While in the Compatibility tab, check Disable full-screen optimizations
, which has solved launch-related file errors for many users. 3. Address "Bitrot" and Drive Issues
If the error persists after a reinstall, your drive might be struggling to read that specific physical sector. Move the Install
: Use the built-in "Move Install Folder" tool in Steam to shift the game to a different drive (ideally an SSD). This forces the OS to rewrite the data to healthy sectors. Check Disk Space : Ensure you have at least 15–20GB of
free space beyond the install size. The engine often requires a large "swap" space for unpacking these bigfiles during runtime. 4. Epic Games Specific Fix: Clear the Webcache If you are playing the Epic Games Store
version, the launcher's own cache can cause "black screen" or bigfile errors: Close Epic Games completely. %localappdata% , and navigate to EpicGamesLauncher/Saved/ Delete the folder and restart the launcher.
Are you seeing a specific "Disk Write Error" message along with the bigfile notification, or does the game simply crash to desktop?
Providing this detail can help pinpoint if the issue is your drive's health Windows permission
If none of the above works, the nuclear option is a complete reinstall. Before you uninstall, back up your save files located in:
C:\Users\[YourName]\Documents\Shadow of the Tomb Raider\[RandomNumbers]\save1 Final Resort: The Clean Install If none of
Delete the local files and let the launcher redownload the game fresh. This ensures a clean, uncorrupted bigfile.000 is created.
Summary: The "Unable to open bigfile.000" error is almost always a security conflict rather than a broken game. Check your antivirus quarantine first—it usually saves you a 40GB redownload. Happy raiding
If your hard drive has bad sectors, the bigfile.000 archive may become corrupted every time you try to install or verify it.
Corrupt cache can cause file mismatches.
You’ve just installed Shadow of the Tomb Raider. You’ve got your popcorn ready, the lights are dimmed, and you’re eager to watch Lara Croft navigate jungle traps and deadly tombs. You hit “Play.”
Then, the screen goes black. A small error box pops up:
"Unable to open bigfile.000"
Few error messages are as cryptic—or as infuriating. That seemingly random file is actually the backbone of the entire game. It contains the bulk of the game’s assets: textures, audio, levels, and models. If your PC can’t read it, Lara isn’t going anywhere.
Don’t worry, though. In most cases, this error is fixable without reinstalling 40GB of data. Let’s walk through the solutions.
If you still see the error, the problem might be deeper.
Move the game to a different drive. If your hard drive has bad sectors, the file may be unreadable. Try moving the installation to an SSD or a different HDD via your launcher (Steam has a built-in "Move Install Folder" feature).
Check your file path length. This is rare, but if your Windows username is very long and the game is installed in C:\Users\ReallyLongName\Documents\My Games\..., Windows can hit a path character limit. Try moving the game to a root folder like D:\SteamGames\.