DISK USAGE 0 mb/s WHEN DOWNLOADING GAMES

[af57xd]

I didnt have any problems with steam downloads before. Yesterday i bought CS GO and tried downloading it, steam would start the download and the network usage would be normal, but my disk usage would always be at zero. The green bar on the graph is always at the bottom. i tried changing my download region, i deleted my download chache, i used steam://flushconfig, i disabled my firewall and windows defender, nothing worked, it would occasionally go to a normal disk usage for 5 seconds and then drop down. I dont know what to do. I NEED HELP. WHY IS STEAM SO ♥♥♥♥! The same thing happened to my friend today. BTW i also installed and uninstalled steam. I also tried opening steam as admin and that didnt work either.

[Jack Schitt]

It the green bar at the bottom growing indicating that it's downloading? If the bar is growing leave it alone...it's downloading. The files aren't going to show up where they will be when the game installs until the download completes. During the downloading process they go in to the downloading folder, not where the files are after the game is installed.

[af57xd]

it says that the green bar is disk, its always at the bottom, the blue bar is always high, the blue bar is network. Sometimes the green bar rises for 10 seconds and my estimated time goes from 32 days to 20 mins as it should be. but then it goes right back down after 10 seconds. Thanks for the reply anyways...

[Jack Schitt]

The blue is the total network connection indicating that you have a connection and the strength of the connection with the server it's downloading from. If the connection fails or fluctuates the blue bars change height. The green line shows how much of the connection the download is using.

Are the blue bars pretty long, or short? When they indicated a good connection to the server they're all the way at the top of that window/panel/section of the downloads area.

Where is the green line? (bandwidth)
Top: It's using all of the connection that it possibly can.
Middle: It's only using half of the connection.
Bottom: It's not using much or any of the connection at all.
The green line will go up and down as or if the bandwidth/connection speed fluctuates up and down (faster and slower).

Have you checked your bandwidth settings in Steam > Settings > Downloads?
Turn the throttling option off and make sure your bandwidth is set to unlimited.

It might just be that the servers are busy. Server population depends on what time of day it is where you are. It's the middle of the day where I am in Eastern Standard Time. A lot of people are online right now and that may cause slowness and drastic fluctuation.

If it's just that the server is busy there isn't much you can do about it other than wait until later at night after 11pm your time and try to download it then.

[af57xd]

i have my no limit for my bandwidth and the throttling option is off. My blue bar is always high, but my green bar is always at the bottom. Thank you so much for answering

[Jack Schitt]

It could just be that the time of day you're downloading there are also 273892578927589157382945723598372593275235 people all over the world online using the internet. The internet is busy. Just like with traffic if you're on the road at busy times you're going to have a long travel time, if you're on the internet trying to download at rush hour (peak) times you're subject to experiencing slower speeds.

The only thing you can do about that is call everyone in your area on the phone and tell them to get off the internet so you can download your game.
Try it, they'll do that for you, right?

Whether that's what's going on or not...
Have you tested your internet connection speed?
http://www.speedtest.net/

Have Windows?
winkey+r and type CMD
Type: ping www.steampowered.com

Here are my personal results indicating a pretty good connection:

C:\Users\user>ping www.steampowered.com

Pinging www.steampowered.com [104.100.155.144] with 32 bytes of data:
Reply from 104.100.155.144: bytes=32 time=25ms TTL=60
Reply from 104.100.155.144: bytes=32 time=25ms TTL=60
Reply from 104.100.155.144: bytes=32 time=26ms TTL=60
Reply from 104.100.155.144: bytes=32 time=26ms TTL=60

Ping statistics for 104.100.155.144:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 26ms, Average = 25ms

The results of interest in this test are Time and Lost. 'ms' is miliseconds, lost is packet loss. If you have a lot of packet loss in one of the lines, which are hops, we've narrowed down to a result of where the problem is. Unless the hop with the longest time is the very first one there isn't much that can be done about it.

Next, run a pathping command. This reports several connection test results:

C:\Users\user>pathping www.steampowered.com

Tracing route to www.steampowered.com [23.199.207.185]
over a maximum of 30 hops:
  0  DESKTOP-0U53MR5.networkID [192.168.1.xx]
  1  ispName.networkID [192.168.1.1]
  2  xx.xx.xx.xx (this is an IP I edited to hide for security purposes)
  3  G0-0-4-0.SCTNPA-LCR-21.ispName-gni.net [xxx.xx.xxx.xxx]
  4     *        *        *
Computing statistics for 75 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           DESKTOP-0U53MR5.networkID [192.168.1.xx]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  ispName.networkID [192.168.1.1]
                                0/ 100 =  0%   |
  2   16ms     0/ 100 =  0%     0/ 100 =  0%  xx.xx.xx.x
                                0/ 100 =  0%   |
  3   18ms     0/ 100 =  0%     0/ 100 =  0%  G0-0-4-0.SCTNPA-LCR-21.ispName-gni.net [xxx.xx.xxx.xxx]

Trace complete.

The results of interest in this test, again, are
the ms
the percentage listed at the bottom in the Lost column

If the first one reports a loss the problem is between your computer and where you get the connection from (a router/modem). If it reports a loss in the first report results and you're on a wi-fi connection a loss is common in that report due to the fact that wireless connections being unstable. It doesn't mean that that's your entire problem and it may not be correctable because a loss there on a wireless connection is just simply how wi-fi connections are, there is no fixing it other than connecting with ethernet cable instead of using a wi-fi connection. It may be possible to improve the loss in a wi-fi connection by moving closer to the router physically but it's extremely rare and virtually impossible to get a loss rate from a wi-fi connection down to a steady 0% constantly.

Next, run a tracert command:

Tracing route to www.steampowered.com [104.100.155.144]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  ispName.networkID [192.168.1.1]
  2    11 ms     9 ms     9 ms  xx.xx.xx.x
  3   139 ms    74 ms   305 ms  G0-0-5-0.SCTNPA-LCR-21.ispName-gni.net [xxx.xx.xxx.xx]
  4     *        *        *     Request timed out.
  5    25 ms    26 ms    25 ms  0.ae7.GW1.EWR19.ALTER.NET [xxx.xxx.xxx.xxx]
  6    26 ms    25 ms    26 ms  a104-100-155-144.deploy.static.akamaitechnologies.com [xxx.xxx.xxx.xxx]

Trace complete.

This indicates how many hops there are between your computer and the destination server. Hops are basically connection hubs, where the "web" around the world intersects.

See that "Request Timed out"? Having one of those it gets by and produces a result below it isn't much of a big deal but if you hae a bunch of results like that that is not good. It means a hop isn't working properly therefore it's causing a delay (lag).

Reply with your results please. Some of this information is sensitive which is why I X'd some of them in my results. The IP numbers aren't important to know we're testing times so it's a wise idea to also X the IP's out in your results.

None of the above tests are illegal to do, they are common IT commands used to test connection quality and times to pin down where a connection problem might be.

THERE IS NO WAY TO RE-ROUTE HOPS AROUND A HOP THAT IS NOT WORKING
The only people who can sometimes change hops around is an ISP and it takes a high level in a very high Tier of the company to edit and steer the connection around a hop that's dead, and sometimes that tech might not bother re-routing it because it's not going to help the connection be any faster anyway.

Run these tests and see if any of it reports any high amounts of packet loss.

Steam lists some of this and explains it a bit, too, here:
https://support.steampowered.com/kb_cat.php?id=4&t=qanda