Thuml News

This site has affiliate links.

Try This
All Recent News
Gaming Problem: Steam downloads repeatedly drop to 0 B/s (or stall at “0 B/s / 0 disk”) on Windows 11 and Steam Deck, making installs/updates take hours or never finish (2026-01-06 07:01)
Jan 6, 2026 7:01 a.m.

Problem: Steam downloads repeatedly drop to 0 B/s (or stall at “0 B/s / 0 disk”) on Windows 11 and Steam Deck, making installs/updates take hours or never finish

Published: 2026-01-06 12:00 (local time)

Quick Summary

  • Many Steam users report downloads that start fast, then plunge to 0 B/s (often cycling), or appear “stuck” with 0 disk usage.
  • Reports cluster around Windows 11 PCs (especially after OS changes) and also show up on Steam Deck (often over Wi‑Fi or SD card installs).
  • There is no single universal fix; the same workaround helps some users and does nothing for others.
  • Research points to multiple overlapping causes: storage write bottlenecks, cache corruption, content server/region routing, security software interference, and SD card/Wi‑Fi power behaviors.
  • The best approach is to try targeted workarounds in a specific order, watching whether the “bottleneck” is network, disk, or security scanning.

What’s happening

Players describe a consistent pattern: a Steam download spikes to normal speed, then abruptly drops to 0 B/s for several seconds (or much longer), sometimes repeating in a loop. Others report the download “freezes” at a particular percentage with 0 disk usage, or ends in “corrupt download” errors. The key detail in many threads is that other launchers (Epic/Xbox/EA) download normally on the same connection, suggesting it’s not always an ISP problem.

On Steam Deck, similar symptoms show up as start/stop downloading over Wi‑Fi and inconsistent throughput, especially when writing to microSD. Users often try common toggles (like Wi‑Fi power management settings) with mixed results. On Windows 11 PCs, the issue is frequently described as appearing after moving from Windows 10 or after system changes, and some users report that only very specific changes (like drive firmware updates or bandwidth limiting) improve stability.

Likely causes (what research suggests)

  • Disk/SSD write bottleneck or instability: Steam downloads are not purely “network”; they often involve frequent writes, patching, and verification. Multiple users report improvements after SSD firmware updates or replacing a failing drive, implying storage can be the real limiter.
  • Corrupted download cache or bad partial depot data: Steam’s own support documentation includes “Clear Download Cache,” which logs you out and rebuilds local download state—often resolving stuck or looping behavior for some setups.
  • Routing/content server issues (region or CDN path): Steam support guidance on slow downloads emphasizes content servers and connectivity to them; switching download regions can change which servers you hit.
  • Security scanning/Controlled Folder Access interference: Real-time scanning can heavily slow or block frequent writes. Microsoft documents how exclusions work and notes the tradeoff: fewer scans but higher risk if misused.
  • Steam Deck Wi‑Fi/SD card throughput mismatch: Community testing suggests that if a microSD can’t sustain the burst write rate Steam attempts, downloads can “pulse” or repeatedly hit 0. Capping bandwidth can stabilize the write pipeline.

Solutions & Workarounds

1) Set a Steam download speed limit (counterintuitively, this can stabilize downloads)

Who it helps: Windows 11 PC and Steam Deck users whose downloads spike then slam to 0 repeatedly.

  • Steps:
    • In Steam, open Settings > Downloads.
    • Enable a download speed limit (Steam has an official help page for client rate limiting).
    • Pick a limit slightly below the speed where your download becomes unstable (example: if it spikes to 80 MB/s before dropping to 0, try 50–70 MB/s; if on microSD, you may need far lower).
    • Restart the download and watch if the graph becomes steady.
  • Risks/tradeoffs: Slower peak speeds; you’re choosing stability over maximum throughput.
  • Stop & contact support when: Downloads still corrupt or stall even at very low limits (e.g., 5–10 MB/s), suggesting deeper disk/network problems.

2) Clear Steam’s Download Cache (official Valve step)

Who it helps: Anyone seeing stuck percentages, repeated “0 B/s,” or looping partial downloads.

  • Steps:
    • In Steam, go to Settings > Downloads.
    • Select “Clear Download Cache” (Steam will log you out per Valve’s support instructions).
    • Sign back in, then retry the download.
  • Risks/tradeoffs: You’ll need to log in again; ongoing downloads reset.
  • Stop & contact support when: Cache clears don’t change behavior across multiple titles/regions.

3) Change Download Region (reduce bad routing/CDN issues)

Who it helps: Users who suspect a specific Steam content server path is unstable (especially if the same title fails repeatedly).

  • Steps:
    • Steam Settings > Downloads > Download Region.
    • Select a nearby alternate region (then test), and if needed try one more within your broader area.
    • Restart Steam and retry the download.
  • Risks/tradeoffs: Farther regions can increase latency and reduce peak speeds; don’t bounce endlessly (it can mask the real issue).
  • Stop & contact support when: Multiple regions behave identically, pointing away from CDN routing.

4) Check storage health and update SSD firmware (especially Samsung NVMe)

Who it helps: Windows 11 users with NVMe SSDs, especially if Task Manager shows erratic disk activity or Event Viewer logs disk warnings.

  • Steps:
    • Confirm free space: keep ample headroom on the drive hosting the Steam library (and on C: if Steam uses it for temp work).
    • If you have a Samsung SSD, install/update Samsung Magician and check for firmware updates (Samsung documents that firmware updates require backup and a reboot, and cannot be done over USB enclosures).
    • Reboot, then retry the download.
  • Risks/tradeoffs: Firmware updates carry small but real risk—backup first; cannot downgrade firmware per Samsung guidance.
  • Stop & contact support when: SMART/drive health looks suspicious, or downloads fail across all apps (not just Steam).

5) Temporarily reduce Microsoft Defender interference (use exclusions carefully)

Who it helps: Windows 11 users who suspect real-time scanning is choking Steam’s heavy write/patch behavior.

  • Steps:
    • Instead of fully disabling protection, consider adding a temporary exclusion for the Steam library folder (or Steam.exe process), following Microsoft’s “add an exclusion” instructions.
    • Retry one problematic download/update and observe whether the 0 B/s stalls disappear.
    • Remove the exclusion afterward if it doesn’t help, or once the large install finishes.
  • Risks/tradeoffs: Exclusions reduce real-time protection for those paths/processes (Microsoft explicitly warns this can increase risk).
  • Stop & contact support when: You’re unsure which folder/process to exclude, or your system is shared/high-risk—prefer official Steam/Microsoft support guidance.

6) Steam Deck: download to internal storage first, then move to microSD

Who it helps: Steam Deck users whose downloads stall or pulse when installing directly to microSD.

  • Steps:
    • Set installation target to internal storage.
    • Download/install the game.
    • Use Steam’s storage management to move the installed game to the SD card afterward.
  • Risks/tradeoffs: Requires free internal space; moving takes extra time but is usually steadier than writing patch chunks to slower cards.
  • Stop & contact support when: Downloads pulse even to internal storage over Wi‑Fi (then it’s more likely network/power behavior).

Prevention (so it doesn’t come back)

  • Keep 15–20% free space on the drive hosting your Steam library to reduce patch/install bottlenecks.
  • Prefer high-endurance, reputable microSD cards for Steam Deck; if instability appears, test by installing to internal storage.
  • Keep SSD firmware current (especially if you notice system-wide stutters or disk warnings).
  • Don’t permanently leave broad antivirus exclusions; use targeted, temporary exclusions only if you can confirm they help.
  • If a speed limit fixes it, keep a stable cap during large installs and remove it later when no longer needed.

FAQ

Q: Is “0 disk usage” always bad?
A: Not always—Steam can alternate between downloading, unpacking, and patching. But if both network and disk sit at 0 for long periods (minutes+) with no progress, that’s when troubleshooting makes sense.

Q: Why do other launchers download fine, but Steam doesn’t?
A: Steam’s patching/unpacking patterns can stress disk writes differently than “download then install” launchers, so marginal storage or scanning issues can show up only on Steam.

Q: Should I keep changing Download Region until it works?
A: Try one or two nearby alternates. Constant hopping can waste time and hide whether the root cause is disk/security scanning.

Q: Why does limiting speed help at all?
A: It can prevent the network from outrunning your storage/CPU/unpacking pipeline, reducing stalls caused by bursts the system can’t sustain.

Q: When is it probably a failing drive?
A: If you see disk errors in system logs, frequent “corrupt download,” or the system stutters during installs across multiple apps, storage health testing becomes the priority.

Q: Is adding a Defender exclusion safe?
A: It’s a tradeoff. Microsoft warns exclusions reduce scanning for those items. Use the smallest scope possible, only if needed, and remove it afterward.

Q: On Steam Deck, is microSD the main suspect?
A: It’s a common bottleneck. If downloads stabilize to internal storage, your SD card speed/health is a strong suspect.

Q: What should I do if none of this works?
A: Document what you tried (regions, cache clear, bandwidth cap, target drive, error messages) and contact Steam Support with those details.

Sources & References

Back to Blog