FSUIPC7 is stuck at "Starting everything now"

[Djeez]

When starting FSUIPC and watching the log, I see that it gets stuck at the "starting everything now" message. When viewing the LVars from the FSUIPC UI, I get 0 LVars and 0 HVars loaded. I checked that the fsuipc-lvar-module folder is present in the community folder. I also tried with different aircraft and removed the fsuipc.ini file to have it recreated from scratch. Nothing helps. Can you help me debug this issue?

Attached is one of the typical log files.

Thanks!

Emile van Gerwen.

FSUIPC7.log

[John Dowson]

Your log file looks very strange... What state is MSFS2024 in when FSUIPC7 is started? Usually it is started while MSFS is still loading, but your log seems to indicate that an aircraft was already loaded and ready-to -fly.
What happens if you exit FSUIPC7 and then restart it?

Could you also please set WAPI Debug logging (Log->WAPI->Debug), and add offset logging (Log->Offsetts...) for offset 026D as U8.
Then show me another log with that logging, and also exit an restart FSUIPC7 and show me a log file from that.

John

[Djeez]

Hi,

I tried several starts and FSUIPC restarts, all with the same effect (I am not sure from what session the log file was that I sent you). 

Here are more log files, copied at different phases during MSFS2024 startup. There is also one with additional logging enabled, from starting MSFS2024 until ready to fly on the runway.

-Emile.

FSUIPC7_at_first_screen.log FSUIPC7_after_pressing_start.log FSUIPC7_after_loading.log FSUIPC7_after_fly_now.log FSUIPC7_with_additional_debug_info.log

[John Dowson]

Your logs show that FSUIPC7 is waiting for the WASM. Can you:
   1. Check to see if the WASM is running. You need to enable the developer tools in MSFS to do this.
       Once you have enabled the MSFS developer tools, go to Debug -> Display WASM Debug menu,
       and then select the FSUIPC WASM module from the menu, and go to the Module Section tab.
       What do you see? Can you take a screenshot. It should look like this:

   Maybe also a screenshot of the Wasm Section tab.

  2. Show me / attach your FSUIPC_WASM.log file. If you don't know where this is, take a look at the WASM section in the Advanced User guide.
      It may also be a good idea to set Debug level logging in the WASM (via the FSUIPC_WASM.ini file LogLevel entry), also explained in that section.

John

[Djeez]

In the WASM Debug dialog I can only select fcr-embedded in the Modules dropdown, so I can not select fsuipc-lvar-module to have a look at the Module Section.

I changed the FSUIPC_WASM.ini file to set the LogLevel to Debug but that did not change the log file: it is still from July!

-Emile.

FSUIPC7_with_WAPI_Debug.log FSUIPC_WASM.log

[John Dowson]

15 hours ago, Djeez said:

In the WASM Debug dialog I can only select fcr-embedded in the Modules dropdown, so I can not select fsuipc-lvar-module to have a look at the Module Section.

So this would indicate that the FSUIPC WASM module is not running, which will be your issue.

The FSUIPC_WASM.log file you attached is also very old - from 30th July.

Could you please show me your InstallFSUIPC7.log file, and can you confirm that you are using an MS Store version of MSFS2024, and not Steam.

John

 

[John Dowson]

Also, do you see the FSUIPC WASM installed under:
    C:\Users\aegva\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2020\fsuipc-lvar-module

?

[Djeez]

Yes, it is MSFS2024 Windows Store edition, and yes, the folder you describe is present. I will add a screenshot of its contents.

I gathered the information you asked for and some more files and screenshots that hopefully can give you some clue.

The mystery of the July version of the WASM log is somewhat cleared up because I saw another FSUIPC folder at another location where FSUIPC was previously installed. Those files were dated July 2025 so maybe at that time that version has worked correctly.

-Emile.

InstallFSUIPC7.log UninstallFSUIPC7.log EXE.xml

[John Dowson]

The FSUIPC WASM module is installed in your MSFS2024 Community folder, which is here:
    C:\Users\aegva\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community\
...or at least FSUIPC thinks it is...

This looks like a strange location to me, as it is under LocalCache. What else is installed under that folder? Is there an 'fcr-embedded' folder? If not, where is that installed? Where do you think your MSFS2024 community folder is?

Could you show me / attach your UserCfg.opt:
    C:\Users\aegva\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt
The Community folder is taken from the InstalledPackagesPath location specified in that file.

Your MSFS2020 community folder is C:\MSFS2020\Community\, which is a lot better...

John

 

