It’s exactly what happened here, so I decided to visit the iFly Discord to look for a solution. Reinstalling the B38M was one of the approaches I tried. The MSFS2024 freezing issue appears to be caused by the iFly plugin, which starts correctly via the exe.xml instruction but then suddenly disappears (crashes?), leaving MSFS2024 frozen. I followed the developers’ instructions to reinstall the B38M, but before doing that, I also decided to reinstall MSFS2024 itself, since Asobo sometimes adds to the chaos. After a clean reinstall of MSFS2024 with an empty Community folder, I reinstalled the B38M. I tried starting with the basic pre-SP1 version as per the developers’ guidance, and then updated to the hotfix 2 version—but nothing worked. The infamous iFly plugin kept crashing and freezing MSFS2024. Through the iFly Manager settings, I tried removing the plugin from the exe.xml and adding it back by pressing the "Add to EXE.XML" button again, but that didn’t help either. The only way I could get this troublesome B38M to work was by removing the iFly plugin from the exe.xml and launching it manually. That did the trick—the aircraft now works as expected. Regarding the heavy RAM and VRAM usage, I noticed that my preferred Ryanair and Buzz liveries are in 8K resolution, and I couldn’t find any 4K alternatives, unlike with other aircraft like the Fenix A320. So I installed a German TUI livery that isn’t 8K (about 32MB download vs. over 100MB for Ryanair), and RAM and VRAM usage dropped to more reasonable levels. While there’s no rocket science involved in getting this B38M to work (though I did lose about four hours of my time), it seems the developers are currently in a state of panic, stuck in a tunnel vision where they keep advising users to reinstall the product over and over. That approach isn’t necessarily wrong, but I found another way to make the B38M work again—though I haven’t started it up yet this morning, so fingers crossed. P.S. Not to mention the infinite "rotating wheel" bug when try to start flying.