How do I wake up the Blizzard Agent? I think it died... RIP

Support Technical Support
1

So the Blizzard Agent refuses to get out of bed, I’m not gonna chuck a bucket of water on my laptop to wake up the lazy thing, but I’m running out of ideas.

Over the last week I’ve tried restarting bnet, my computer, updating drivers, clearing caches and temp data, reinstalls, all of it multiple times, basically if it’s on the tech support section of the site I’ve tried it.

I can get it to the point where bnet app actually loads but then no games will update or let me play, and the Agent just goes back to sleep…

Can someone tell me how to wake it’s lazy a** up please?

2

Had the same thing the other day you can either just launch the game from inside your WoW folder or just restart your PC.

3

Hi there Zihizikuhl!

Don’t worrry, there’s a pretty easy procedure for waking up the Blizzard Agent ^^

  1. Close the Blizzard launcher
  2. Open the Task Manager and make sure the launcher and Agent are both closed
  3. Press Windows+R on your keyboard (I’ll give the mac procedure below)
  4. type %programdata% in the Run window, then hit enter
  5. In the Program Data folder, delete the Blizzard Entertainment and Battle.net folders completely.
  6. Re-start the Blizzard launcher :slight_smile:

If you use a Mac:

  1. Use Activity Monitor to quit all Agent, Blizzard Battle.net desktop app, and game processes.
  2. Using Finder, click the Go menu and select Computer .
  3. Navigate to the /Users/Shared/Battle.net/Agent directory.
  4. Delete agent.db and relaunch the Blizzard Battle.net desktop app.
  5. If the issue persists, delete the Agent folder inside the Battle.net directory and relaunch the Blizzard Battle.net desktop app.
  6. If the issue persists, go back to the /Users/Shared directory and delete the Battle.net folder.
  7. Launch the game using the Battle.net desktop application.

Hope that helps ^^

2 Likes
4

Same result, nothing will update or let me play and the Agentprogram goes back to bed.

I’ve repeatedly tried this, even uninstalled and reinstalled several times and cleared those folders and even the others that the tech support articles suggest. If the app loads and Agent isn’t asleep straight away, then it needs to update the games at which point the Agent decides to go back to bed again.

Or it can’t find the installed games to update despite me resetting the file paths and making sure everything is where it should be and such, at which point the app crashes and tells me to restart, so I do (yes I have tried both clearing and not clearing the programdata folder again in between - same result), and then the Agent is asleep again when I load it back up.

1 Like
5

The agent is notorious for this. It seems to happen everytime theres a significant patch, then blizzard will silently push out a hotfix that fixes it, for a while.

Sorry I can’t offer anything in the way of a resolution though.

6

This can indeed occur after application updates, but it isn’t generally actually us fixing it all silent sneaky-like via a hotfix… because in many cases the reason the problem occurs is actually a local security software no longer playing nice with our app (possibly because it is no longer recognized as safe, thanks to the update). In other words: this usually happens when the battle.net app it is no longer allowed/able to establish a connection to our servers, so it goes to sleep and waits to be “woken up” once a connection is permitted/available again.

These issues do tend to eventually disappear seemingly on their own (mostly because security program eventually update their database/definitions) but if that is not happening then the steps listed in the bluepost above are often useful. They essentially force-refresh the app in turn often prompting it being again correctly recognized by whatever software was so far suppressing it, which indeed may solve the problem.

If those don’t do the trick either the next step would be to look into all connection restrictions that may be imposed - firewalls/antivirus programs are a good first bet, setting up access permissions manually (or failing that uninstalling such programs) is definitely worth a try.
Beyond that router- and ISP-level restrictions may play a role too (especially in the current situation where many ISPs had to resort to throttling measures). It might be interesting to try and use a VPN, to see if that changes things at all - if it does that’d indeed strongly imply that some form of restriction is imposed onto the regular connection route.

1 Like