AAO was starting fine with MSFS just yesterday. Then, to get the remote CDU for PMDG's 737 working, I had to enable it in Admin mode. That's the only change I've made to it. Now it won't start with MSFS. Here's what AAO is inserting into exe.xml:

 

  <Launch.Addon>
    <Name>LorbyAxisAndOhs</Name>
    <Path>C:\Program Files\LorbyAxisAndOhs_MSFS\LorbyAxisAndOhs_MSFS.exe</Path>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <CommandLine />
    <NewConsole>False</NewConsole>

When AAO is supposed to start "As Administrator", MSFS must be started "As Administrator" too. Otherwise MSFS is not allowed (by Windows) to start AAO because of missing execution privileges.

On 11/27/2022 at 10:48 AM, Lorby_SI said:

When AAO is supposed to start "As Administrator", MSFS must be started "As Administrator" too. Otherwise MSFS is not allowed (by Windows) to start AAO because of missing execution privileges.

Thanks! This fixed it. It also fixed the issue with Couatl for GSX not starting that was driving me crazy. 

Small tip on the side, you can also call AAO with extended rights (admin mode) without UAC query. To do this, create the task in the Windows Task Scheduler (with highest priorities) and call the task in the exe.xml - f.e. with the following code:

<Launch.Addon>
<Name>schtasks</Name>
<Disabled>False</Disabled>
<Path>C:\Windows\System32\schtasks.exe</Path>
<CommandLine> /run /TN "AAO"</CommandLine>
</Launch.Addon>

In this case, "AAO" ist the name of the Windows-Task.

If you don't want to have this in the exe.xml you can also make a shortcut on the desktop with the same commandLine (call schtask from c:\Windows32\schtasks.exe). After that you can give this shortcut the icon from the original AAO-exe file.

You can do this with any other program that needs Admin Rights.

Summary: Don't call AAO directly - call the task. 🙂

 

Edited November 29, 20223 yr by plerzelwupp