Hello, I just bough Behind Enemy Lines, when I finished the installation, I tried to start it but a '' I can't find Directx 5 error'' appeared constantly. I just got my new computer 2 weeks ago with windows 7 and Directx 11, I tought that every thing would be alright with newest version of directx, but it doesnt.

Is anyone got this problem already ??? What could I do ???

Thanks

@thiev

İ ll try it. İ have same proplem.

Go to the Comandos.exe in the folder GOG Games\Commandos
and change the name Comandos.exe in Commandos.exe (only add the letter M) and the problem is solved. for Windows 10 and maybe more Windows Versions.

and don't forget a new copy for the shortcut on the desktop when you change the name of the .EXE file.

Actually this worked, So I'm going to assume there is a problema with the installer in Windows 10... Maybe the GOG team should look into this.

Thanks for the tip.

No, it's just a problem with Windows 10's in-built compatibility settings which were apparently assigned to a non-existing file :P That's not GoG's fault.

yes but they could let you know before buy it

Holy Crap! I pride myself at getting older games to work on newer systems...but I never would have attempted or even seen that it was misspelled. Bravo Sir...Sticky this. Oh BTW I am also win 10 x64

Hi, same issue here.
Just bought and installed commandos, when I launch the exe I got the "Can't find directx 5" error.
I tried to reinstall directx (even if I've a later version), and also renamed the comandos.exe to commandos.exe, but didn't work.
Any suggestion?

I am also having this issue, but within the Galaxy client.

Renaming the file works when you click the icon but not when you try to launch through Galaxy. Program locks up.

Just to provide one more tip here.

I can confirm that renaming the main executable to "commandos.exe" fixes the "DIRECTX 5 NOT FOUND" error. However, this prevents you from being able to open the game from the galaxy client.

To fix this, go to the game's installation directory (the same place where you renamed the main executable). Open the "goggame-1207662193.info" file in a text editor (i.e., right click, "open with", and select notepad, wordpad, etc.) and you'll see "comandos.exe" for the "path" variable under the "playTasks" section. Change "comandos.exe" here to match the renamed file "commandos.exe".

Save the file, exit the text editor, and then quit/restart the GOG client.

I can confirm that renaming "comandos.exe" to "commandos.exe" on Windows 7 64bit does NOT fix this problem. That's launching it directly by clicking on the exe file. Installing DirectX 9 did not solve the problem either.

Doesn't GOG actually test these games?

The store page says the game requires video hardware with DirectX 7 support, DirectX 9 recommended, so I'm not real clear on why there should be a DirectX *5* error, that makes not a lot of sense.

Solved my problem! Thanks

Tried adding the extra m in but still getting the same issue on Windows 10.

isnt the gog version updated the same as the steam version?

I believe steam version has work around for it.