Not starting, issuing that popout about the process being slow, and being logged...

Tried everything, but it does not want to start...It's XP12 time 🙂

EDIT:

So.. whatr I did so far...

.) Installed the latest NVIDIA App and drivers, that were on hold;

.) Ran the usual DSMC commands from the command prompt;

.) Deletede System Shaders Cache;

.) Deleted Simulatir WASM folder content;

Starting the sim again to check if it works now...

Edited April 29Apr 29 by jcomm

Ok found the culprit - the iFly 737 MAX which in all my tries to use it caused problems and instability in MSFS 2024... 

I remove it, MSFS 2024 starts OK... I put it back, MSFS 2024 doesn't start...

Giving up again on the iFly 737 MAX ...

EDIT: Turned out to be the only paintwork I had installed for it, through the iFly Manager - Cabo Verde Airlines... Uninstalled that livery and MSFS 2024 starts OK even with the iFly MAX .

 

Edited April 29Apr 29 by jcomm

My MSFS 2024 “Get started” times skyrocketed (went from 50 seconds to about 5 minutes) after installing my WinCTRL SimAppPro … to be clear MSFS starting NOT starting a flight (that time remains unchanged).

I do have iFly Max installed but will check liveries to see if I have that one installed.  I’d be really surprised that a livery could be responsible for the sudden change in MSFS 2024 start times … but ya never know.

1 hour ago, SayAgain said:

My MSFS 2024 “Get started” times skyrocketed (went from 50 seconds to about 5 minutes) after installing my WinCTRL SimAppPro … to be clear MSFS starting NOT starting a flight (that time remains unchanged).

I do have iFly Max installed but will check liveries to see if I have that one installed.  I’d be really surprised that a livery could be responsible for the sudden change in MSFS 2024 start times … but ya never know.

Thx! Please report black. It was the TACV livery.

1 hour ago, jcomm said:

Thx! Please report black. It was the TACV livery.

I’ve got all my 3rd Party stuff under management by Addon Linker. 

I’ve even got it controlling my Orbx scenery libraries since they have their own install locations. 
And I’m even going to delve into moving the Default addons over since there are so many I just never use (it’s “supported” as an Advanced Feature, so…🤞).

Aaaand…I’ve gone back through my MarketPlace purchases (including all the Aviator Edition addons) and Disabled not only the stuff that I rarely fly, but also almost everything that’s not officially labeled as v2024. 

Point of that is that:

A. My startup times are MUCH faster, and I almost never have system glitches or crashes of any sort. 

B. It’s literally just a couple clicks to disable ANY or ALL 3rd party content for troubleshooting purposes. Makes it super easy to zero in on even esoteric problems like that livery!

E.g., even tho the iFly is theoretically 2024 compatible, it’s still Beta, and so probably that livery is still 2020…? With all the changes under the hood in 2024, I can definitely see how that could be an issue 🤙

 

Edited April 29Apr 29 by UrgentSiesta

On 4/29/2026 at 10:09 AM, jcomm said:

Thx! Please report black. It was the TACV livery.

Unfortunately TACV Livery was not installed so that doesn't appear to be the problem.

 

On 4/29/2026 at 12:06 PM, SayAgain said:

My MSFS 2024 “Get started” times skyrocketed (went from 50 seconds to about 5 minutes) after installing my WinCTRL SimAppPro … to be clear MSFS starting NOT starting a flight (that time remains unchanged).

I do have iFly Max installed but will check liveries to see if I have that one installed.  I’d be really surprised that a livery could be responsible for the sudden change in MSFS 2024 start times … but ya never know.

As part of a support session I had with WINCTRL they indicated there should be no issue starting SimAppPro AFTER MSFS 2024 is up and running, including starting SAP after one has fully loaded a flight. Give that a try - that is my standard workflow on most flights and SAP connects to MSFS and the aircraft with no issue.