EDIT: This issue is solved. I installed it on my main drive instead of my backup drive and it worked. Very strange; no idea why that would be the case.

My specs are as follows:
Windows 7 64-bit
Intel Core i5 CPU, 2.80GhZ (4 CPUs)
6 GB RAM
AMD Radeon HD 6670 with latest drivers

The game goes to the splash screen, then starts up but disappears without an error message about 5 seconds later.

I've tried compatibility modes, installing the old directX files, disabling visual themes, and getting rid of the config file. Also looked for directions under Support, but nothing works. Even Safe Mode doesn't work. Anyone have some insight?

I just wanted to say: I had the exact same problem, and after hours of fishing through message boards and fiddling with the GamerProfile.xml file, I tried installing on C: rather than my copious USB 3.0 external drive... and for whatever reason, that worked. So, thank you.

I still think it's downright stupid that Ubisoft's game has such a lousy error reporting process, but that's on them.

Wow it worked, thanks a lot, I was pretty dissapointed with no being able to play the game I bought

Am having the same issue now with v1.03. Have checked the install drive and it's not a random drive, it's the same one as the OS (which happens to be the ONLY drive). Verified files, no luck. What a pain, can't play the game.

Do you by any chance use the GoG Galaxy client ? I had the same problem (and still kind of have): It wouldn't start through GoG Galaxy. Same problem as described above. Splash screen, then just nothing. However, by simply starting the game through the shortcut (if you don't have it, you can go in the game's installation folder and either find it there or directly start the .exe), it works normally.

For some reason GoG Galaxy mess up the launch.

Yes, I am, Durango! Shortly after posting I tried launching with the .exe as you said you had luck with and it worked for me too. Great that I can play the game but a pain we can't use the client to launch it easily.

Thanks for replying!

In my case, the game launched fine the first time.
I changed a few graphics settings, including setting the DX version to 10.

I restarted the game to apply my changes, and then it would crash after the splash screen.
To fix this, I had to go open:

C:\Users\[user name here]\My Games\Far Cry 2\GamerProfile.xml
which can be opened in Notepad.

Somewhere under <RenderProfile>, there's:
Platform="d3d10a"

which I changed back to:
Platform="d3d9"

Now the game works again.

Just thought to say that disabling the GoG Overlay fixed the crash on startup for me. :)

I also needed to revert the DX version from 10 to 9.

There seemed to be a number of DX related settings in GamerProfile.xml, so I just temporarily disabled cloud saves then deleted GamerProfile.xml (you need to disable cloud saves else GOG client will restore the file)

It is generally advisable to use DX9 instead of DX10, because there's a known bug which makes the game crash after moretheless 70 minutes of gameplay, but only with DX10 renderer. With DX9 you can play for hours without any trouble.

how do you do this?

don't know if it's fixed by now by Galaxy 2.0, but you can disable it by going into settings; game features; and untick Overlay.

I have issue launching Far Cry 2. It only displays splash screen after start and is closing after few seconds ( dont even start FarCry 2 process in task menager).

Any help or suggestions?

Win 10 64

AMD Ryzen Threadripper 1950X
32 GB Ram
Geforce 2080

Hi guys,
I had the same problem with FC2 crashing after displaying splash screen for a few seconds. Tried all of the solutions known to humanity (meaning first 2 Google result pages) with no success.

I found a solution for this very particular issue. I believe some people here might have actually experienced the same solution and unknowingly worked it around by installing the game on another drive.

Long story short, I have a set of WD NVME drives (SN850+SN570) which is one of the few brands supporting the option to choose sector size when secure erasing the disk. You can choose either 512b (default) or 4096b. I decided to format all my drives with 4kB sector size and now I found this is what caused the issue.
After reformatting (secure erase) with the default 512b sector size the game works.

You can check check the sector size with this command:
fsutil fsinfo sectorinfo c: [where c: is the disk you want to check, so if you have the game installed on d: then use this letter instead)
Then check the first result line:
LogicalBytesPerSector : 512 is fine
LogicalBytesPerSector : 4096 is not

Why noy to use normal Windows format function? There is no issue choosing sector size there. Well, for my external WD drives.
And using x64 Win7Sp1+hotfix and Win8.1+hotfix. Cant say for Win10. Some minor issues happened for Win8. Intially aalow to format external USB drive to differ filesystems, after first format it list only NTFS (hm, and maybe FAT32 but who cont it today?)

And yes, first thing that i do when but and connect harddrive to PC (any OS) - reformat what been there even pre-installed soft. Its always useless.

Anyway, thanks to at least one possible reason why random Windows randomly silencly dont start games for many peoples. Never have a clue why that happned for many people... so at least here the one reason.