FSC Administrator doesn't start

[01thomas]

Hi

I'm new to FSC and my Administrator doesn't start.

I get a pop-up with an error which says "FSCaptain Administrator is reporting this Write failure condition 3/3770" (or 3/3716 or 3/3732 etc). When I accept that one I get another one which says: "I could not create a file in the FSCaptain\Config folder".

If I OK that I get a very brief flash of something and that's it.

I'm running FSC 1.8.2 (simConnect SC-64) with Windows 10 Pro and P3D 4.5 although when I try to start the Administrator I haven't yet started the sim.

Has this occured before and if so what's the solution?

Regards

Thomas

[Travis]

Hi Thomas,

I've dreaded a post like this... that Write Failure should be preventing us from creating logs for me to review.

I'm going to make a wild assumption that you're running from a securely protected set of folders, and that you are not running the FSCaptain Administrator 'as Administrator' from Win10.

Could you check if that's the case - just right click on the Admin icon or menu item and select "Run as Administrator" and see if that works any better.

Best,

[01thomas]

Hi Travis
Thanks for the tip! I've changed the default values for the Administrator and the MCDU to 'Run as Administrator' and that seems to have done the trick.

Onward!

regards
Thomas

[01thomas]

More help needed...

Hi
I'm now at the point where I can start the FSC Administrator, but only if I use the Windows10 Run As Administrator function... even though I've adjusted the permissions in the Security tab.
Also, even if the FSC Administrator is open and running there is no Icon in the Win10 taskbar as there is for other active applications - is this normal? It's certainly unusual. Furthermore if I try to minimise the FSC Admin by clicking the Minimise button in the top-right corner it dissappears completely. The only way to get it back is by the Win10 Administrator function.

I have completely uninstalled FSC as per the notes in the PDF file and then reinstalled it but these issues haven't gone away.
Any Ideas?

regards
Thomas

[peter]

Hello Thomas,

Aug 17, 2020 16:01:21 GMT -5 01thomas said:

I can start the FSC Administrator, but only if I use the Windows10 Run As Administrator function

Let me guess: you installed your simulator in the default directory (C:\Program Files\ or C:\Program Files (x86))? If yes, I would advise to reinstall the simulator if it is not too inconvenient. There are many issues with read/write permissions in that folder caused by Windows, and this causes problems not just for FSCaptain, but for many other third-party programs as well. If reinstallation is not an option, "run as administrator" should normally help.

Aug 17, 2020 16:01:21 GMT -5 01thomas said:

if the FSC Administrator is open and running there is no Icon in the Win10 taskbar as there is for other active applications - is this normal? It's certainly unusual. Furthermore if I try to minimise the FSC Admin by clicking the Minimise button in the top-right corner it dissappears completely. The only way to get it back is by the Win10 Administrator function.

Yes, that is actually how the Administrator is supposed to work. The reason is that, in this way, the Administrator can be launched from both within the simulator and outside of it. I agree with you, it is unusual. The way I deal with it is
- I only open the Administrator for flight planning and dispatch, i.e., before I even start a flight.
- On rare occasions, I have to open the Administrator during a flight. In that case, I pause and minimize the simulator. The Administrator window is never gone, it is just hidden behind other windows, mostly the simulator itself.

Cheers,
Peter

[01thomas]

Hi
Yes I installed P3Dv4 in the default location. If I have reason to reinstall it I'll move to some other location.

Thanks
Thomas

[peter]

Hi Thomas,

If the Administrator works for you with Windows10 "Run As Administrator" settings, then just use these settings and report any problems that may occur here. More often than not, this is sufficient. However, sometimes users experience issues that can only be resolved by re-installing P3D in another directory. Usually, that's a lot of work,so consider this as a last resort option.

Cheers,
Peter

[Travis]

Hi Thomas,

No matter where you install P3D (or FSX, etc.) you should always have the simulator "Run as Administrator" so that the OS won't try to deny it read or write access to anywhere.

Likewise all Flight Sim addons should be set to "Run as Administrator".

And yes, that could have security implications, but the risk is lessened if we know what we're doing....  Also, each time I run FSX or P3D... and their addons, I have to answer "yes" to the "Do you want this app [...] to make changes to your device?"

And as Peter alluded to, the Administrator is a Property Page, not a regular "Windows Dialog" so it can be used inside FS9 to P3D5.  That's why it's not visible in the Desktop's taskbar.
----

When I installed FSX back in 2010 or so, I initially let it install into Program Files(x86).   Within a few weeks, I literally moved my installation to a separate drive and adjusted one or two Registry keys.

Such is not as simple with P3D or newer flight simulators.  I really do not like to uninstall something and reinstall it unless I'm forced to.

Best,

[nppinto]

Hi! Have the same problem. Tried to start Administrator under as Admin. made exclusions inantivirus. No result. Log divided on 3 parts due to limitations

Attachments:

ADMIN_20210402_095732.log (957.34 KB)

[Travis]

Hi NPPinto,

You've found an AI package new to us, and it is overwhelming the Administrator.

Please update your \FSCaptain\Config\no_scan_folders.txt file with the one I'm attaching here.

Let us know if this does not fix your issue.

Best regards,

no_scan_folders.txt (7.27 KB)

[nppinto]

Thank You much! Everything is OK now!

[Travis]

That's great!

But if you could please do me a favor, email me your newest ADMIN log.  I would very much like to see the difference between the new log, and the one you posted here on the forum.

Best regards,

[nppinto]

Hi! No problem

Attachments:

Log1.txt (810.98 KB)

Log2.txt (796.23 KB)

ADMIN_20210403_081436.log (822.9 KB)

[Travis]

Hi NPPinto,

Thanks.  Everything looks correct in your current log file!

Best,