What causes a Steam depot build missing files after upload?

The depot build VDF's file mapping did not include the build output directory or used the wrong path, so SteamPipe uploaded an incomplete depot and players download a build without those files.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix a Steam Depot Build Missing Files After Upload

Quick answer: Point the depot's FileMapping at the correct build output, include all needed subfolders, and verify the uploaded depot in the Steamworks build console.

Players report missing files or a failing launch after a Steam update because the depot upload did not include everything. Fixing the SteamPipe file mapping fixes it.

How to fix it

1. Map the full build output

In the depot build .vdf, set FileMapping's LocalPath to your packaged output with a recursive pattern (e.g. * and recursive 1) so every file and subfolder is uploaded.

2. Check excludes and depot config

Review any FileExclusion rules and confirm each depot in the app build VDF references the right depot ID. A stray exclusion or wrong depot drops files from the shipped build.

3. Verify the build before setting live

After running steamcmd run_app_build, inspect the build's file list in the Steamworks build console and set it live only once the file count and paths look complete.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.