Hi,I've recently bought the Mc Donnell Douglas MD-11X for my FSX. After install it I launch Flight Simulator X, Then a message where I have to accept for using this software appear. I clicked Accept and after that, FSX stops itself.I had the 747-400X installed before this new installation and the both software are Boxed/DVD products by Aerosoft.Thank you

The common reason for this is something is wrong with the dll.xml file, you find this file in the same directory as fsx.cfg. The problem can be easily fixed: http://ops.precisionmanuals.com/wiki/How_t...SX_DLL.XML_FileLess common, you might look at this too: http://ops.precisionmanuals.com/wiki/FSX_Trust_DLL_PolicyHope it helps.

Thank You I'll watch it

Ok I'm not sure if i did it correctly but I tried it and that's don't work. Now i can't use the 747 or MD11

Copy and paste your dll.xml file here and let's see what is going on.

Ok I tried it again so I created a text file named DLL.XML then I added into the text:<?xml version="1.0" encoding="Windows-1252" ?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> </SimBase.Document>I put it into the folder which contain the FSX.cfg, Then I installed the 747-400X. No DLL.XML file appear and the file that I created looks like that:{\rtf1\ansi\ansicpg1252\deff0\deflang1036{\fonttbl{\f0\fswiss\fcharset0 Arial;}}{\*\generator Msftedit 5.41.15.1507;}\viewkind4\uc1\pard\f0\fs20 <?xml version="1.0" encoding="Windows-1252" ?> \par<SimBase.Document Type="Launch" version="1,0">\par <Descr>Launch</Descr> \par <Filename>dll.xml</Filename> \par <Disabled>False</Disabled> \par <Launch.ManualLoad>False</Launch.ManualLoad> \par <Launch.Addon> <Name>PMDG Options</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGOptions.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Events</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGEvents.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Sounds</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGSounds.dll</Path> </Launch.Addon></SimBase.Document>\par}PS:The first time I tried it the text wasn't the same.If something isn't correct please tell it to me.

The curly brakets " { } " don't appear anyplace in any of my xml files, I'm not sure what their function is and the header looks foreign to me. All instances of the "\par" are not anywhere in my dll.xml.If you delete the dll.xml then FSX should create a new one and when you launch a pmdg aircraft, you should be promted to trust the dll's. If this isn't happening then look at the registry error discussed in the second link I provided above.Here is my dll.xml for comparison (I have other things besides pmdg, your's will probably not have all the same Launch sections:

<?xml version="1.0" encoding="Windows-1252"?><SimBase.Document Type="Launch" version="1,0">  <Descr>Launch</Descr>  <Filename>dll.xml</Filename>  <Disabled>False</Disabled>  <Launch.ManualLoad>False</Launch.ManualLoad>  <Launch.Addon>	<Name>Object Placement Tool</Name>	<Disabled>False</Disabled>	<ManualLoad>False</ManualLoad>	<Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\Object_Placement.dll</Path>  </Launch.Addon>  <Launch.Addon>	<Name>Traffic Toolbox</Name>	<Disabled>False</Disabled>	<ManualLoad>False</ManualLoad>	<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>  </Launch.Addon>  <Launch.Addon>	<Name>Visual Effects Tool</Name>	<Disabled>False</Disabled>	<ManualLoad>False</ManualLoad>	<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>  </Launch.Addon>  <Launch.Addon>	<Name>PMDG Options</Name>	<Disabled>False</Disabled>	<Path>PMDG\DLLs\PMDGOptions.dll</Path>  </Launch.Addon>  <Launch.Addon>	<Name>PMDG Events</Name>	<Disabled>False</Disabled>	<Path>PMDG\DLLs\PMDGEvents.dll</Path>  </Launch.Addon>  <Launch.Addon>	<Name>PMDG Sounds</Name>	<Disabled>False</Disabled>	<Path>PMDG\DLLs\PMDGSounds.dll</Path>  </Launch.Addon>  <Launch.Addon>	<Name>FSUIPC 4</Name>	<Disabled>False</Disabled>	<Path>Modules\FSUIPC4.dll</Path>  </Launch.Addon>  <Launch.Addon>	<Name>Addon Manager</Name>	<Disabled>False</Disabled>	<ManualLoad>False</ManualLoad>	<Path>bglmanx.dll</Path>  </Launch.Addon></SimBase.Document>

Ok I've also tried it and nothing better :(

You would help yourself by adding a little more to your explanation of what you did and what the results were.

ok I'm trying to make only the 747-400X running so the DLL.xml operation don't work, the regedit operation (HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing) registry key don't work.When I have to choose accept or not I click on the Accept button and FSX shutdown itself.I tried the latest update and it also don't work.So it's always the same results or sometimes, FSX launch itself normaly and when I choose the PMDG 747, FSX close itself.Maybe a error of the FSX.cfg I delete sometimes? Can I have the lines code of PMDG please?

Unless you fixed you dll.xml file (that is, got rid of the problems in the copy you pasted in this thread) then this is your problem. Please delete you dll.xml, then restart FSX and select a default aircraft. If that works, select the 747X and report what happens.

Ok.What I did:(747-400X Uninstall)I deleted de dll.xml , I launched FSX, selected a Defaut aircraft and load somewhere. Then I quit FSX, I installed the 747 then I launched FSX the message appear: (Oui=Yes)(Non=no)I clicked Yes and FSX crashed.

Very good, I think the problem is the registry entry for the trust dll policy. Instead of the error message, you should have received a dialog box asking if you trusted three pmdg modules, which you would accept and they would be entered in the dll.xml. However, instead of being asked if you trust you are being told that there is an error. That is wrong, and I believe the reason is described and solution offered here: http://ops.precisionmanuals.com/wiki/FSX_Trust_DLL_PolicyYou will use regedit to make this fix. Advise if you need help with that.EDIT: Sorry, I see you already looked at that registry entry. The only suggestion I can come up with is to send an email to pmdg support, be sure you get an automated response. Please report back to the forum what the solution to this problem turns out to be.