Game won't launch - "Error: Command failed"

Need help installing the mod?
trolley
Dark Huntress
11 | 2
After troubleshooting with #tech-support on discord, they're out of ideas and understandably swamped with other requests for help.

So here's the low down on my issues, others in discord are posting the same thing.

Launching from the launcher, or directly with no shortcut options the Diablo 2/Game.exe files provides the same result - nothing happens. Using the launcher gives this error message:

[2019-01-18 09:50:13 11:00] Error: Command failed:  "C:\d2fresh\Game.exe" -w -3dfx -skiptobnet
||


Troubleshooting things I've tried:
  • I've installed/reinstalled multiple times, using both 1.13 unofficial and 1.14 official blizzard installers. New/different folder each time
  • Enabled, disabled DEP (always rebooting after a change)
  • Tried every Video Mode setting in the launcher
  • Reset default glide settings (still had my old MXL17 glide settings), glide test works fine
  • Disabled windowed mode, in-game sound, skip main menu options. All combo's tried with the video mode settings.
  • Registry cleanup with CCLeaner, in between the restarts and reinstalls
  • Ran LoD before installing Median XL - launched fine, connected to BNet and performed a small update. Then installing MXL through the launcher, the game wont run with the above error. I've tried this without installing the small BNet update with the same result.
It's probably worth adding, that when launch occurred and I eventually got Sigma to download, it launched OK and i was able to log into TSW. I had the 1678 error, and after a few reinstalls got the c0000005 error. Then I tried DEP, back to the 1678 error, and a few reinstalls later i'm now in the state where the game won't launch at all.
Edited by trolley 6 years.
Vagabondage
Acid Prince
49 | 0
run game.exe with -w command line.
trolley
Dark Huntress
11 | 2
Vagabondage wrote:run game.exe with -w command line.

Same result, doesn't run.
etern1ty
Imp
4 | 0
I'm getting the same issue. Tried everything that OP listed as well. I was able to play in single player but I exited that and tried multiplayer but got the c000 error. Now i'm just getting the same shit with the error_log.txt.
dyanikoglu
Fallen
1 | 0
Same problem. Still no solutions, what a shame.....
User avatar
lunar.seven
Grubber
326 | 8
hi guys, dont run the game.exe itself, run the launcher and press PLAY button

i recommend the following to check


i recommend, you get an clear d2 installation

you can copy an d2 installation and put it somewhere in your programm directory, use this for the MXL Launcher Installation, the Launcher itself gets the correct gateway information to your computer, at the setup steps in the installation

try following the steps:

make sure you cleared the old installation from your computer,

by going to software deinstallation, deinstall the mxl launcher from sigma

redownload it,

find the correct spot for the installation, incase your D2 directory, where you want to put the installation in

and follow the steps with the installer

if there comes an error,

then it is better to start new

and delete old directories before

i recommend clearing any registry from last hours from failed mxl sigma installations first

there is an app data directory, it gets the launcher information aswell, make sure, that you delete all before try to new install it
its in the admin app data directories, in the end its called Median XL

you can find all stuff by using the programm: Everything

its an searching programm, very good for using

try to find all Median XL directories and sort them out, that have been created today, delete them

then start over a new installation from scratch



best regards
trolley
Dark Huntress
11 | 2
Hi Lunar, thanks for the post but I had already tried what you recommended.

UPDATE. Launcher 1.0.6 fixes the "Error: Command failed" issue.

The game still doesn't run.

I click 'Play', the launcher minimises, I get the loading circle on the cursor for 4 seconds, and then the launcher comes back up. Diablo 2 doesn't run.
Deafwave
Cultist
22 | 11
Great Supporter Badge
Donated 5 times
Common Contribution Badge
Has collaborated to our forums, realms or mod
Launcher version 1.0.6 + a restart should fix 99% of these cases. If this does not work for you, I'll need more context outside of the game doesn't run.

1. Is everything installed to the C:\ drive? Or are Median XL Launcher or Diablo II (or both) installed to a different drive such as D:\?
- Can try reinstalling to C:\ drive
2. Is Diablo II installed to Program Files?
- Can try reinstalling to non-program files directory

Thanks.
trolley
Dark Huntress
11 | 2
1. I've tried everything installed to C:\ root folders (shudder), both Launcher and D2 in their own on the same disk. Currently 'installed' on my desktop.
2. Nope just installed to C:\D2

If it helps i can provide the sysinternals process monitor export for game.exe :)

I'm in #tech-support-2 on discord if you'd prefer.


EDIT: Issue was resolved by deleting Median XL related folders in %appdata% (you can just type that straight into windows explorer). Open the Launcher again and hit play, and hey presto, it worked.