atcogl

Hi John, Yes I only tried creating the AppData\Roaming\Microsoft Flight Simulator folder as you had suggested it as a possible fix for the installer not writing the EXE.xml. Like the others I tried that and the installer still did not create the file. Was just pointing out that fix didn't work for me either. Yes, In step 8, I had the EXE.xml file in both LocalState and LocalCache folders. As I don't have a full understanding of the file structures I wasn't sure what should be where so I tried a few things. My UserCfg.opt is in LocalCache so that would be why it works. I don't have that opt file in my LocalState. I'll report it to Aerosoft for sure, but would like to see confirmation from anyone else that they also had installed the Honeycomb software first as more evidence would be helpful just incase it might have been something else. Hope this has been helpful.

I have been having the exact same issue and I think I may have found the culprit. By any chance have you guys got Honeycomb Yokes or Throttles? My story: 1: Have been running FSUIPC7 with no problems at all until yesterday. 2: Yesterday I got my Honeycomb Alpha and downloaded the AS_HONEYCOMB_MSFS file that enables LED lights. 3: After installing this software I noticed FSUIPC was not starting anymore. 4: Uninstalled FSUIPC and re-installed several times. Then I noticed I was getting the EXE.xml not found error and the install was not completing. 5: Found that my EXE.xml had been totally removed from the AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState folder 6: Then I noticed that in the AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache folder was an EXE.xml and an exe_backup.xml 7: In the backup file was the entries to auto-start FSUIPC. The EXE.xml itself written by the Aerosoft installer looked strange. It didn't have any entries to launch and just contained this: <Launch.Addon> <Name>AFCBridge</Name> <Disabled>False</Disabled> <Path>D:\MSFS\community\AFC_Bridge\bin\AFC_Bridge.exe</Path> </Launch.Addon> 8: I re-created the EXE.xml in the LocalState folder and added the FSUIPC and AFC_Bridge entries into it, and fired up MSFS and FSUIPC started correctly again. 9: When I removed the EXE.xml file from the LocalCache folder and kept it only in LocalState then FSUIPC did not run. It is only with the EXE.xml in the LocalCache folder does FSUIPC start automatically. 10: None of the other suggested fixes worked, including creating the <USER>\AppData\Roaming\Microsoft Flight Simulator I'm not certain at all that the EXE.xml should be in the LocalState folder at all. John are you perhaps confusing LocalState folder with LocalCache? Once I fixed the over-written EXE.xml in LocalCache everything performed exactly as it should. The EXE.xml in LocalState did nothing at all. So to conclude my experience was that the Aerosoft Honeycomb software changed and over-wrote my existing EXE.xml in LocalCache deleting the auto-launch code and the FSUIPC entry.