flying engineer

Stuart, Found 2 fsinsider reg entries and deleted them. Happy to say that I can now start FSX and MCE. Thank you very much for the help. Edwin

Am back being unable to use MCE due to fsInsider.dll. Identical to topic started 39th Sept 2015 by myself. All was working OK for quite some time using version 2.6.7.3. Then, for some reason, FSX was not able to start up. Renaming fsInsider.dll allows FSX starts up OK. Reviewed all the help suggestions from back in 2015. Never did get a fix and ended up doing a complete reinstall of my entire system to get MCE up and running. Am not going to do that again and will just give up trying to use MCE if no easy fix is available. I really enjoyed MCE when it was working and the FS++ crew put a lot of effort into helping me right from day one many years ago. Am hoping that someone has found an easy fix for this problem and can post it here. Edwin Brown Osoyoos BC Canada

Two problems; 1: After a flight, aircraft is shutdown, sitting cold and dark. Avionics off of course. Headset/mic turned off -- even unplugged as a test. FSX and MCE is still active. Trav and attendant still making comments? 2: Something triggers a repeating function, approximately every 25 to 30 seconds, that causes the comment "back" to show up in the red letter area at the top left of the windscreen area. This, in turn, causes the ATC window to open. These two events keep going on and on until finally FSX and MCE are shut down.

Would be nice to include the Quest Kodiak by Lionheart Productions.

Stuart, Yes, all registry entries were lost. Guess you know what I've been doing since Oct 16th. So far so good on all the reinstall of FTX ORBX etc etc. Sad to say that MCE has gone strange again but too busy for that problem right now. Ed.

Finally did do a complete clean install of Windows 10 Pro, FSX and MCE version 2.6.5.4. Happy to report that I'm back up simming as opposed to tinkering. Thanks to all for the help. Edwin

Had to do a complete clean install of Windows 10 Pro, FSX and MCE version 2.6.5.4 to solve my problem. Back up and simming as opposed to tinkering. Edwin Brown Osoyoos BC Canada

Gus, Good for you. Nice to be flying rather than seeking/tweaking. Gerald, FSX runs better than ever in either DX10 or 9 as long as there is no fsInsider.dll in the FSX folder. Uninstalled Eset Nod32 as you suggested. Restarted computer. Ben had sent me two Windows 10 fsInsider.dll files to try. One was not optimized the other was optimized. Sorry to say that trying either file in DX9 or DX10 works. Get the same series of warnings and no FSX start up. Seriously thinking of doing a complete reformat of both my main C drive and the SSD dedicated drive for FSX. Does mean starting all over again with a clean install of Windows 10 and then FSX. Not looking forward to this but if that is all that's left to try then so be it. Could also go back to Windows 7 Pro but seeing that others have MCE working in Windows 10 pro leads me to believe that there must be a solution to fix my problem. Edwin

Gus, Thanks for getting in here. At least you can get FSX and MCE combo up and running under Windows 10. No such luck for me -- so far. Gerald, Ben has been helping me by sending me different fsinsider.dll files to try -- to no avail unfortunately. Have had UAC off from day one. Always have any program startup as Administrator. Dx10 Preview on with Steve's fixer. Here is the latest instruction from Ben: To confirm dll isn’t loading, open “fsInsider.ini” (not the dll) and change “Debug=0” to “Debug=1”, then save the file If fsInsider.dl loads, when FSX crashes, you should see a “fsInsider.log” file in same folder. This trial does not create the fsInsider.log as expected. FSX shuts down with the same series of warnings that have come up every time. Have also completely disabled Eset Nod32 virus protection program prior to any trials, just in case the Exclusions I have set up are not working. Edwin Brown Osoyoos BC Canada ​

70 views and no replies? Here is the entire content of the warnings that I am getting when trying to start FSX: "Flight Simulator has detected a problem with a third-party software program(add-on): Name: FSinsider Version: 2.6.5.4 (also the same with versions 2.6.5.44 & 2.6.5.45 sent to me by FS++) Company: FS++ Limited File: fsinsider.dll Do you want to run this software (not recommended)?" Choose "Yes" FSX fails to start and the following messages appear: "To avoid seeing this message in the future, uninstall this program or disable it's ability to start when running Flight Simulator. For more information about third-party programs, contact the publisher or see http:/www.fsinsider.com" "A fatal error has occurred. Windows is checking for a solution" " Microsoft Flight Simulator X has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. Close program" Has anyone had this problem and found a fix? FS++ has been very helpful in trying to clear this up but no luck so far. Edwin Brown Osoyoos BC Canada

Steve Sumner, Glad to hear you've had success with FSX-Steam. I do not have FSX-Steam. Am still with the original Deluxe edition with the Acceleration pack, DX10 with the fixer and my own FSX-DX10 profile in NVidia Inspector. Am curious how the Steam advertisement got into the Windows 10 warning that comes up when trying to run MCE. Here is part of the warning message in question: "To avoid seeing this message in the future, uninstall this program or disable it's ability to start when running Flight Simulator. For more information about third-party programs, contact the publisher or see http:\www.fsinsider.com​" fsinsider.com takes me to the advertisement for the Steam edition. I am not interested in switching to the Steam edition. Don't know who is responsible for inserting the suggestion of going to the Steam site. I know I don't like it. The FS++ team from MCE has sent me several fsinsider.dll files to try but am still getting the same warnings. FSX is excellent on it's own. Edwin Brown Osoyoos BC Canada

Has anyone had success in using MCE after upgrading to Windows 10 Pro? MCE was running fairly well under Windows 7 Pro with version 2.6.5.4. Now I can't get any success in getting past the warning about the FSinsider.dll. "Microsoft Flight Simulator X has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available Close program" FS++ crew has sent me a number of different FSinsider.dll files to try. 2.6.5.44, 2.6.5.45 the latest but still no luck. Just wondering if anyone can jump in here and give these guys some help in what must be one hell of a job to try and keep up with all the changes coming down. Ed Brown Osoyoos BC Canada

Was running WINDOWS 7 PRO and MCE version 2.6.5.3. Went to Windows 10 Pro and lost many functions in MCE. Was advised by FS++ Team to go to version 2.6.5.4. Did so and now can't get FSX up and running at all. Get the following warning: Flight Simulator has detected a problem with a third-party software program (add-on) Name: FSinsider Version: 2.6.5.4 Company: FS++ Limited File: FSinsider.dll Do you want to run this software (not recommended) Option of yes or no Yes shuts down FSX screen and all is dead. No allows FSX startup but no MCE of course. Tried going back to MCE version 2.6.5.3 which was not working good but at least allowed FSX to run. Get the same warning and opting for "yes" shuts down FSX and all is dead. Am waiting for reply back from FS+++ Crew as to what to do now. Ed Brown Osoyoos BC Canada

OK. Not to worry about that anymore. Just have to nose up to the screen with different reading glasses on. I did read the FSUIPC guide mention of not being able to make any changes but thought that having been able to change the colour from red to white meant that something may have changed since that manual was issued and editing could now be done. Thanks for clearing that up.

Did find the help to change the RC4 menu red lettering to white. Am now wanting to know if and how the font size can be increased for better visibility? Am not a Wide FS user by the way.