Ah, sorry... no, it can't be a Windows 7 x86, since the dll on both systems (x86 and x64) are the same. It is only, that the 32 bit dll on the x64 system is in the syswow64 instead of system32 folder... on Vista it's the same. The whole 32bit stuff on a x64 bit system is in the syswow64 folder. So, the "real" system32 folder on a x64 system is the syswow64 folder... but, because of the redirection system of windows, every 32 bit process accessing the system32 folder on a 64 bit system is automatically redirected... :-) ... a bit complicated, I know... but that's how it works...OT: I never understood, why they didn't rename the system32 into system64 on 64 bit systems... but, that's Microsoft... that's politics, not informatics...

So just to clear up my last question then. I can replace the .dll in the system32 folder with the .dll from the syswow64 folder, and that would give me the .dll that would fix the issue? Or does the new .dll absolutely have to come from a x86 version of Vista?

So just to clear up my last question then. I can replace the .dll in the system32 folder with the .dll from the syswow64 folder, and that would give me the .dll that would fix the issue? Or does the new .dll absolutely have to come from a x86 version of Vista?

ONLY, if these points are true (both):1) You have a Windows 7 32 bit system and the System32 folder you are talking about is on your system.2) The Syswow64 folder is on a Vista x64 system.Then yes... but I don't recommend that. You only want to use this dll for FSX and not globally on your system. Maybe this (the copy action) (as well as registering an old version with regsvr32) could cause other problems. So, my recommendation is to place such a 32 bit version of the dll right beside the fsx.exe into the fsx folder. For me this worked... if you want, you could verify the result with the process explorer.so, again where to find the dllVista 32 bit System -> in the system32 folderVista 64 bit System -> in the syswow64 folderwhere to copy the dll toFSX main folderthis works for Windows 7 32 bit and 64 bit !! (at least it worked for me, FSX with acceleration pack or SP2)

Well, I've copied the .dll into my folder, but when trying to use the process manager to verify, fsx.eve*32 loads both when I make no changes, and when I place the .dll in the FSX main folder. Does that mean that it had always been using a 32 bit version of the .dll? or what? I guess I'll just place the .dll in there and start flying. If I can make 10 solid flights with multiple clicks and no crashes, I'll figure that its solved.

Well, I've copied the .dll into my folder, but when trying to use the process manager to verify, fsx.eve*32 loads both when I make no changes, and when I place the .dll in the FSX main folder. Does that mean that it had always been using a 32 bit version of the .dll? or what? I guess I'll just place the .dll in there and start flying. If I can make 10 solid flights with multiple clicks and no crashes, I'll figure that its solved.

Hey Jordan, As far as a process showing in task manager, it will always show as fsx.exe *32, because it is a 32 bit program.Good luck with your tests.

Hey Jordan, As far as a process showing in task manager, it will always show as fsx.exe *32, because it is a 32 bit program.Good luck with your tests.

That's kinda what I figured, but wasn't sure how else to use the process manager to verify if the .dll was being loaded.

Well, I've copied the .dll into my folder, but when trying to use the process manager to verify, fsx.eve*32 loads both when I make no changes, and when I place the .dll in the FSX main folder. Does that mean that it had always been using a 32 bit version of the .dll? or what? I guess I'll just place the .dll in there and start flying. If I can make 10 solid flights with multiple clicks and no crashes, I'll figure that its solved.

Hi... the FSX is always a 32 bit process and since a dll is always loaded into the calling process, it has to be of the same type like the process. This means, you were always using a 32 bit dll. Never a 64 bit version.With the process explorer (from sysinternals) you can list all dll loaded in a process (click on the dll symbol on top of the screen). There you will see, that the fsx.exe loaded a uiautomationcore.dll and when you right-click it and open the property page of this dll you can see the path of the file and you will find out, that it uses the one from the fsx folder.I know, it can be a little bit difficult sometimes... when you're working with this (as I do) the whole day long, things become a bit more clear, but some things ever remain a mystery :-) ...

Well I thought I was out of the woods, but it appears I'm still having the issue. I was able to verified with the Process Manager that FSX is indeed using the .dll placed in its folder. I obtained the .dll from the wowsys64 folder from a 64bit version of Vista as your post said. If I absolutely have to get it strictly from a 32 bit version of Vista, I'll have to look around. Would it perhaps be possible to obtain the .dll from an XP system? I do have a 32 bit version of that I could look in.EDIT: NM, I managed to find a 32 bit version from another thread about the issue. Though they are saying you need to replace the file into your systems file as well. I'm going to try just leaving it in the FSX folder to begin with as it has a significantly smaller file size than the one I was using. And yes I checked for viruses before I extracted the supplied .dll

So Jordan...did that fix work? I just upgraded to W7 64bit and am having the CTD issue.