2.25 crash Exeption_accesss_violation

[Lucinator]

when I try to start the new version I get this error message.  Any Idea why?  My old 2.1 works fine

Exception in thread 3544 - Main Thread
Exception code EXCEPTION_ACCESS_VIOLATION
    The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
    Attempt to read from address 00000018

Exception occurred at 0091C0AE - Unknown code pointer

[Corey]

You may have interfering files installed to your base data folder.

[Lucinator]

reinstalled FOC same results, maybe it has somthing to do with the fact that 2.1 has a installer?

[Lucinator]

nevermind the 2.15 also works and it is a manual install so still no idea why 2.25 is not working.

[Corey]

When you reinstalled FoC did you delete the remaining folders? Uninstalling it won't always remove unexpected files, since it doesn't know they're there to get rid of in the first place.

[Lucinator]

yes, and I reinstalled the game in a different location just to make sure.  It just wont work.  Based on 2.15 working I feel like its something that changed.  Do you still have a copy of 2.2 I could try.  I could see if it works.   Another odd thing is that I cant run the Batch file as a admin, it just flat out crashes.  Lastly is there a way to check if the FOC vista patch has installed correctly?

[Corey]

Honestly, this is why we generally suggest people upgrade to the Steam, version. Aside from just being more stable in general as a result of the patches PG has released over the last year, there's fewer variables users have to account for. There isn't an easy way to know if the ram fix has applied, no.

The biggest relevant change for the mod actually running between 2.15 and 2.2 is that 2.2 requires more to be run out of the mod's actual folder. That's about it. The game without the aforementioned EaW patches is also less capable of running it properly, hence why we've had to cut things like map previews and VOs from the Disk and GoG releases.

1. Are you running everything as admin?
2. Are you running in compatibility mode?

[Lucinator]

finally got a fix.  After some more work trying everything I could think of I tried to use a different vista fix.  And for some reason that seemed to work.  why, I have no idea but it did.