Most likely it corrupted the dll.xml if you tried to install the traffic toolbox.  Yet, just installing the SDK on your HDD has absolutely no affect whatsoever to FSX's operation until you try to install something like the traffic toolbox.  It adds nothing to your FSX main folder.  It sits in a separate folder next to FSX but you have to run a program inside the SDK in order for it to do anything to FSX.  So, if you ran a program inside of the SDK, then look in your dll.xml and remove that line by changing the false to true, save, and go fly.

Nonsense. A dll.xml that is "corrupted" by an SDK installation will have no affect on FSX. FSX doesn't even need a dll.xml to run.

 

There is nothing in the SDK to "run" that will change the dll.xml.

 

The only thing the SDK entries in the sll.xml do is tell FSX where to find them and whether to run them or not.

 

A "corrupted" dll.xml will stop you from being able to use the 3 tools in FSX, it will not keep FSX from starting.

 

..you might be missing Microsoft Visual C++ 2005 w/SP1 (32 bit version). This is required for FSX to start up.

The FSX installer looks for any needed V C++ files and installs any missing ones.

 

They would only be missing if..

a) you copied FSX from another computer instead of installing it

B) you uninstalled them yourself, don't do that or

c) another program removed them when you ran it's uninstaller, which would be a bad idea on the part of the uninstaller writer.

 

Have you uninstalled anything else lately?

 

regards,

Joe

 

 

Nonsense. A dll.xml that is "corrupted" by an SDK installation will have no affect on FSX. FSX doesn't even need a dll.xml to run.

 

Nonsense!!  If you have a corrupted dll.xml, FSX may not run.  I have hundreds of examples in the AVSIM CTD Forum to prove my point.  There have been many members who have CTD's but, when they disable a module from running, the crash(es) will stop. 

 

It is a 100% proven fact that fsx will not start up if it is missing Microsoft Visual C++2005 w/sp1.  I do not know why you had to go through the iteration of how and why the MSV would be missing and just let the OP just look in his Add/Remove Programs to see if it was there or not.  It was almost like you were questioning my response. 

 

Best regards,

Most likely it corrupted the dll.xml if you tried to install the traffic toolbox.  Yet, just installing the SDK on your HDD has absolutely no affect whatsoever to FSX's operation until you try to install something like the traffic toolbox.  It adds nothing to your FSX main folder.  It sits in a separate folder next to FSX but you have to run a program inside the SDK in order for it to do anything to FSX.  So, if you ran a program inside of the SDK, then look in your dll.xml and remove that line by changing the false to true, save, and go fly.  If you did not run anything inside the SDK folder, then there is a problem with your installation.  One thing I found is a corrupted Addon Manager (if you have any programs that use it like FSDT airports).  Simply download the latest and install it.  If that is not the problem, then you might be missing Microsoft Visual C++ 2005 w/SP1 (32 bit version).  This is required for FSX to start up.  See AVSIM CTD Guide located under Hot Spots to the right of this forum for more information.

 

Best regards,

Uninstalling Addon Manager did not work. I do not have the dll.xml because I have uninstalled SDK. I am afraid that is the problem though. I used Airport Design Editor, which needs SDK. I have used it in the past many times, but I re installed my operating system and my FSX. Anything I can do? Also I can't find the C++ 2005 for 32 bit computers. I have run FSX many times on this computer many times just until I installed SDK. 

Nonsense!!  If you have a corrupted dll.xml, FSX may not run.  I have hundreds of examples in the AVSIM CTD Forum to prove my point.  There have been many members who have CTD's but, when they disable a module from running, the crash(es) will stop. 

 

It is a 100% proven fact that fsx will not start up if it is missing Microsoft Visual C++2005 w/sp1.  I do not know why you had to go through the iteration of how and why the MSV would be missing and just let the OP just look in his Add/Remove Programs to see if it was there or not.  It was almost like you were questioning my response. 

 

Best regards,

I do have C++ 2005, but I'm not sure about sp1.

Nonsense. A dll.xml that is "corrupted" by an SDK installation will have no affect on FSX. FSX doesn't even need a dll.xml to run.

 

There is nothing in the SDK to "run" that will change the dll.xml.

 

The only thing the SDK entries in the sll.xml do is tell FSX where to find them and whether to run them or not.

 

A "corrupted" dll.xml will stop you from being able to use the 3 tools in FSX, it will not keep FSX from starting.

 

The FSX installer looks for any needed V C++ files and installs any missing ones.

 

They would only be missing if..

a) you copied FSX from another computer instead of installing it

 you uninstalled them yourself, don't do that or

c) another program removed them when you ran it's uninstaller, which would be a bad idea on the part of the uninstaller writer.

 

Have you uninstalled anything else lately?

 

regards,

Joe

I installed FSX from my two discs. I have only uninstalled the FSDT addon manager after it was not working somehow. My terminals disappeared. I just uninstalled it again. That might be the problem.

Thank you to everyone who helped me with this issue! I uninstalled my addon manager and it worked! Thanks especially to firehawk44 or Jim Young. This is a great aviation form!

 

Nonsense. A dll.xml that is "corrupted" by an SDK installation will have no affect on FSX. FSX doesn't even need a dll.xml to run.

 

 

Nonsense!!  If you have a corrupted dll.xml, FSX may not run.  I have hundreds of examples in the AVSIM CTD Forum to prove my point.  There have been many members who have CTD's but, when they disable a module from running, the crash(es) will stop.

Did you fully read what I posted?

 

How many of your examples in the CTD forum were caused by an SDK installation?

 

And of those hundreds of examples, how many were caused by the dll.xml and not the module itself?

 

It is a 100% proven fact that fsx will not start up if it is missing Microsoft Visual C++2005 w/sp1.

I never said FSX would run without the libraries.

 

I do not know why you had to go through the iteration of how and why the MSV would be missing and just let the OP just look in his Add/Remove Programs to see if it was there or not. It was almost like you were questioning my response.

I was simply pointing out that the FSX installer includes all needed dependencies and gave the very few possible reasons for them not to be there.

 

And I was questioning your response in those 2 regards.

 

I did suspect that it could be a problem with the Addon Manager and it turns out I was right. So were you.

 

 

Uninstalling Addon Manager did not work. I do not have the dll.xml because I have uninstalled SDK. I am afraid that is the problem though. I used Airport Design Editor, which needs SDK. I have used it in the past many times, but I re installed my operating system and my FSX. Anything I can do? Also I can't find the C++ 2005 for 32 bit computers. I have run FSX many times on this computer many times just until I installed SDK.

 

I did not want you to uninstall the Addon Manager.  I recommended you download the latest and reinstall it.  If you uninstalled it, then any of your FSDT products will not work.  The dll.xml is installed when you install FSX.  It has nothing to do with the SDK.  The latest C++2005 link is in the AVSIM CTD Guide.

 

Best regards,