Windows 10 installation question

[Codfangler]

Hi, I have spent a day look through the forum and on-line to look for an answer to my issue so apologies if this answer is already buried in here somewhere already.

I am getting an Event ID 1903 from source HHCTRL error launching in Win10 64Bit (I7 and 16Gb mem). Which refers to XML code launch. I am running the disk based 1.0 software install as I recalled you had to first launch before patching on the original. I then tried to launch the 1.8 with patch and got the same result, am I doomed to buy the steam version or if the forum aware of a fix for this launch error?

Many thanks in advance

[WWJD]

well, if you installed 1.8 then make sure you are launching the alliesnew.exe as administrator, see if that helps, if not report back and we can keep working.

WWJD

[Codfangler]

I have tried dowloading and dropping the 1.83 framework into bin and launched the Alliesnew exe as Admin to got the screen error 'An Error has encountered while setting up the appication' Plus event Id's 1903 as above and 916 'svchost (4840,G,98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.' in the app log. I have only audit sucess messages in the sec logs. System log shows
In most launch attempts I get only the 1903 event. the other only appears when using the the troubleshhoting tool in win10.

[WWJD]

does it run without the patch? You could also try going intot he config folder and removing the file with "current" in it.

WWJD

[evilernie]

i can only get the (Allies windowed) to work

[WWJD]

are you running as an admin?

WWJD

[pablomm1b]

WWJD I do have the same problem with the 1.8 patch and i do not know what i have to do with the patch or where should i put it

[WWJD]

once you DL the patch just copy the giles into the original PSA game files. Replace anything it asks you to. The game files for PSA can be found if you right click it in steam and find the file location option.

WWJD

[Codfangler]

Thanks WWJD, aftere reading through loadds of thtreads and lots of debugging I discovered theres a call to the disk in the non steam version that is now blocked by win10. I followed the advice and bough the game in a sale on steam and it worked better than it ever did back in the days of 1.0 and 1.1 until I started to run into long battles. I have commented on another thread for that. Thanks again.