Official advice is to try logging in later when the servers are less busy.
This might be considered an exploit of the way that the client is reporting Error 37 to indicate that servers are too busy.
When started, they all check and update the same Agent files.
Abendschein, Ok, could you navigate to your C:\Program Data\Battle.net\Client\Blizzard Launcher.1949\Logs folder and delete the file called "Blizzard Launcher.log"? I assume it will fail again and when it does, please post the newly created "Blizzard Launcher.log" file from the above location.
Or is there another launcher version folder where you see Blizzard Launcher.1949 listed? If so, see if there's a Logs folder inside it with the log file I mentioned.
UI fix for OSX 10.9 template token, which works in conjunction with my People Support plugin to automatically include in upload captions and the like the names and/or ages of people in a photo.
Abendschein, Could you try what's described in the following two articles please?
https://us.battle.net/support/en/article/deleting-the-battlenet-cache-folder-pc? utm_source=internal&utm_medium=support_forums&utm_campaign=Blizzard CShttps://us.battle.net/support/en/article/deleting-battlenet-tools-folder-pc? utm_source=internal&utm_medium=support_forums&utm_campaign=Blizzard CSIf it doesn't help, since it appears you're playing from a campus, it would be helpful to know if any other students playing the game there are having similar problems.
Diablo III will block certain systems running the game if it does not detect a certain spec of video card.It makes for a hassle every couple of years, I know.Better handle some character-encoding issues related to template tokens.It was included by Adobe in Lr3, but as of Lr4 must be downloaded and installed manually.A missing 'automatic destination' could cause the plugin to crash.