I decided yesterday to purchase the e-Jets 175 early access version from Flightsim Studio through SimMarket. I got the purchase done and got the SimMarket e-mail with the product registration key, as always. After entering the provided key in the Aerosoft One App I could not install the product because the key couldn't be validated, so I immediately opened a ticket to Aerosoft Support to let them know the issue.

Then after, without any specific response from Aerosoft Support (yet), I got into their forums and noticed that there are several people reporting issues during the installation of this product related to a corrupted "exe.xml" MSFS file caused by the installer. Looks like some dependencies that needed to be installed (Aerosoft "Utilities") caused a deletion of all previous entries in the existing MSFS "exe.xml" file, producing CTDs. Obviously, something's wrong with the installer.

I'm waiting for the correct key and most importantly, to make sure the installers are working as they should before installing the product. A bit frustrating, to say the least.

Just to share my experience so far and to prevent others about these issues.

 

 

This is the link to the corresponding thread about the installation of the e-Jets 175:

https://forum.aerosoft.com/index.php?/topic/175168-install-issues-via-aerosoft-one-fss-e-jets-msfs/

 

Sounds like your issue is very different to the one in the thread which occurs when your entire MSFS install is not on the C drive. Installing via Aerosoft One does not require a key. 

Bought the E175 from AS on 16.01 and installed it without any issues through A1 Installer. My MSFS is not on Drive C but moved on another drive.

Frequent isssues preventing the instalation are:

- overly aggressive Antivirus SW -> these two have been the culprit of another failed installation (Acronis Cyber Protection and Webroot Antivirus)

- strange characters in usernames

- etc.

31 minutes ago, jarmstro said:

Sounds like your issue is very different to the one in the thread which occurs when your entire MSFS install is not on the C drive. Installing via Aerosoft One does not require a key. 

It does when you purchase through a different store

When you buy from another store, don't you enter the key on Library page of the A1 app and then it's treated the same way as something bought direct from Aerosoft ?

2 minutes ago, Matchstick said:

When you buy from another store, don't you enter the key on Library page of the A1 app and then it's treated the same way as something bought direct from Aerosoft ?

I'm not sure about buying directly from Aerosoft, but the provided key (in my case, from SimMarket), as you said, should be entered on that Library page of the AO (or A1) application to be validated and to proceed with the installation.

Unfortunately my key, even if it's valid (as stated by Aerosoft), cannot be validated as yet.

 

59 minutes ago, jarmstro said:

Sounds like your issue is very different to the one in the thread which occurs when your entire MSFS install is not on the C drive

As far as I understand, even if the main MSFS install is not on drive C, the "exe.xml" is located in either:

A) MS Store Version: "C:\Users\YOUR_USERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\exe.xml"

B) Steam Version: "C:\Users\YOUR_USERNAME\AppData\Roaming\Microsoft Flight Simulator\exe.xml"

Mine is Steam, and it's correctly in that location above.

If that is the case, that I think it is, the issue of the corrupted "exe.xml" file caused by the installer, has anything to do with the main MSFS install location, but that's up to Aerosoft to point out, once they're finally able to digest the issue.

2 hours ago, edpatino said:

As far as I understand, even if the main MSFS install is not on drive C, the "exe.xml" is located in either:

A) MS Store Version: "C:\Users\YOUR_USERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\exe.xml"

B) Steam Version: "C:\Users\YOUR_USERNAME\AppData\Roaming\Microsoft Flight Simulator\exe.xml"

Mine is Steam, and it's correctly in that location above.

If that is the case, that I think it is, the issue of the corrupted "exe.xml" file caused by the installer, has anything to do with the main MSFS install location, but that's up to Aerosoft to point out, once they're finally able to digest the issue.

No. In fact it depends on the options you choose when you install MSFS (store version). My exe.xml is on my F: drive along with all the complete MSFS file system. The issue is not that the file is corrupted it is that the installer assumes it's on the C drive. Other addons such as the Fenix and Maddog find the correct location just fine.

7 minutes ago, jarmstro said:

The issue is not that the file is corrupted it is that the installer assumes it's on the C drive

If that's the case, it's an installation problem to be resolved by the developer/Aerosoft, don't you think?

7 minutes ago, edpatino said:

If that's the case, it's an installation problem to be resolved by the developer/Aerosoft, don't you think?

Yup. The last email I had from Aerosoft support said that they were working to fix the installer. EDIT. In my case though I simply edited my exe.xml file, once I knew what the issue was, and it's now working. But as I have said it sounds like your issue is entirely different.

Edited January 18, 20233 yr by jarmstro

11 minutes ago, jarmstro said:

But as I have said it sounds like your issue is entirely different.

I cannot even install the thing...

@edpatino

 

I know. I can't help you. You need to file tickets with Aerosoft and Simmarket support. (Does Simmarket have support? I know not.) Despite their reputation Aerosoft do respond if not particularly quickly.

Grasping at straws and probably a silly suggestion but if you bought it using the app check on the web Simmarket site for a different serial number just in case you are using the order number or something? And visa versa.

 

Edited January 18, 20233 yr by jarmstro

12 minutes ago, jarmstro said:

Grasping at straws and probably a silly suggestion but if you bought it using the app check on the web Simmarket site for a different serial number just in case you are using the order number or something? And visa versa.

Well, a bit silly..., yes. Thanks anyway

17 hours ago, jarmstro said:

No. In fact it depends on the options you choose when you install MSFS (store version). My exe.xml is on my F: drive along with all the complete MSFS file system.

Are you sure about this? I can only repeat: I also have choosen to install MSFS on another drive but it still created symbolic links under C:.

Those symbolic links take nill space and the SIM is on my M.2 drive.

If you don't have the links under C, then your setup might be bugged. Did you "play" with BETA or other such things?

 

Edit just to show I'm not talking rubbish: https://flightsimulator.zendesk.com/hc/en-us/articles/360015910560-How-to-install-Flight-Sim-on-a-different-drive-

Edited January 19, 20233 yr by GEKtheReaper