Interactive troubleshooting
Fix Progress
Try the steps in order. Open each step, follow the instructions, then mark the step that solved the problem.
Open the Steam menu and select Exit. Confirm that Ste:contentReference[oaicite:0]{index=0}resume the download from Library > Downloads. If several games show the same error, pause the queue and test only one title.
Verification:
The download leaves the queued state, disk and network activity resume, and the Manifest Unavailable message does not return.
Go to Steam > Settings > Downloads. Open Download Region and select the next nearby region rather than a distant continent. Restart Steam when prompted, then retry the affected game.
Verification:
Steam connects through a different content route and begins downloading the game or update without the manifest error.
Open Steam > Settings > Downloads > Clear Download Cache. Confirm the action and sign in again after Steam restarts. This removes cached download configuration but does not uninstall installed games.
Verification:
After signing in, start the same download and confirm that Steam reacquires the update metadata instead of displaying Manifest Unavailable.
Exit Steam, disconnect any VPN, and turn off manually configured proxy settings. On Windows 11, open Settings > Network & Internet > Proxy and disable Use a proxy server unless your school or workplace requires it. Reopen Steam and test again.
Verification:
The download works on the direct connection, or it works when the computer is connected to a phone hotspot or another trusted network.
Open Steam > Settings > Storage. Select the drive that contains the affected game, open the three-dot menu, and choose Repair Folder. Approve the administrator prompt if Windows displays one.
Verification:
Steam completes the repair without a write-permission warning, and the download can create or update files in the selected library.
Use this step when only one game fails. Right-click the game, select Properties > Betas, and set Beta Participation to None unless the publisher requires a specific branch. Then open Installed Files and select Verify integrity of game files.
Verification:
Steam reports that the files were validated, downloads any required replacements, and the title no longer requests an unavailable branch manifest.
Keep the firewall enabled. Add Steam.exe and SteamService.exe to the allowed-app list in Windows Security or your third-party security suite. Check quarantine history for blocked Steam files, then restart the computer.
Verification:
Steam can sign in, open Store pages, and download game data without being blocked. Re-enable any protection you temporarily paused for testing.
Open Command Prompt as administrator, enter ipconfig /flushdns, and press Enter. Restart Steam after Windows confirms that the DNS resolver cache was cleared.
Verification:
Steam resolves a working content-server address and the download continues. If the error remains on every game and every network, move to Steam Support rather than deleting game manifests.
What worked for other readers
Steam displays Manifest Unavailable when the client cannot obtain the metadata needed to identify and download the correct game build. The failure may sit between the client and a regional content server, inside cached download data, in a filtered network path, or in the game’s own depot and branch setup. Most cases do not mean that the installed game files are permanently damaged.
Quick Fix
- Exit Steam fully and reopen it.
- Change Steam > Settings > Downloads > Download Region to a nearby alternative.
- Select Clear Download Cache in the same Downloads panel.
- Disconnect VPN or proxy software and retry on a direct connection.
- If only one game fails, leave its beta branch and verify its installed files.
What the Error Means
A Steam manifest identifies the exact content assigned to an application depot and build. SteamPipe can deliver one or more depots for a game, with each depot grouped under a unique Depot ID. When Steam cannot retrieve or authorize the required manifest, installation or updating stops before the correct file set can be selected. [✅Source-1]
Find the Relevant Fix
How the Manifest Error Appears
The message usually appears in the Downloads page as “An error occurred while updating [game name] (manifest unavailable)”. It can happen during a new installation, a scheduled patch, a Proton or Steam Linux Runtime download, DLC retrieval, or a move between library drives.
Common Symptoms
- The download starts, falls to zero, and returns to the queue.
- One game repeatedly fails while other titles update normally.
- Several games fail after changing networks, regions, or security software.
- Steam alternates between Manifest Unavailable, Content Servers Unreachable, or No Internet Connection.
- A beta, DLC package, compatibility tool, or platform-specific component cannot install.
What It Usually Does Not Mean
- Your Steam account has not automatically lost ownership of the game.
- Your save data is not normally involved in manifest retrieval.
- Reinstalling Windows is not a suitable first response.
- Deleting every
appmanifest_*.acffile is not a safe opening step.
Why Steam Says Manifest Unavailable
Regional Content Server or CDN Route Failure
Steam selects content servers according to geographical download regions. A selected route can be slow, overloaded, unreachable from a particular internet provider, or temporarily unable to return the requested metadata. Valve’s support guidance advises trying another nearby download region when the current region has download trouble. [✅Source-2]
Stale Download Cache
The Steam client stores temporary download configuration and session data. A stale route, interrupted request, or old cached response can keep sending the next attempt through the same failing path. Clearing the download cache forces Steam to obtain fresh configuration and requires the user to sign in again. [✅Source-3]
VPN, Proxy, DNS, or Filtered Network Path
A VPN exit node, manual proxy, school network, workplace gateway, parental filter, DNS resolver, or router security feature can alter the path between Steam and its content network. Steam may still open Store pages while game metadata requests fail, because browsing and content delivery do not always follow the same host and port path.
Steam lists web traffic on TCP ports 80 and 443, plus Steam traffic across the 27015–27050 TCP and UDP ranges. Home users should normally allow the Steam applications rather than open broad inbound router rules. On a managed network, blocked remote ports can explain why Steam works on a phone hotspot but not on the main connection. [✅Source-4]
Game-Specific Depot or Branch Problem
If every other title downloads correctly, the problem may be tied to one game’s selected branch, operating-system depot, language depot, DLC entitlement, or publisher-side build assignment. Steam depots can be restricted by operating system, architecture, language, and DLC ownership. A branch that points to a retired or unavailable build can therefore fail for one title while the client remains healthy.
Library Folder Permission or Disk State
A manifest can be retrieved successfully but the update may still stop when Steam cannot write the resulting files. This is more likely after moving a library, restoring a backup, changing Windows accounts, replacing a drive, or using an external disk. Steam’s library repair command refreshes folder permissions and checks the selected storage location.
Security Software Interference
Antivirus, firewall, web-filtering, traffic-shaping, and endpoint security tools can inspect or block Steam network and disk operations. Valve lists VPN software, security products, peer-to-peer utilities, and download accelerators among programs that may interfere with Steam. [✅Source-5]
Identify Whether the Failure Is Local or Game-Specific
| Test Result | Most Likely Area | Next Action |
|---|---|---|
| All games fail on one computer | Steam cache, security software, DNS, or client state | Clear the cache, restart, and test another network |
| All games fail on every device using the same router | Router, ISP route, DNS, proxy, or regional server path | Change region and test a phone hotspot |
| Only one game fails | Game branch, depot, DLC, platform, or publisher configuration | Leave betas, verify files, and check the game’s Steam Support page |
| The download works on a hotspot | Main network or ISP path | Restart the router, disable filtering, or contact the network administrator |
| The error began after moving the game | Library registration, folder permission, or drive issue | Repair the Steam library folder and check free disk space |
| Store pages also fail to load | Broader Steam connectivity problem | Check proxy, firewall, DNS, and general internet access |
Fast isolation test: Try one small free title or an update for a different installed game. A second successful download points away from the computer and toward the original game’s depot or branch.
Repair Steps in the Safest Order
1. Exit Steam Completely
Do not close only the main window. Select Steam > Exit, then check the notification area for a remaining Steam icon. Reopen the client and resume one download. A full exit resets active content-server sessions and releases locked library files.
2. Select a Nearby Download Region
- Open Steam > Settings > Downloads.
- Select Download Region.
- Choose the next nearby city or country.
- Restart Steam and retry the affected title.
A nearby alternative is preferable because it changes the server pool without adding unnecessary distance. Try two nearby regions before moving to network resets.
3. Clear the Download Cache
- Open Steam > Settings > Downloads.
- Select Clear Download Cache.
- Confirm the action.
- Sign back in and resume the download.
This action does not erase installed games. It can remove queued state and temporary download settings, so note any custom download limit before resetting the cache.
4. Test Without VPN, Proxy, or Traffic Filters
Disconnect VPN software and close network accelerators. On Windows, check Settings > Network & Internet > Proxy and turn off manual proxy use unless the connection requires it. Steam warns that VPN software can prevent the client from reaching the Steam network.
Do not use a VPN to imitate another store country. For troubleshooting, the safer test is a direct connection or a temporary switch to another trusted network.
5. Repair the Library Folder
- Open Steam > Settings > Storage.
- Select the drive that contains the game.
- Open the three-dot menu.
- Select Repair Folder.
- Approve the administrator request if shown.
Also confirm that the drive is connected, writable, and has enough free space for both the download and temporary patch files. Some updates need extra working space while Steam rebuilds large archives.
6. Handle a One-Game Failure Differently
Right-click the game and open Properties > Betas. Set Beta Participation to None unless the developer requires a named branch. Then open Installed Files > Verify integrity of game files. Steam compares the local installation with the assigned build and downloads missing or altered files. [✅Source-6]
If the title is newly released, recently patched, removed from sale, or limited to a particular platform, the publisher may need to correct the depot or branch. Repeatedly reinstalling Steam will not create a missing publisher-side manifest.
7. Allow Steam Instead of Disabling the Firewall
Open Windows Security > Firewall & network protection > Allow an app through firewall. Permit Steam on the network types you use. Third-party suites may have separate web shield, application control, and quarantine panels.
Temporarily pausing protection can be used as a short diagnostic test, but the lasting fix should be an allow rule. Turn protection back on immediately after the test.
8. Flush DNS on Windows
- Search for Command Prompt.
- Select Run as administrator.
- Enter
ipconfig /flushdns. - Restart Steam.
Microsoft states that /flushdns clears and resets the DNS client resolver cache, including negative entries that can preserve a failed lookup. [✅Source-7]
9. Test Another Trusted Network
Connect the computer to a phone hotspot or another private network long enough to start the download. Stop after a small amount of data if mobile usage is limited. Success on the second network shows that the Steam account, game entitlement, and computer can obtain the manifest; the remaining fault sits in the original router, DNS resolver, ISP route, or network policy.
Advanced Checks When the Error Returns
Do Not Delete Local App Manifest Files First
Files named appmanifest_AppID.acf inside a Steam library record local installation state. They are not a replacement for the remote depot manifest Steam is trying to download. Removing them can make an installed game appear uninstalled until Steam rediscovers the files. Back up the library before changing any file inside steamapps.
Check the Steam Content Log
Steam records download activity in content_log.txt inside the client’s logs folder. Search the newest entries for the affected AppID, depot, manifest, timeout, 403, or 404. The pattern matters:
- Timeout or connection errors across many depots: investigate region, routing, DNS, proxy, and security software.
- The same missing manifest for one depot only: suspect a game branch, DLC, platform depot, or publisher setup.
- Disk write or permission errors: repair the library folder and check the drive.
Check Steam Deck and Linux Compatibility Downloads
On Linux and Steam Deck, the failed item may be Proton, Steam Linux Runtime, shader data, or a platform-specific depot rather than the game itself. Remove a forced compatibility-tool selection only as a test: open Properties > Compatibility, clear the forced-tool option, restart Steam, and retry. If several compatibility tools fail together, treat the issue as a client or network problem.
Use Network Reset Only After Simpler Tests
Windows network reset removes and reinstalls network adapters, then returns related settings to defaults. It can also require VPN and virtual adapter software to be configured again. Use it only when Steam and other network applications show persistent connection faults: Settings > Network & Internet > Advanced network settings > Network reset. Microsoft documents the same route for Windows 11. [✅Source-8]
Know When Reinstalling Steam Is Unlikely to Help
A reinstall may help if Steam itself cannot update, client files are damaged, or menus and downloads fail across every title after cache and network repairs. It is less useful when one game requests a manifest that no regional server can provide. Preserve the steamapps folder before uninstalling so installed game data is not removed unnecessarily.
When to Contact Steam Support
- The error affects every game on more than one trusted network.
- The same game fails on more than one computer using the same Steam account.
- Changing region, clearing cache, leaving betas, and repairing storage do not change the result.
- The content log repeatedly names the same AppID, Depot ID, or manifest number.
Include the game name, AppID when known, operating system, selected download regions, the exact time of the latest failure, and the relevant lines from content_log.txt. Remove account names, local usernames, and network addresses before sharing logs publicly.
Common Questions About Steam Manifest Unavailable
Does Manifest Unavailable Mean Steam Servers Are Down?
Not always. A regional content route can fail while Steam sign-in and Store pages remain available. Change to a nearby download region and test another game. If all titles fail on several devices, a wider service or network-route problem becomes more likely.
Will Clearing the Download Cache Delete My Games?
No. Steam’s cache-clearing process resets temporary download data and signs the account out, but it does not uninstall games already stored in the library.
Why Does Only One Steam Game Show the Error?
That pattern points toward the game’s branch, depot, DLC assignment, language package, operating-system package, or publisher-side build. Leave optional betas, verify files, and check whether the title’s support page reports a deployment problem.
Should I Delete Appmanifest ACF Files?
Not as an opening fix. Those files help Steam track locally installed applications. Deleting one can make the game appear uninstalled and does not repair a remote manifest that the content server cannot provide.
Can DNS Cause Manifest Unavailable?
Yes. A stale or failed DNS entry can prevent Steam from resolving a working content host. On Windows, ipconfig /flushdns clears the resolver cache. A successful hotspot test also points toward the original network’s DNS or routing path.
Is Reinstalling Steam Necessary?
Usually not. Try a region change, cache clear, direct network connection, library repair, branch reset, and firewall allow rule first. Reinstall the client only when Steam itself appears damaged or every title fails after the safer checks.
How Long Should I Wait Before Retrying?
Steam does not publish a fixed wait period for this error. Restart the client, change the download region, and retry after a brief pause. A one-game failure that continues on different networks is more likely to need a publisher or Steam Support fix.