Sueede

Pete. As I mentioned I changed in the registry/deleted the post as stuarth suggested. The error occured while I still had the former/next latest FSUIPC version. However the error reoccured after I installed the latest version and the registry post was there after the installation. The entry in DLL.xml concerned triggering xmltools.dll. This I deleted. Perhaps that was the key. Regards, Tommy

Thank you Pete. You have the FSUIPC.log file above. Here is the .ini file. I really dn't know how to provide the crash reports in the Event Viewer. But since I wrote that line I followed the instructions by stuarth and checked a recent dll.xml entry (although it is older than yesterday by a couple of weeks). Which operation that worked I don't know at the moment but it seems that my FSX-SE and FSUIPC4 work as they should. Thank you! FSUIPC4.ini FSUIPC4.log

Hallo. I run FSX-SE, Windows 10 updated, FSUIPC4.dll version 4.966c registered. Suddenly yesterday I am met with this message (enclosed). If I answer Ja/Yes FSX closes. If I answer Nej/No FSX opens. I hope this is enough for you to find the reason, maybe also the solution. Regards, Tommy Engman FSUIPC4.log

Pete - I registered my version of FSUIPC a couple of years back and have updated now and then, not because I had problems but in hope the new version would work even better (how that even could be possible - I never indulged in much of the possibilities for customizing that the registering allows). For quite a while though my FSX DeLuxe SP2 has crashed when in an airport and I tried to change aircraft, or trying to move to another airport directly. For these changes to work I have had to leave the flight/airport and return to the start page of FSX - and change or choose from there. (Sometimes that entailed crashes as well, but mostly it worked.) My idea for a long time has been that a new aircraft caused this, or perhaps a freeware scenery, or maybe scenery enhancements (UTX or REX4). Or maybe even the new version of IvAp. Well. Removing these extras, and removing this or these aircraft hasn't helped. Not uninstalling and reinstalling AvAp either and not deleting and reinstalling FSUIPC. So I finally - today - tried to eliminate that one or two of the newer versions of FSUIPC was the culprit. In my case the version 4.9.0.0 works without crashes in either case; changing aircraft or airport. The versions I have tried that don't work for me are 4.929 and 4.983c. If you are interested I will send all the logs you want (I mostly don't understand what they tell me or even where they all are). But at least this can be a comfort to others that have similar experiences, or at least it serves as a proof that an older might work very well. My setup: Windows 8.1 Pro 64, FSX De Luxe with SP2, AMD Phenom II x4, Gigabyte GTX660. Regards, Tommy Engman

Pete - thanks for your time and concern. I have to admit that although many have pointed out the hazards with addons I seem to be in too much of a hurry to respect these warnings. After your messages above I thought I chance on uninstalling an aircraft addon - FS9 twisted for FSX with warnings added in textfiles - and se what happened. And there wasn't any sign of problems with either FSX, SquawkBox or FSUIPC4. Or Win 8 for that matter. I have installed other freeware addon aircraft and scenery that were modified from FS9 to FSX and not had similar problems. So "Case closed" on this subject. But I can mention that my problems seem to have come from a Mike Stone ATR 72-500 in National livery that was converted - and which was supplied with an installer. The download file entitled nlatr72x.zip. So be careful out there. Thanks again, Pete! Tommy

Well - just when we thought all was well: After having had succes for a while flying on line with FSX also in Windows 8, I was faced this morning with the problem mentioned above, i.e. problems with FSUIPC4 when starting FSX. Yesterday, I had errors shutting down FSX after about twenty minutes of flying on line with SquawkBox on Vatsim. No mentioning of either SquawkBox or FSUIPC4. And today FSX wouldn't even load. So I followed the instructions regarding placing FSUIPC4_loader.dll in Modules and reinstalling FSUIPC4. After that FSX load was OK. But now FSX will shut down after a minute or five, after being on line with SquawkBox. Just now I loaded a new FSX session. FSX started OK. I waited a couple of minutes, and there was no shut down. Then evoked IvAp instead. IvAp started OK, and when I had connected on line and filed the plan for the flight FSX told me that it is sorry but has to shut down, and it will tell me whats wrong if it can. Sofar FSX has not been able to tell what's wrong any of the times. Nor has Windows8. The install log for FSUIPC4 reads - I'll paste the end of it here: Checking if there's already a version of FSUIPC4 installed in: C:\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL ... No previous valid version found. FSX Modules folder already exists. Okay -- installed FSUIPC4 into "C:\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Tommy\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Tommy\AppData\Roaming" Found FSX.CFG in "C:\Users\Tommy\AppData\Roaming\Microsoft\FSX\FSX.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4_Loader section already exists but will be replaced. (with FSUIPC4_Loader entry) ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... There is a SimConnect.XML, checking for "local" section. ... "local" section already exists, file not modified. "Modules\FSUIPC Documents" folder created okay! Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX controls.pdf" okay Installed "GlobalSign Root.exe" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay FSUIPC4.DLL installed and signature checked out okay! Deleted GlobalSign Root fix program ... no longer relevant =========================================================== All installer tasks completed. *************** End of Install Log *************** I do hope that there is a way to get FSX to work in Windows8, both on VATSIM and on IVAO. Regards, Tommy