Sign in to follow this  
Ronnie1968

Can not open up Config Manager

Recommended Posts

Hi,

 

I  have a problem with the 737 NGX REBOOT CONFIG MANAGER, as that I can not open it up. I've turned off the UAC and downloaded again, I have also ran as admin, but no joy as of yet..

 

I'm sure what the problem is. I have done another install, but still the same.

 

I'm running windows 7, with ESET firewall etc.

 

Thanks

 

Ronnie

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hey Ronnie, have you tried to disable your firewall?

My guess is the Config Manager needs an internet connection.

 

I've once had a similar problem with another FSX Tool using Privacy Firewall 7.0. Had to shut it down completly and after that the tool worked fine.

Share this post


Link to post
Share on other sites

Cheers Fabian.

 

I've tried that, also I've tried running in another compatibility mode. I'm at a lose end with it now...lol. I have put in a ticket, but I thought maybe guys have had similar issues...

 

It's the first problem I've ever had with a FSX installation.

 

I'm running FS2crew on a SSD (E drive) as all my FSX is separate to my hard drive. 

 

I take it FS2crew needs to be directed to my FSX on my SSD and can't run from my other hard drive as a stand alone program.

 

Thanks anyway.

Share this post


Link to post
Share on other sites

 

 


I take it FS2crew needs to be directed to my FSX on my SSD and can't run from my other hard drive as a stand alone program.

 

 

Correct, and I replied to your ticket.

 

The FS2Crew installer should auto detect the location of your FSX/P3D install.

 

FS2Crew needs to go into your root FSX/P3D folder.

 

Don't try installing it elsewhere.

Share this post


Link to post
Share on other sites

It does auto detect to my E drive, where fsx located. I will look later, I'm just off for a few beers. :rolleyes:

 

Thanks for the quick reply Brian, and I will get back to you tomorrow.

 

Thanks

 

Ronnie

Share this post


Link to post
Share on other sites

You probably have a corrupt Dot Net file somewhere.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this