[Djeez]

Yes, you are right about the Community location. That's what I tried when installing MSFS2024 but for some reason a lot of things went wrong and I had to try a few times until I got it installed. At that time the Community folder was at its default location and I left it there because at least I could fly. In my attempts to change the installation folder, I also changed the installation folder setting in the XBox app to C:\MSFS2024, which turned out to be a mistake. This is probably why the fcr-embedded location is so weird. See the screenshot.

Maybe it is a good idea to do a full reinstallation of MSFS2024 to get everything setup according to standards. Do you have suggestions how to completely remove MSFS2024? From my initial attempts where I did a few uninstalls and installs it looked like some settings carried over and I could never enter the intended C:\MSFS2024 as installation folder. 

Anyway, I include the UserCfg.opt files of both MSFS2020 and MSFS2024 and a screenshot of the Community folder contents. If I use the developer tool to open the VFS Community location it opens the right one.

 

UserCfg_MSFS2024.opt UserCfg_MSFS2020.opt

[John Dowson]

1 hour ago, Djeez said:

I also changed the installation folder setting in the XBox app to C:\MSFS2024, which turned out to be a mistake. This is probably why the fcr-embedded location is so weird. See the screenshot.

Ok - this then has probably changed the location of your Community folder, but hasn't updated the location in the UserCfg.opt screen. This is why the FSUIPC WASM isn't being detected, as well as those other apps installed in the same location. Sorry but I have no idea how the MS Store and Xbox apps install or configure MSFS2024. 

1 hour ago, Djeez said:

Maybe it is a good idea to do a full reinstallation of MSFS2024 to get everything setup according to standards.

Yes, I think that is probably a good idea. But before you do this, check in MSFS2024 where it thinks the Community folder is - you used to be able to do this from the Library settings, but there have been so many changes to MSFS2024 that I am not sure any more. If you can find this, try setting the InstalledPackagesPath (in your MSFS2024 UserCfg.opt file) to this location. You should uninstall FSUIPC7 before doing this.

1 hour ago, Djeez said:

Do you have suggestions how to completely remove MSFS2024? From my initial attempts where I did a few uninstalls and installs it looked like some settings carried over and I could never enter the intended C:\MSFS2024 as installation folder. 

No, sorry - especially for MS Store installs as I use a Steam installation. However, I am sure there are many posts on how to do this if you google... I would have thought that uninstalling either using MS Store or the Windows Apps panel, and then removing the MSFS2024 folders from your AppData/Roaming folder should do the trick, but best to confirm this with other MS Store users/google.
One think i would do before you uninstall MSFS2024 and re-install is to uninstall any Community add-ons first. For FSUIPC7, just run the uninstaller. However, as you are using the same installation for MSFS2020 and MSFS2024, this will also uninstall for MSFS2020, but you can then re-install for that version.

After you have re-installed, move your Community folder to the location you want to use BEFORE installing anything. In Steam, I would just do this by setting the InstalledPackagesPath in the UserCfg.opt file, but it may be different for MS Store versions, I don't know.
I also think that this was possible from within MSFS2024 (in Library settings), but not sure if this is still available. There have been so many updates to MSFS2024 that it is difficult to keep track.....!

John

 

[Djeez]

4 hours ago, John Dowson said:

Yes, I think that is probably a good idea. But before you do this, check in MSFS2024 where it thinks the Community folder is - you used to be able to do this from the Library settings, but there have been so many changes to MSFS2024 that I am not sure any more. If you can find this, try setting the InstalledPackagesPath (in your MSFS2024 UserCfg.opt file) to this location

I think is this fine, as the additional aircraft and scenery in the Community folder are loaded correctly. And this is in agreement with the InstalledPackagesPath and the location when I use the Developer Tools to open the Community folder. Anyway, I'll try reinstalling MSFS and hopefully get my Community folder at a more convenient location.

Thanks for all your help thus far, and maybe I'll have to come back to you...

 

Best regards,

-Emile.

[John Dowson]

14 hours ago, Djeez said:

I think is this fine, as the additional aircraft and scenery in the Community folder are loaded correctly. And this is in agreement with the InstalledPackagesPath and the location when I use the Developer Tools to open the Community folder.

Ok. And I see now that fcr_embedded is an internal/MSFS wasm that isn't installed in the Community folder. This was confusing me, sorry.
Then it seems that MSFS is just not starting the WASM for some reason. You should check the MSFS console for any messages relating to FSUIPC to see if it is detected (search for 'FSUIPC'):

John

: