Battle.net launcher "updates" every time

  • So, I believe the title here pretty much says it all. Every time I open up the Battle.net launcher since Patch 2.0.5 came out, it seems to think that I have to update D3. It's not even changing the build number (23920), though, so it seems to me to just be a glitch.

    The game runs fine after the 5 seconds of "updating." It's just annoying and, certainly, shouldn't be happening.
  • Hey all,

    Issues with the Update Agent getting stuck on an update or checking after exiting a game are usually resolved by deleting some specific files related to Battle.net. Please try closing the Battle.net App and restarting first, and if that doesn't work, give deleting these files a try.
    ______________________________
    Technical Support: Sunday-Thursday, 12pm - 9pm Pacific Time
    How am I doing? // https://www.surveymonkey.com/s/Glaxigrav \\
  • Alright. Let's go a bit higher out and delete all Battle.net folders:

    1.) Using Finder, click Macintosh HD.
    2.) Navigate to the /Users/Shared directory.
    3.) Delete the Battle.net and Blizzard folders.
    4.) Relaunch the game.

    There are some files in the Blizzard folder that Battle.net will reference as well; this should remove *all* traces of the Battle.net cached items and allow it to progress after a restart.
    ______________________________
    Technical Support: Sunday-Thursday, 12pm - 9pm Pacific Time
    How am I doing? // https://www.surveymonkey.com/s/Glaxigrav \\
  • Much appreciated. After I had posted that I ran my Mac through it's paces to see if I could resolve it locally as well... no dice. I'm going to confer with Machkhan tomorrow and we'll touch base with the Mac Engineers and see what we can do. :)
    ______________________________
    Technical Support: Sunday-Thursday, 12pm - 9pm Pacific Time
    How am I doing? // https://www.surveymonkey.com/s/Glaxigrav \\
  • Hey dribble,

    I just responded to your thread over in the Mac Battle.net forums. Can you take a look and send us the files?

    After that, if you're affected by this problem as well, try our workaround listed here.