Q u o t e:
The very first thing i told you was that i experienced the very same thing you do and how I fixed it. I guess up to now you did not follow that advice.
I also told you that Diablo II.exe DOES NOT require a network OR internet connection, it never had, it never will. All Diablo II.exe does is a sanity check of the installation and settings and that's it!
Look at this image and try to follow me:
https://public.s
n2.livefilestore.com/
y1pMhen-S6LoQOE4n_G4O
-jxHgXSzCgxRYKXUZ2-Y4
mN5tLWVYxGu73xSxsHWqg
cuE-A5rqaTXYnOA0Ywxza
YcR5A/diablo2naocorre
.png?psid=1
1 - In that image I double clicked the shortcut to Diablo II.exe without internet access.
2 - Rundll.exe comes up at the same time pointing to gameux.dll because it detected me running Diablo II.exe
3 - Rundll.exe is hogging 25% CPU, Diablo II.exe is at 0% CPU and waiting for some thread in Rundll.exe to proceed.
4 - Gameux.dll is a Microsoft Game Folder/Explorer thing related, attempting to update something but unable to, unless I connect to internet.
5 - The game didn't run at first try. Gameux.dll is the culprit.
Now there are 2 possible paths for this, path A, or path B:
A - Connect to internet, and see rundll.exe and Diablo II.exe misteriously disappearing and Game.exe taking place and the game starting. Clicking Battle.net does indeed connect to Battle.net with no errors.
or
B - Click again the same shortcut to Diablo II.exe. Another Rundll.exe appears momentaneously, but disappears. Now I got 1x Rundll.exe, 1x Diablo II.exe and 1x Game.exe all running, the game boots but, in the background I have Rundll.exe hogging 25% CPU and a Diablo II.exe at 0%, and the actual Game.exe taking another 25%.
Now 2 things could happen from option B once I connect to the internet. Thing 1 and Thing 2
Thing 1 - Without exiting the game via Exit Game button
1 - I connect to the internet
2 - I receive an error message - "Only one copy of Diablo II can run at the same time"
Thing 2 - After exiting the game via Exit Game button
1 - I connect to the internet
2 - Misteriously getting Diablo II starting up unexpectedly
B was happening many times on my parents computer, in their case with 100% CPU usage being distributed to Game.exe and Rundll.exe slowing down the whole computer. Thing 2 was also what they were experiencing, they actually believed they had a virus or malware, but nope, it's...
RUNDLL.EXE / GAMEUX.DLL - a microsoft issue ruining the whole thing!
----------------
---------------------
---------------------
---------------------
---------------------
---------------------
-----------------
That's part of 'Diablo II.exe' shortcut issue. 'Game.exe' shortcut issue has already been explained. And my game installations are not corrupted. Because I tried the exact same installation version twice:
One is installed on Windows 7 Ultimate 64-bit. The other is installed on Windows XP Mode. Each installation in different folders.
On Windows 7:
- Starting up the shortcut pointing to Game.exe WITH YOUR PROVIDED SETTINGS, with internet access would end up with Unable to identify game version when connecting to Battle.net. Doesn't ask for permission when starting up. Does run at first try with or without internet access.
- Starting up the shortcut pointing to Game.exe with my settings, with internet access will allow me to connect to Battle.net, but asks for permission when starting up. Does run at first try with or without internet access.
On Windows XP Mode:
- Starting up the shortcut pointing to either Game.exe or Diablo II.exe with '-window' after it and no additional setting changes, would run the game and let me connect to Battle.net, NO ERRORS, NO FUSS, NO STUPID QUESTIONS, NO ISSUES, NO PROBLEMS, just like everything should be from the beginning.
Both installs are patched manually in offline mode, no internet connection.
Both versions are EnGB.
