Haven’t played any games in a while and when trying to come back to SC2 or Warzone the games needed updates. While trying to update them they get stuck saying “Queued - 0%” or “Waiting…”. I waited for more than an hour now and nothing has changed. I tried reading and following other topics on this forum but nothing worked. Please help!
Hey there! Thank you for reaching out, as it can understandably be frustrating to have a technical issue occur when simply trying to enjoy your gaming time. This behavior with an update can have a few causes ranging from a conflicting third-party program to a network-related problem. Try the following to narrow this down further:
- Try a DNS Flush to clear out any corrupted or stagnate data.
- Fully update or temporarily uninstall security programs which may be interfering with your connection to the patching server(s). More information on troubleshooting security applications here, if curious.
- Test an alternate network such as a mobile hotspot to determine whether the problem is isolated to your current network.
If you’re still unable to update your games, please run a WinMTR network test so that we can further investigate the problem. Here are the instructions:
- Download the tool from this page
- In the “Host” field, enter “us.patch.battle.net” (without quotes).
- Start the test and launch the Battle.net Desktop App, then try to update a game. Ensure the problem occurs while the winMTR tool is running.
- After recording data for about 5 minutes, click “export text” and save the winMTR file in an easy to find location.
- Once you have that made, open the file. You’ll need to copy and paste the contents of the Text document into the post, and put four Tilde (~) marks above the winMTR. It’ll look like this:
WinMTR goes here
If you have issues pasting here, please use Pastebin and post the link (ex: Pastebin (dot) com/123456).
Hello there! Thanks for the response. I tried following the first three steps but it was still not working, so I tried to do the WinMTR test. But this time I had a different issue that reads: “Battle.net Update Agent went to sleep. Attempting to wake it up…”, so I was not able to even try and update one of the games while the test was running. After some time, here are the results:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 99 | 80 | 1 | 3 | 3 | 3 | 3 |
| No response from host - 100 | 79 | 0 | 0 | 0 | 0 | 0 |
| 172.16.186.251 - 6 | 327 | 310 | 9 | 15 | 82 | 11 |
| 172.16.182.10 - 80 | 1502 | 310 | 9 | 15 | 108 | 19 |
| No response from host - 100 | 79 | 0 | 0 | 0 | 0 | 0 |
| 206.41.108.77 - 11 | 275 | 245 | 110 | 116 | 186 | 113 |
| 206.41.108.97 - 84 | 1497 | 245 | 110 | 119 | 213 | 114 |
| 137.221.76.35 - 92 | 1411 | 119 | 163 | 175 | 273 | 166 |
| xe-0-0-1-1-br01-eqda6.as57976.net - 24 | 206 | 158 | 163 | 170 | 273 | 211 |
| et-0-0-2-br02-swlv10.as57976.net - 88 | 1482 | 179 | 158 | 169 | 275 | 160 |
| et-0-0-1-pe02-swlv10.as57976.net - 90 | 1467 | 159 | 163 | 169 | 228 | 164 |
| las-swlv10-ia-bons-02.as57976.net - 89 | 1471 | 164 | 164 | 168 | 211 | 165 |
| 137.221.105.17 - 27 | 191 | 140 | 163 | 171 | 273 | 166 |
| 137.221.106.19 - 76 | 1541 | 377 | 162 | 175 | 307 | 163 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Edit: The Update Agent issue somehow solved itself after half an hour, and got to run the test on the original “Waiting…” on updates issue, here are the results:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 99 | 65 | 1 | 2 | 2 | 2 | 2 |
| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |
| 172.16.186.251 - 5 | 273 | 261 | 9 | 13 | 44 | 13 |
| 172.16.182.10 - 5 | 273 | 262 | 9 | 13 | 57 | 16 |
| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |
| 206.41.108.77 - 4 | 283 | 274 | 110 | 117 | 205 | 124 |
| 206.41.108.97 - 10 | 229 | 207 | 111 | 123 | 223 | 116 |
| 137.221.76.35 - 46 | 114 | 62 | 164 | 178 | 269 | 167 |
| xe-0-0-1-1-br01-eqda6.as57976.net - 39 | 126 | 78 | 163 | 175 | 271 | 173 |
| et-0-0-2-br02-swlv10.as57976.net - 13 | 213 | 187 | 158 | 175 | 296 | 159 |
| et-0-0-1-pe02-swlv10.as57976.net - 29 | 149 | 106 | 163 | 174 | 255 | 164 |
| las-swlv10-ia-bons-02.as57976.net - 41 | 122 | 72 | 163 | 176 | 255 | 166 |
| 137.221.105.17 - 33 | 138 | 93 | 163 | 177 | 271 | 188 |
| 137.221.106.19 - 7 | 252 | 236 | 162 | 176 | 282 | 163 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderCarlish38 - Thank you for taking the time to try those steps and post the WinMTR data! Both tests show 99% packet loss on the first hop, which typically indicates that a network-level firewall or other security measure is prioritizing or filtering certain network traffic. Was there any different behavior when you tried temporarily testing a different network such as a mobile hotspot? This generally helps quickly determine whether the issues are network-related.
If the updates continue when using an alternate network, at that point we can be sure that the issue is isolated to the primary network. In these situations, ultimately we can only recommend contacting the Internet Service Provider (ISP) for assistance determining what is causing the issue to occur on that specific network. They might need to adjust network-level security/firewall settings or temporarily replace the network devices in your home to narrow it down further.
I hope this helps narrow it down further. Let us know how it goes!
All I did was:
- Uninstalled the game (since the download never really started)
- Settings
- Downloads
- Network Bandwidth
a. Unticked “Limit download bandwidth” - Restarted Battlenet via forcing it in Task Manager.