I've had just a couple occurences of the "Loading 97% never ends" syndrome with FS 2024, and yesterday was my second encounter, after the quirks with the initial release of FS 2024.

Tried emptying the "Streammed content" folder and reloading FS 2024, rebooted the PC, no, I didn't empty the Rolling Cache because I don't think that can help with this sort of problem as well as with many other...

Then I recalled that on my first session of the day I had loaded after an update of the iFly 737 MAX, a session with that exact airplane... It lasted a very long while, and since I had to leave for work, I interrupted it, quited FS 2024, shutdown the desktop and came back at the end of the day...

It was then that, the first time I loaded FS 2024 the loading took so long that a message stating that "taking too long...." was shown... and in the various instances through which I tried to have success starting FS 2024 one after the other, it sloooooowly reached the 97% mark, and stopped there 😞

Well, fast forward, I decided to save the contents of the Community and then emptied it, and also edited the EXE.XML and made the entries for "Disabled" = True for each of the products I had in the Community folder that also created EXE.XML entries.

The first load with an empty Community was fast and effective.

Then I moved a few aircraft of the drag&drop type into the Community folder and restarted FS 2024 ... No problem again...

Then moved the FSLabs folders together with the FSLTL AI Traffic models and enabled the FSLabs entries in EXE.XML, loaded FS 2024 and voilá - no problem again...

Then repeated the same with the IniBuilds 350 and the Fenix 320... and eventually I had to go to bed...

FS 2024 started flawlessly and rapidly at each step, and the only addon now lacking is the iFly.

I plan to move the iFly 737 MAX folder into the Community later today, enable the entry in EXE.XML, and load FS 2024... If it gives me back that 97% loading quirk then I will uninstall and reinstall it ( and report it here! ), but the message I wanted to pass is that, most probably, most of the time this type of simulator loading problem happens when a product in the Community folder is installed or updated, and when trying to use it in a session the WASM compilations probably don't get to the end, are interrupted, or fail, leaving an incomplete compile state and driving the sim start into some kind of "never ending load".

Edited July 11, 2025Jul 11 by jcomm

Thanks for sharing your thoughts on this "undocumented feature"

Well,

as promised .. after playing around with the updates of FS 2024 and iFly 737 MAX since the OP I am now on:

- FS 2024 1.5.16.0 SU3 Beta

- iFly 737 MAX8 for MSFS 2024 1.0.4.2

or, no longer with the iFly until they / ASOBO get this 97% loading indefinitely quirk solved.

Whenever I install the iFly 737, try to load a flight with it - which I eventually have to interrupt after hours loading the situation, and then restart FS 2024, I get the 97% slow loading that never comes to an end 😕

I uninstall the iFly 737, all is back to normal...

So, at least in my case, the culprit was / is the iFly 737 MAX ...

OFC!!! They state very clearly at their DISCORD support channel that they can't support Beta branches / Flighting versions of FS 2024, so, I will just have to wait for SU3 to come to a final release, and then iFly to upgrade it's MAX for full compatibility 🙂

Edited July 12, 2025Jul 12 by jcomm

This thread deserves a justification because, the "quirk" was on me 😕

Today after reinstalling FS 2024 as suggested by ASOBO for the update to SU 3 1.5.23.0, I reinstalled my airliners and tried them all, and they all loaded without problems until I arrived to the iFly 737 MAX and the same happened - loading that never ends...

Well, it turns out that during install I explicitly chose not to start the iFly 737 MAX driver when FS 2024 starts, thus, having to manually start it before selecting the iFly! 737 MAX, and I was ** again ** failling to do so 😕

My bad !

It worked the other time I experienced this problem because most probably when I reinstalled it I opted to the automatic start of the driver ...

All is well, all is iFlying 🙂

Edited August 7, 2025Aug 7 by jcomm