MSFS 2024 / PMDG 777-300ER: Hub alternates extraction path, causes WASM crash, and 77W IDENT ends up blank

Navigation Data General MSFS Data
1

Hello,

I am looking for help with Navigraph Hub + PMDG 777-300ER in MSFS 2024 (MS Store version).

Environment:
Windows 11 Pro 24H2
MSFS 2024 (MS Store)
(With MSFS 2020 also still installed on the same PC)
Navigraph Hub v1.2.24
PMDG 777-300ER v2.04.130 (confirmed in OC3)
AIRAC update 2603
Hub is not running as Administrator
AVG was temporarily disabled during testing

The problem:
I am unable to get current navdata into the PMDG 777-300ER in MSFS 2024.
I have now seen three different behaviors from Hub during troubleshooting:
Earlier, Hub was incorrectly extracting MSFS 2024 packages to:
F:\MFS\Community (my MSFS2020 Community folder)
even though my active MSFS 2024 packages path is:
C:\Users\brian\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages
(as confirmed from the last line of UserCfg.opt - see below).

But following a complete reinstall of the Navigraph Hub, Hub no longer extracts to F:\MFS\Community, but now extracts:-
sometimes to
C:\Users\brian\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-77w\work
and sometimes to C:\Users\brian\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024_now_valid\pmdg-aircraft-77w\work

After that extraction, loading the 77W in MSFS 2024 gives me a WASM crash.
If I clear the relevant work directory to stop the crash, the aircraft loads, but CDU IDENT then shows no NAV DATA at all.

Baseline check
I confirmed that the PMDG base install is healthy:
After reinstalling the 77W via PMDG OC3, the default bundled AIRAC returned correctly in the FMC (AIRAC 2404 APR18MAY16/24).
So PMDG’s bundled default data can be restored correctly - the problem begins when I try to use Navigraph Hub for the current cycle

UserCfg.opt check
My MSFS 2024 InstalledPackagesPath is correct:
InstalledPackagesPath “C:\Users\brian\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages”

Current questions:

For PMDG 777-300ER in MSFS 2024, is Hub supposed to extract to the WASM work folder rather than to the aircraft package Config\NavData location?

Why is Hub alternating between …\LocalState\WASM\MSFS2024\pmdg-aircraft-77w\work and …\LocalState\WASM\MSFS2024_now_valid\pmdg-aircraft-77w\work ?

Is …‘MSFS2024_now_valid’ expected/normal?

And…

What is the correct recovery procedure when this update causes a WASM crash?

Which folder should be cleared for a safe rebuild, if any?

Is my still-installed MSFS 2020 likely to be confusing Hub’s path selection for the MSFS 2024 PMDG 77W update?

Relevant log excerpts:

Earlier incorrect path:
[ExtractionManager] File: …pmdg-aircraft-77w.7z
[ExtractionManager] Extract to: F:\MFS\Community\

After Hub reinstall:
[2026-03-25 08:41:17.703] [info] [ExtractionManager] File: …fe8d28aa-1fcd-428f-b723-08f790739b9c_pmdg-7xx-workfolder-2603.7z
[2026-03-25 08:41:17.703] [info] [ExtractionManager] Extract to: C:\Users\brian\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-77w\work

and on the next reinstall attempt:
[2026-03-25 09:08:12.830] [info] [ExtractionManager] Extract to: C:\Users\brian\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024_now_valid\pmdg-aircraft-77w\work

Current status
77W loads with bundled default AIRAC after OC3 reinstall
Hub update then causes either a WASM crash or, after clearing work, blank IDENT / no navdata.

I can provide the full main.log and supporting screenshots if needed.

With thanks in advance,

Brian

2

Hi Brian,
and what happened when you update the AIRAC via the EFB in the T7?

For MSFS2024, this is the correct full path to the navigation data files:
C:\Users\<your user>\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-77w\work\NavigationData

Cheers,
Richard

3

Hi Richard, and many thanks for your swift reply.

Unfortunately, since I’m now getting a WASM crash every time I enter the 777 flight deck, I can’t get to the EFB to try. But IIRC (which is far from guaranteed!) when I tried the EFB update once it failed, which is why I hit the PMDG forums and found from Mathijs’s post in January that the hub was currently the way to do updates, pending a PMDG resolution of the EFB update problem introduced in SU4.

4

Hi Richard,

In an attempt to try and answer your question about updating the AIRAC via the EFB, I removed the 77w update using the Hub, cleared the whole of the cache (i.e. all the contents of …WASM\MSFS2024\pmdg-aircraft-77f) and restarted the sim. The regenerated data (without AIRAC 2603, of course) had the desired effect of removing the WASM crash, but in the absence of navdata the IDENT page on the CDU shows no version (see pic).

No navdata
No navdata355×307 23.9 KB

However (albeit contrary to PMDG’s current recommendation), I was then able to go to the EFB and try to update from there — but as expected the loading process stalled about two thirds of the way through.

Navdata upload stalled
Navdata upload stalled1055×532 26.2 KB

(It also unhelpfully reset all my preferences, and cleared my SimBrief Alias and Hoppie ID).

So the WASM crash was removed along with AIRAC 2603, but I am currently unable to plan routes in my 777.

Anyway — hopefully, that answers your question.

[Later edit] - in desperation, I tried substituting the 777-300ER msfs_navigation_data_interface.wasm with the downloaded version from https://forum.navigraph.com/uploads/short-url/25JJ8QRWSTx6EuidMB5xjXrZKEg.wasm and then trying the EFB update again, but complete failure — the progress bar didn’t even begin to move. Ah well, I tried.

And I can confirm that the path you gave (C:\Users\brian\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-77w\work\NavigationData) does contain the navdata files for AIRAC 2603: it’s just that the aircraft is unaware of that, seemingly.

5

Hi, the same issue also happens to me on both 738 and 77w.

Before navigraph or pmdg find out the real solution, is there any workaround, for example, falling back to 2602?

6

Hi Brian,
Do you use Addon-Linker or a similar tool? Also, could you please upload your UserCfg.opt file so I can run some checks?

Thank you very much,
Richard

7

Hi Richard,

Sure - Usercfg.opt is attached.

I do use Addons Linker, but only for airport files (I keep only the departure, destination, and alternate airports for the current flight in my Community folder). Nothing else (including navigraph files) is via symbolic links (or whatever Microsoft has renamed them to — as an old-time Unix man I prefer the original name).

UserCfg.opt (4.0 KB)

8

Hi Brian,

Please install the latest versions of PMDG 777, just released.

Cheers

Ian

9

Hi Ian,

And thank you. I note from Randazzo’s comments that “A few critical fixes are implemented to reduce/eliminate some problems with navdata updating”, so I am hopeful… :folded_hands:

Cheers,

Brian