📎 AI Summary:
The thread asks what Windows network issue could make Steam downloads appear to take 18 days, and why renewing the IP lease and flushing DNS seemed to help. The response says those commands can refresh DHCP settings or clear stale DNS answers, but the SSD’s 100% utilization may indicate Steam was bottlenecked by disk work; because several fixes were applied together, the cause is uncertain, and checking Steam’s disk/network graphs and testing each fix separately was advised.

winget help

New Member
Member details
Joined
Dec 5, 2025
Messages
2
Thread Author #1
What Win11 network misconfiguration would cause a video game downloads to take 18 days?

Background:
I helped someone resolve an issue where video games from their Steam library had an estimated download time of 18 days. Their ssd would shoot to 100% utilization and their download speed would drop to 20 Mbps.
I resolved the issue by running:
ipconfig /release
ipconfig /renew
ipconfig /flushdns
Then I had to user reset their Windows Network sittings and cleared the download cache folder in Steam.

I would like to know why the ip commands resolved this issue. Obviously there was some sort of network misconfiguration on their device. What could that misconfiguration be? I just want a better understanding of the underlying issues to some of the resolutions I've found to help me better understand computers and networking better.

Please NOTE: All of the below steps were completed with no results. It was the ip commands that resolved the issue which means the slow download speeds were caused from the network side of things.

chckdsk C: /f > rebooted device to initiate scan.
sfc /scannow (until no errors were found)
DISM /Online /Cleanup-Image /RestoreHealth (completed successfully)
Reinstalled Steam.
Reset router.
 

Last edited:

WindowsForum AI

AI
Staff member
Robot
Member details
Joined
Mar 14, 2023
Messages
122,683
The 100% SSD utilization is the strongest clue, not the 18-day estimate. If Steam’s network rate repeatedly dropped when the SSD hit 100% and recovered when the disk eased up, I’d suspect Steam was waiting on local install work before I’d suspect a Windows network misconfiguration. Valve notes that Steam can slow downloads to match how quickly it can install the data. That doesn’t mean the SSD is failing.

What the IP commands could have fixed​

  • ipconfig /release and ipconfig /renew drop and reacquire the adapter’s DHCP IPv4 configuration. The PC may get the same IP address back. If the router had changed its DHCP settings and the PC was still using an old gateway or DNS server, reacquiring the lease could help. A wrong gateway would usually affect more than just Steam.
  • ipconfig /flushdns clears Windows’ cached DNS answers, including cached lookup failures. That can help Steam’s next connection if an old answer pointed to an endpoint that was no longer reachable. It doesn’t change which DNS server Windows uses or speed up a transfer that’s already connected.
Because you also reset Windows networking and cleared Steam’s download cache, you can’t tell which step helped unless you tested between them. Steam’s cache clear refreshes Steam’s own cached configuration; it’s separate from the Windows DNS cache. And for scale, a 100 GB download at a sustained 20 Mbps would take about 11 hours, not 18 days. That 20 Mbps reading alone doesn’t explain the estimate.

If it happens again​

  1. Watch Steam’s Network and Disk graphs together. If network traffic dips while disk activity stays high, then rebounds when disk activity eases, that supports an install bottleneck. Check Task Manager to see which process is using the drive.
  2. Pause Steam and run a separate speed test on the same PC. If that’s also slow, investigate the network. If it’s normal and Steam is slow even when the disk is quiet, check Steam’s download limit and region before resetting Windows.
  3. If you suspect DHCP, capture ipconfig /all before and after a lease refresh. Compare the active adapter’s IPv4 address, default gateway, and DNS servers. Test after each fix rather than doing them all at once—that’s how you turn a successful fix into a useful diagnosis.
 
Last edited: