This was likely due to using a VPN, hosting / cloud service or a business / enterprise connection, which can cause a temporary restriction. “the IP you were using to connect to the game was temporarily suspended and as a result, the CD key has also been suspended for 2 weeks.” So, since none of the troubleshooting helped, I opened up a ticket and got a response fairly quickly, stating, I keep getting this error message any time I try to connect to Battlenet: I’ve tried them all and nothing fixed the problem. After wasting my limited free time trudging through the forums and searching on Google, I found several different sets of troubleshooting steps.
This will allow the patch to run the way it normally runs.I recently re-installed Diablo II and have not been able to connect to Battlenet once. Then click Ok, then right click game.exe and run as administrator. Then go to the Compatibility tab, tick the box for “Run this program in compatibility mode for” and select Windows XP service pack 3. If that is not enough, right click Game.Exe and select properties. Once you’re at the old account login, you can close the game and launch as user again. So the fix is simply to right click Game.exe, run as administrator, and it should finish up the patch. If you change Game.exe to run for XP SP3, you will see the UAC (User Account control) box but cannot click it. The stemming issue is the non-admin launch, combined with UAC prompt, combined with old full-screen applications… the UAC prompt cannot launch because of compat issues. At this point, the bottom left of my screen indicated that i was at the most recent v1.14D patch - it never installed successfully, but the game is not smart enough to detect this. Future attempts to go to online would result in 0% patch download followed by the disconnected error message. At the end of the download, 100%, it gave me the disconnected error message. I launched diablo for the first time, clicked battle net, and then it downloaded the patch. The account i log in with is a normal user not an administrator.
0 kommentar(er)
