This message appear everytime and i can't play this game i tried to use an eidos patch but doesn't work at all something strange it's the commandos 2 BCOD working fine to me :( any solution?

------------------
System Information
------------------
Time of this report: 1/18/2015, 17:41:05
Machine name: PC_TITO
Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.141211-1742)
Language: Spanish (Regional Setting: Spanish)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 12/10/13 11:42:18 Ver: 06.02
Processor: AMD A10-7850K APU with Radeon(TM) R7 Graphics (4 CPUs), ~4.0GHz
Memory: 16384MB RAM
Available OS Memory: 15298MB RAM
Page File: 4104MB used, 26488MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

Have you tried these steps: http://www.gog.com/support/commandos_ammo_pack/directx_file_not_found_d3dx9_43dll_etc

I tried but i have the same problem :(

try this one:

www.gog.com/forum/commandos_series/direct_x_5_not_found

Into the commandos directory, change "commandos.exe" to something else (e.g. "xyz.exe") then rename it back to "commandos.exe" . Just this fixed the issue for me and for other people.

Actually, the catch seems to be that you have to rename "comandos.exe" (with one "m") to "commandos.exe" (with two "m"-s) for some reason. I heard Windows 10 automatically deploys some compatibility changes to games it recognizes, so it might be an error on MS' part.

Thanks guys I had this issue after installing Win10 and I only added one 'm' to comandos.exe--> commandos.exe, and now it works like a charm, thanks again.
Too bad GOG team isnt supporting their customers and users have to find solutions by themselves.

As far as old and officially unsupported games go, you cannot depend on companies to help you, the respective games' communities often have better solutions than companies can and will ever have. It's that sort of age, you can't expect older stuff to run right out of the box (though some old games do run immediately), you have to Google around a bit.

This worked for me... what a wild fix. XD

Thanks!


EDIT: I did also follow the steps listed in the general crashing article ( https://support.gog.com/hc/en-us/articles/213039345 ) also, not sure if that helps or doesn't matter. But they didn't work and just adding the "m" finally did.

Hello i just installed today same problem as you guys even if i try to rename i get this message no clue how to solve it :)
Windows 10 64bit pro latest update

Go into the GoG directory on the drive you installed the game to (probably C:), Find the Commandos directory, look for a file that reads comandos.exe (I'm running W10, and it showed only as 'comandos'). Right click on it and rename it commandos.exe It should solve the problem.

You people are absolutely amazing! I've been wanting to play this since I got back into PC gaming a few years ago. I just bought it on sale and was determined to find a Win10 fix, but all it took was a trip to the forums. Thank you so much for sharing your expertise!

Doesn't work for me (windows 10 home 64-bit). Haven't tried this:
"Install the June 2010 DirectX runtime package, then use the DirectX web installer, as your current DirectX may have become corrupt over time. "

Could that cause problems with other games?

Hi, in my case it works only if I launch game directly from folder. It won"t work via Galaxy, which kind of sucks.

I've renamed it to "commandos" and still doesn't work...