EXE.xml entries not launching after switching to SU4 Beta

User Support Hub Install, Performance & Graphics
, , ,
1

Hi everyone,

I recently switched from SU3 to the current Sim Update 4 Beta (MS Store version). Before doing so, I made backups of important files, including my exe.xml, because I use several external programs that normally start automatically with MSFS (such as FSRealistic, the Fenix A320 app, FS2Crew, Aerosoft VDGS driver, Couatl/GSX, etc.).

After installing the SU4 Beta, none of these programs start automatically anymore. I tried replacing the new exe.xml with my backed-up version, but that doesn’t seem to change anything – the programs still don’t launch with the sim.

It looks like SU4 may have changed the way the exe.xml is structured or how it is being read.

Has anyone else run into this issue with the Beta? Is there a specific fix or adjustment needed so that external apps start correctly again?

Thanks in advance for any help or tips!

Cheers,

Stefan

2

Check the test of your exe.xml file. There may be incorrect references to the locations of the apps you plan to autoinstall.

1 Like
3

Hi, I have exactly the same problem since today, but with the SU3, anyone else in this situation ?

4

Since Asobo has probably fixed SU4 compatibility with 3rd party aircraft, I’ll check the iFly 737MAX shortly. I’ve already prepared the exe.xml file and I’ll paste its contents below so you can compare the lines.

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="SimConnect" version="1,0">
	<Descr>Launch</Descr>
	<Filename>EXE.xml</Filename>
	<Disabled>False</Disabled>
	<Launch.ManualLoad>False</Launch.ManualLoad>
	<Launch.Addon>
		<Disabled>False</Disabled>
		<ManualLoad>False</ManualLoad>
		<Name>iFly Plugin</Name>
		<Path>T:\MSFS 2024\Community\ifly-aircraft-737max8\Data\Tool\737MAX_Plugin.exe</Path>
		<CommandLine>auto</CommandLine>
		<NewConsole>False</NewConsole>
	</Launch.Addon>
	<Launch.Addon>
		<Name>SPAD.neXT</Name>
		<Disabled>False</Disabled>
		<Path>c:\Program Files\SPAD.neXt\SPAD.neXt.exe</Path>
		<CommandLine>-m</CommandLine>
    </Launch.Addon>
    <Launch.Addon>
        <Name>Aerosoft VDGS Driver</Name>
        <Disabled>False</Disabled>
        <Path>t:\MSFS 2024\Community\aerosoft-vdgs-driver\aerosoft-vdgs-driver.exe</Path>
    </Launch.Addon>
</SimBase.Document>

For reference, I have MSFS 2024 launcher installed on drive C to avoid any file permission issues (like with exe.xml), while MSFS Packages (Official and Community) are located on a different drive. I also always run MSFS 2024 from administrator account - Windows 11 24H2.

Stuck at home with covid, so I’ve got way too much time for testing haha.

EDIT

As I already mentioned, I keep the MSFS 2024 launcher on drive C and never moved it, so my exe.xml is located here:

C:\Users\YourUserName\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\
1 Like
5

Get well soon!

I also use the default location of the exe.xml

I deleted my MSFS2024 Launcher Exe and created a new desktop shortcut from the MS store… maybe that is the issue? But how to i create the MSFS2024 Laucher Exe again?

6

Thanks!

I have the standard desktop shortcut that was created during the MSFS 2024 installation. I don’t mess with it, because less tinkering makes it easier to find the cause of any problem.

MSFS 2024 has just started up and along with it, SpadNext, iFly plugin and Aerosoft VDGS-driver also launched.

1 Like
7

I think I may have found the cause of my issue. A while ago, I deleted my old desktop shortcut for MSFS2024 because the icon wasn’t displaying correctly. Since then, I’ve been starting the sim either from the Windows Start Menu or by creating a new shortcut via the MS Store/Xbox app.

The problem: this new shortcut doesn’t give me the option to “Run as Administrator.” Previously I always launched MSFS as admin, and that might explain why my external apps (FSRealistic, Fenix, GSX/Couatl, etc.) no longer auto-launch through the exe.xml.

So it looks like the exe.xml itself may not be the problem – it could simply be that the sim isn’t running with admin rights anymore, which prevents the external tools from starting properly.

Has anyone else run into this, and is there a reliable way to create a desktop shortcut that always runs MSFS as Administrator (MS Store version)?

8

exactly same problem, my shortcut has changed since this morning, and I no longer have the possibility to open it as administrator, I think that the problem comes from there for the exe.xml, i don’t understand why ?

1 Like
9

As I mentioned, I’ve got plenty of time, so I’ll delete the desktop shortcut and create a new one using the Xbox app, to see if it might trigger an error - or maybe not.

EDIT

@Dustoff2002 @FredLock5679

After creating the MSFS 2024 shortcut via the Xbox app, the option to run as administrator was not available when I right-clicked the shortcut, so I deleted it from the desktop.
Then I went to C:\XboxGames\Microsoft Flight Simulator 2024\Content, right-clicked on FlightSimulator2024.exe and selected show more options → send to → desktop (create shortcut).

A shortcut was created, but it looked ugly without the MSFS icon. So I right-clicked the new shortcut, chose properties, went to the shortcut tab and clicked change icon → browse. I navigated to C:\XboxGames\Microsoft Flight Simulator 2024\Content, selected the file SmallLogo.ico and clicked open → ok → apply → ok.

Now, when I right-click the new shortcut, the option to run as administrator is available.

1 Like
10

We are so lucky that you have plenty of time :slight_smile: Thanks for your great Help. You should apply as a moderator here :smiley:

1 Like
11

334 / 5 000

Thanks, I tried but unfortunately I don’t have the run as administrator option, but I found another solution in the meantime, I had the shortcut in the start menu, I was able to launch it as admin, and everything works again on my side! but impossible to put the shortcut on my desktop, but at least it works now !

1 Like
12

If you followed the instructions the Run this program as an administrator option is in the compatibility tab of the shortcut properties.

1 Like
13

Thanks for the kind words! Fly safe mate.

14

I have no compatibility tab on the shortcut small logo !

15

OK, try a different tack. Instead of creating a shortcut using the .exe just create a shortcut on the desktop and then browse to select the .exe file.

That definitely works and has a compatibility tab as i have just done it.

16

Yep

image
image403Ă—534 17.4 KB

I think you might not have read the instructions carefully. If you created a shortcut to the SmallLogo file.

Please read the instructions again
https://forums.flightsimulator.com/t/exe-xml-entries-not-launching-after-switching-to-su4-beta/740598/9?u=tenpatrol

1 Like
17

ok sorry, i have do that but i have a message : Windows cannot access the device…

18

Moved to User Support Hub > Install, Performance & Graphics as a solution has been marked for the issue, and the issue is with windows permissions on a shortcut , and not a regression in SU4.