ERROR-A / Search

Start with a symptom, message or error code.

Explore
Menu
Error messageDisk write error means Steam did not complete a write during installation or updating. It does not by itself identify a faulty drive or corrupted download. The game, drive and failure stage help separate one file, one library and a broader storage problem.

Steam disk write error

Disk write error

Steam reports a write error during installation or updating. Record the full message and affected library before changing download settings.

Try this first

1 quick checks · ~3 min

  1. Record the failure and affected libraryLocate the operation and drive before changing permissions or content.

Find your situation

See all the clues. Choose the one that matches what you observe.

Only one game fails

Compare another installation in the same library; running an installed game does not test whether writing works.

Several games fail in one library

Check space, availability and permissions at that location before changing the network.

Windows also fails to save files

Prioritize preserving data and diagnosing storage rather than repeating downloads.

Diagnostic signals

ObservationThe message identifies a file or drive
Keep the path for support and check that actual location. Do not assume it always matches the drive you were looking at.
ObservationRepair seems to work but the error returns
Temporary recovery does not identify the cause. Record whether the same file fails again and investigate blocking or external errors; do not repair in a loop.

Step-by-step solutions

01

Record the failure and affected library

  • Estimated time: 3 min
  • Easy
  • Low risk

Locate the operation and drive before changing permissions or content.

  1. Record the full message, game, new installation or update, and path if shown. In Steam > Settings > Storage identify that library’s drive and available space. Do not delete files yet.

  2. If reading/writing also fails outside Steam, move to data protection. Otherwise choose one game or several games based on an actual write comparison, not on existing games launching.

Sources:
02

Distinguish one file from a library-wide failure

  • Estimated time: 5 min
  • Easy
  • Low risk

  1. Use a small update you already need for another game in the same library. If no comparison is available, leave the scope unconfirmed; do not download a huge game solely to test. If it also fails, follow the library branch.

  2. If only that game fails, close it and its mod editor or tools that may hold files open; exit Steam normally and reopen it. Retry once: recovery is consistent with a temporary lock, not proof of a faulty drive.

  3. If it persists and the game is installed, move to verifying its files. For a new installation without verifiable files, keep the error and check whether security software recorded a specific block. Do not disable antivirus or automatically restore a detected file.

Sources:
03

Check the location Steam is trying to write to

  • Estimated time: 5 min
  • Easy
  • Low risk

  1. Confirm the drive remains available in Windows and has space for the operation Steam reports; download size does not always equal update space. If space is insufficient, move only recoverable content using its normal tool. There is no universal free-space percentage.

  2. If an external drive disappears or also errors outside Steam, do not force it with more downloads: follow data protection. If Windows otherwise works and several games fail only there, repairing the library folder is a bounded permissions test.

  3. If another healthy drive with space is already available, a pending small installation in a library there allows comparison. Success localizes the problem to the original location without proving physical damage. If both fail, investigate the client and specific blocks with support.

Sources:
04

Stop writes if the failure extends beyond Steam

  • Estimated time: 5 min
  • Easy
  • Low risk

  1. If you already observed unreadable personal files, Windows errors or drive disconnections, pause downloads and avoid benchmarks, repeated repairs or large tests. This pattern requires investigating the drive and its connection before modifying a library.

  2. If data remains accessible, prioritize copying irreplaceable files to another healthy drive. With mechanical noises, continuous disconnections or critical data without a backup, stop using it and seek professional recovery advice before forcing reads.

  3. Give technical support the model, connection, affected paths and messages. Some games launching does not prove the drive can write reliably. Do not format or use DiskPart or repair-mode CHKDSK as an automatic response.

Sources:
Advanced

Advanced checks

Continue if the earlier steps did not help. Read each procedure’s precautions first.

05

Verify only the affected installed game

  • Estimated time: 10 min
  • Easy
  • Moderate risk
  • Data loss: Possible

  1. Run verification without other intensive processes or simultaneous verifications. Let it finish and test the failing update once.

    1. Library
    2. Affected game
    3. Properties
    4. Installed Files
    5. Verify integrity

  2. If it replaces files and the update finishes, stop. Some local configuration files may normally fail verification; the useful criterion is the operation working again. If Disk write error returns at the same point, verifying integrity again does not explain why writing fails.

Sources:
06

Repair only the identified library folder

  • Estimated time: 5 min
  • Easy
  • Moderate risk
  • Administrator required
  • Data loss: Possible

  1. Select the affected library, open its three-dot menu and use Repair Folder/Repair Library, depending on version. Accept elevation only when it belongs to Steam and this action.

    1. Steam
    2. Settings
    3. Storage

  2. Retry one operation in that library. If it works, stop; the result supports a folder-access problem without proving its origin. If unchanged, keep the result for Steam Support and the comparison with another drive. Do not change ownership or permissions across the whole disk.

Sources:
Next step

Still not working?

If the operation finishes, stop repairing. For a persistent error, send Steam Support the game, drive, stage, message and comparisons. A security detection needs provider review, not global exclusions. Changing region or clearing cache is not the first response to a local write failure; do not reinstall Steam without preserving content and saves either.

Sources

Documentation behind this guide. Editorial recommendations are identified separately.

Source review: . A documentation review, not a physical hardware test.

Related problems

steam
Problem

Steam won't download games

The game never enters an active download or remains paused, scheduled or stopped by an error. First distinguish queue state from an active download displaying 0 B/s.

View solution
steam
Problem

Steam download stuck at 0 B/s

0 B/s measures network throughput, not all installation work. An update can keep processing files on disk after downloading; check progress before interrupting it.

View solution