kragsky

I still didn't find a solution. ED Member ''c0ff'' recommended to me install VisualC++ 2005 Runtime as well. http://www.microsoft.com/en-us/downl....aspx?id=18471 I just did it, but the problem persists. I'll ask him again for a solution.

I couldn't install, because windows says I'm using a newer version of the Visual C++ 2010.

I know, but how do I fix it ?

So... does anybody know how to solve this problem ???

It happened to me! I tried several times, uninstalled and re-installed DCS World and could not solve the problem. So, I gave up and installed my Windows XP in my other HD, and then installed DCS World in this new windows. This was the only solution I found.

I installed both of them, but the problem persists.

Does anybody know how to solve this problem ? I've just installed Windows7, made all the windows updates, and installed DCS World 1.2.4. This error occurs just after the end of installation, and happens again every time I try to run the game. DxDiag64.txt

If you uninstalled the DCS, why the installer didn't let you to install? And how do you happen to still have both versions installed at this point? Something is definitely wrong with the system. Installers do no have a habit to close silently. Install logs may be of some help. They are in the Temp dir, named "Setup Log (DATE) #(number).txt" Also you can try to use the Module manager. ******************************************************* I gave up and installed Windows (XP SP3) again in a partition in my second hard disk. Installation of DCS World is doing fine up to now. The ''old and buggy'' windows is still there in the first hard disk, with all my other programs. At least now I (hope) will be able to play. Thank you very much for your attention. I hope everything will be ok now. Best Regards

********************* I didn't use de module manager. First I tryed to use the updater. The updater ended with a pop up error message (happened with other several people of this forum too). When I noticed the updater wasn't working, I uninstalled the DCS World, BS2, FC3 and CArms. Then I downloaded the standalone installers. When I tryed to reinstall, the installer didn't let me install on the same folder the old (1.2.3) version was installed. Then I created a new folder and installed the new 1.2.4 version of DCS World. It worked (at that moment I had both versions installed). Then I installed CArms standalone. It worked but the ground units didn't lock their weapons. Then, I tryed to install FC3 standalone, but the installer kept closing itself seconds after openning. So, I tryed to install BS2 standalone, and it kept closing too. I lost my patience and then uninstalled version 1.2.4 and 1.2.3. Since then, I am not able to install neither the 1.2.3 nor the 1.2.4 DCS World because EVERY standalone installer closes itself just after oppening. (I use Windows XP SP3) I'm thinking of reinstalling windows but I don't want to do that...

****************************************************** Here it goes: ''Autoupdade.log'' content: * * * Begin * * * 00000.000 INFO : === MiniLog opened UTC 2013-05-02 02:32:43 00382.118 INFO : === MiniLog closed. * * * End of File * * * By the way, I'm new here, what is ''PM'' ? Regards

It is not possible because after being unsuccessiful in updating, I uninstalled DCS World. So there is no ''Repair DCS World'' anymore. As I cant re-install the game, I am stuck... that's why I am asking for help.

And I just CAN'T install because the installation wizard closes by itself just after openning. DCS World, CArms, FC3 and BS2, all of the installation wizards close just after openning... So frustrating. Now I just cant play anymore !!!

I had the same problem when trying to update DCS, but the error ocurred after 1 min (not 8 hours, thank God). So I downloaded the full file and installed DCS World AGAIN, in another folder. Then I installed CArms. Results: - CArms ground units now don't lock its weapons anymore. - FC3 1.2.4 installation program closes just after I run it, making it IMPOSSIBLE to install FC3 !!!! How I miss 1.2.3 ....

My target lock is not working too, after upgrade to 1.2.4. E eu também sou brasileiro (será que tem alguma coisa a ver com isso?).