I recently got this error after playing co op mode with my friend. Tried the scan and repair but it says no repair required. It worked fine before so im not sure why i get this error suddenly
Hey, Quintin! This error is typically a connection related issue as the game isn’t able to connect to the depot to download the game data.
These steps may be able to help for some basic connection issues, but it may require additional information with the connection if these suggestions do not resolve the issue.
- Delete the Cache and Tools folder for the Blizzard Application.
- Close Background Application. Check for any content filtering programs like NetNanny and uninstall them as needed.
- Reset the network devices.
- Try an alternative connection. If this does work, it can help to try a different DNS service. This isn’t supported, but may be a better workaround and improve overall connection at times. By default, it uses the provider’s DNS, there are DNS services like GoogleDNS or Cloudflare.
If it continues, could you provide a WinMTR test while attempting to connect for 10-15 minutes? Copy and paste the text file created and paste it between two ~~~ like so:
~~~
WinMTR Here
~~~
So i’ve tried the above solutions but it didnt fix my problem, something weird is that in Co-Op i cant get past the error when it comes to normal missions yet when i tried playing mutation missions the error didnt pop up and it says i was searching for a game. I’m not sure why this error only pops up for normal missions but not mutation?
The symptoms for both the normal and mutation missions sound like there is a connection issue. Could you provide the WinMTR test requested above?
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.0.0.1 - 0 | 140 | 140 | 1 | 2 | 6 | 3 |
| 192.168.1.1 - 0 | 140 | 140 | 1 | 2 | 6 | 5 |
| lo-vprn-100.br1.mdr.vygr.net - 0 | 140 | 140 | 3 | 6 | 9 | 5 |
| ae-0-621.cr1.mdr.vygr.net - 0 | 140 | 140 | 3 | 18 | 179 | 7 |
| ae-1-0.cr2.mdr.vygr.net - 3 | 129 | 126 | 3 | 8 | 56 | 7 |
| ae-1-0.cr1.mdr.vygr.net - 0 | 140 | 140 | 3 | 18 | 168 | 6 |
| ae-1-0.cr2.mdr.vygr.net - 2 | 133 | 131 | 3 | 8 | 53 | 6 |
| ae-1-0.cr1.mdr.vygr.net - 0 | 140 | 140 | 3 | 17 | 162 | 3 |
| ae-1-0.cr2.mdr.vygr.net - 3 | 129 | 126 | 4 | 8 | 52 | 5 |
| ae-1-0.cr1.mdr.vygr.net - 0 | 140 | 140 | 4 | 18 | 178 | 8 |
| ae-1-0.cr2.mdr.vygr.net - 2 | 133 | 131 | 4 | 8 | 50 | 7 |
| ae-1-0.cr1.mdr.vygr.net - 0 | 140 | 140 | 3 | 18 | 168 | 6 |
| ae-1-0.cr2.mdr.vygr.net - 2 | 133 | 131 | 3 | 8 | 49 | 6 |
| ae-1-0.cr1.mdr.vygr.net - 0 | 140 | 140 | 3 | 17 | 160 | 4 |
| ae-1-0.cr2.mdr.vygr.net - 2 | 133 | 131 | 3 | 8 | 48 | 5 |
| ae-1-0.cr1.mdr.vygr.net - 0 | 140 | 140 | 3 | 18 | 160 | 8 |
| ae-1-0.cr2.mdr.vygr.net - 2 | 133 | 131 | 4 | 8 | 47 | 7 |
| ae-1-0.cr1.mdr.vygr.net - 0 | 140 | 140 | 3 | 18 | 160 | 7 |
| ae-1-0.cr2.mdr.vygr.net - 2 | 133 | 131 | 4 | 8 | 49 | 8 |
| ae-1-0.cr1.mdr.vygr.net - 0 | 140 | 140 | 3 | 18 | 156 | 6 |
| ae-1-0.cr2.mdr.vygr.net - 2 | 133 | 131 | 4 | 8 | 46 | 7 |
| ae-1-0.cr1.mdr.vygr.net - 0 | 140 | 140 | 4 | 19 | 155 | 8 |
| ae-1-0.cr2.mdr.vygr.net - 2 | 133 | 131 | 4 | 8 | 45 | 7 |
| ae-1-0.cr1.mdr.vygr.net - 0 | 140 | 140 | 3 | 20 | 155 | 8 |
| ae-1-0.cr2.mdr.vygr.net - 2 | 133 | 131 | 4 | 8 | 46 | 7 |
| ae-1-0.cr1.mdr.vygr.net - 0 | 140 | 140 | 3 | 19 | 155 | 8 |
| ae-1-0.cr2.mdr.vygr.net - 2 | 133 | 131 | 4 | 8 | 45 | 7 |
| ae-1-0.cr1.mdr.vygr.net - 0 | 140 | 140 | 3 | 20 | 156 | 8 |
| ae-1-0.cr2.mdr.vygr.net - 2 | 133 | 131 | 4 | 8 | 46 | 7 |
| ae-1-0.cr1.mdr.vygr.net - 0 | 140 | 140 | 3 | 20 | 154 | 6 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Tested with the host being: 202.9.67.254
Hey, Quintin! Thank you for the WinMTR test! There’s a DNS loop occuring in the test. It’s cycling through the same nodes over and over again. It’s never reaching the StarCraft II servers.
| ae-1-0.cr2.mdr.vygr.net - 2 | 133 | 131 | 4 | 8 | 46 | 7 |
| ae-1-0.cr1.mdr.vygr.net - 0 | 140 | 140 | 3 | 20 | 154 | 6 |
Have you tried an alternative connection and the third party DNS service like Google DNS mentioned earlier?
Those options should help workaround the issue. You will need to contact your ISP with this connection test to address this DNS looping issue. It may be a problem with the Top Level Domain list, somewhere between the system, home network, or ISP.
I’ve tried using a mobile hotspot and using the google dns, both did not work
EDIT: I’ve tried contacting my ISP and they said they have no solution since they never heard about the issue and the last time they checked theres no issues with their server.
Would a factory reset of the modem help? I just reinstalled windows so i dont think i want to repeat that process again. My pc is connected to a router not directly to the modem
EDIT 2: I have tried other modes and every single one of them works as in it managed to get to game starting and initializing, versus team, 1v1 etc it all works, even Mutation works fine, the only mode that does not work at all is the normal coop mode.
EDIT 3: It appears that the error disappears and coop works again when i reset in game settings via the battle.net app. For now no more errors.
Hey, Quintin! Thanks for the update. It’s a strange issue, especially with the connection test loops and this error, typically being a connection related issue with downloading assets. Glad it’s working for now! Just in case it does come back, let us know 