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.

ronzie,

Thanks for the info.

Am waiting for the RC4 CD that I ordered and hope to run it with MCE.

Amazing what we put ourselves through to better enjoy FSX.

Tight Git,

In full screen mode you should be able to press the alt/enter keys together to change the screen size.

This combo will give you a means of being able to see your desk top icons.

After you have successfully started the extra programmes you can then work your way back to full screen mode using the alt/enter combo again.

Welcome to the Senior fight simming group.

I turned 80 in May.

As a customer who has been trying to use  MCE, since version 2.4.4.8, for ATC communications while flying small single engine aircraft and no co-pilot, I have to add my thanks to the MCE Team, Ben in particular.

Have currently had my license expire but am waiting for the next version to come out before asking for a new one --- again.

Edwin Brown Keremeos BC Canada. 

nathanpinard,

No, you don't have to buy a new license for each install  -- but as you can see -- they do expire and you have to contact the supplier for a new one.

 FS++,

Sorry to find out that I ventured into what appears to be a confidential area with such a simple question.

Hard to believe that the number of installs allowed for a license is that big of a secret.

Edwin Brown Keremeos BC Canada.

Does anyone know how many uninstall/reinstalls I should be able to get out of the new license I was issued on April 16 2014?

I know -----  have been told a number of times ----  you don't have to do a complete uninstall for every new version.

After so long at having little or no success, even with FS++ Team suggestions along the way, I finally did another uninstall/reinstall.

Once again, my license has run out.

I'm one of those PITA FSX users that has been trying to use the ATC only part of MCE to fly single engine small craft, VFR, no co-pilot, in and out of the small strips.

Edwin Brown Keremeos BC Canada

Thanks for the clarification.

Don't see any swings but do see the difference in core usage between having the "Enable Optimization" checked or not checked.

Problem solved.

MultiCrew Experience team sent me a new fsInsider.dll and the ATC menu now shows up as it should at the small non-towered strips.

Thanks to all.

charliearon,

Thanks for the pictures.

Have tried to post my pic here but following the Avsim instructions for posting just hangs my computer.

Obviously I'm not doing something right or am following the wrong instructions.

In any event, my picture shows different numbering and different options.

        Choose an option for L08 Traffic on 122.800:

        1-[ Tune L08 Automated Weather on 126.575 ]

        2-Announce Taxi

        3-Announce Clear of Runway

        4-Announce Takeoff-Remain in Pattern

        5-Announce Takeoff-Depart Straight Out

        6-Announce Takeoff-Depart North

        7-Announce Takeoff-Depart South

        8-Announce Takeoff-Depart East

        9-Request Taxi-Depart West     <<<<<<<<<<<<<<<<<<

        0-[ Select a Runway for Takeoff ]

I use MultiCrew Experience for my ATC and while troubleshooting my setup one of their team got the same weird menu item for #9.

I get the same at ALL small strips so something has gone wrong fairly recently.

Have no idea when this happened and sure don't know what to do to fix it.

Am afraid to go through the FSX repair operation because that really buggered things up last time I did that.

Hope someone can jump in here and suggest what I have to do. (Other than the FSX repair -- which I won't do again!)

Thanks for the explanations.

Next question (which I should have included in my original post).

Having 2 monitors I am able to watch all the core activity on one monitor and FSX in windowed mode and MCE running on the other monitor.

When the "Enable Optimization" check box is checked or unchecked should I be able to see the changes take effect on the core readings?

Edwin.

David,

Thanks for the reply.

I'm in totally uncharted waters here so please bear with me on this.

See my sig for my setup.

Am I to believe then that the MCE prog can take over control of core usage on my i7 970 6 core CPU and do a better job than my Windows 7 64 bit OS?

Seems to me I recall having selected the Windows 7 64 bit OS because of it's  superior capabilities in regards to multi-core CPUs.

Edwin.