If only I would have known about that log..
It was very clear what went wrong. It was not about the “work” folder that was the culprit.
I use a lot of “JUNCTIONS” and “SYMBOLIC LINKS” and the pmdg folder in the community had a corrupt link for “pmdg-aircraft-77w/config/NavData”.
Then again, I wonder why the HUB app makes changes to the community folder instead of just the “work” folder inside LocalState. The community folder should be left alone to my mind and have the default Airac provided by PMDG in it?
Isn’t that why there’s a file inside the “work” folder called “navigraph_config.json” and inside the {“is_bundled”:false} statement?
Never touches the community folder again. The work folder takes over from that point
Symlinks and junction links are not recommended. Not from Asobo/MS, PMDG, nor from us. Those could result in such side effects. I’m not sure which program you are using to find which files are modified but I do know we don’t touch these default files, there is no reason to.
Hub DOES replace the community folder pmdg/config/navdata. It replaces the default very old airac.
The log file pointed me to that folder unable to copy the Airac to the above folder. At that point I knew that the junction was corrupt. In fact the whole reason to have a junction on that folder is unnecessary. The active Airac is in the work folder. It was a left over from a distant past not fully grasping the way PMDG navdata works. Auto updates are nice but I want to know what goes on.
I’m old school and used to run a business with 200Megabyte server storage.. I still hate wasting hd space or inefficiency. don’t get me started on what I do to keep everything as clean/tidy as possible..
All pmdg planes’ airacs I own are the same files.. I don’t like that many copies of the same files.. hence junctions. Yes PMDGs fault not Navigraph…
The program I’m using to show the “changed” community folder is PMDG’s own OC3 application and selecting the option: validate install
The junction/symlink usage works perfectly, recommended or not. Just my error in moving a folder the junction pointed to. But with this I found out that HUB does replace the default PMDGs Airacs.
Hi Roel,
No, the Hub does not change anything in the community folder, as written before. The default data are updated via an addon update from PMDG, not via the Hub.
To prove it DOES, look at this log file attached of Hub!
(this recreated to the before I found out about the corrupt junction)
It throws an error not being able to save files to.. the community folder!
TLDR:
ERROR: Cannot open output file : The system cannot find the path specified. : D:\FS2020_Community\pmdg-aircraft-77w\Config\NavData\cycle.json
that seems to me a very good indication that it wants to save there but couldn’t…
Cheers
Roel
BTW: Removing the (faulty) Navdata folder inside the PMDG community folder and starting and updating via HUB.. it saves the current Airac in the community folder (AND the work folder btw)
Update:
I’ve removed my installation and reinstalled. The 777-300ER of course came with an old Airac in the community folder.
After using HUB it again was updated to the latest. Just to be perfectly clear: this is on the FS2020 version and only for the 777-300ER that I know of (I have no other 777)
There is some kind of bug, not that serious at all but it’s there…
Hi Roel,
Sorry, but you are wrong - as I wrote before, we don´t have the possibility in the Hub to distribute any default data. That’s part of the addon.
I have tested your use case:
I have deleted the community-PMDG navdata folder (on my system D:\Simulation\MSFS2020\Community\pmdg-aircraft-77er\Config\NavData) - you see in the video, the folder is empty
Open the Hub → folder is still empty
remove/re-install the MSFS2020 T7 data → folder is still empty
Here is the video with these three steps:
Again, we don´t touch this folder. According our experience (without going into the detail) the most common reason for such entries in your log are permission issues.
Please please please.. now you’ve showed it working on fs2024!
I’ve never claimed it didn’t work on fs2024..
It’s FS2020 with the PMDG 777-300er and nothing else…
Hi I believe exactly what you are showing but the trouble is, you’re not showing solutions to my question. You took the time (really appreciating it) to create videos and elaborating on it.
You keep on saying HUB doesn’t change anything in community.
But you’re not understanding or reading the issue I had.
Again I think it’s a niche situation I’m trying to make you aware of, not trying to be pedantic or non cooperative or anything like that.
Just stating the fact that I clearly see HUB replacing files in the community folder, but ONLY FOR FS2020 and PMDG 777-300er. All your suggestions and explanations point to a different situation/plane/config.
I sincerely hoped you took the time to check my original question and statements.
Why you’re showing me things that I never said were wrong is beyond me.
I do think there is some kind of left over code or whatnot in HUB that specifically does something wrong in the combi FS2020 and 777-300er.. nothing more.. nothing less.
Showing me that it works in all other combi’s doesn’t help.
If you don’t want to check my particular situation.. it’s fine by me.. would however appreciate it VERY much, for you to check the real issue.
If I’m wrong with that combo, I will leave you alone with an apology. If I’m right, I can sleep again
Ehm.. did you delete your comment? I’m following up on your request to show you via a video.
And again I want to state.. that you in fact have shown me the FS2020 PMDG 777-200 and the FS2024 PMDG 777-300er, but not the culprit FS2020 PMDG 777-300er.
Anyhow, here’s my video showing you exactly what happens on FS2020 777-300er, nothing more, nothing less.. 2020_777-300er.mkv (3.5 MB)
relevant log:
[2020_777-300er.mkv|attachment](upload://lE2gzMRH2XfFuKl2vYaYoDLD1Tp.mkv) (3.5 MB)
\[2026-05-21 12:50:38.839\] \[info\] \[ExtractionManager\] Extraction successful (code 0, no errors)
\[2026-05-21 12:50:38.839\] \[info\] \[ExtractionManager\] Removing temp file: C:\\Users\\kostex\\AppData\\Local\\Programs\\navigraph-hub\\downloads\\330253fc-d7f3-4420-a5d6-faaef8d2ae78_pmdg-aircraft-77w.7z
\[2026-05-21 12:50:38.845\] \[info\] \[ExtractionManager\] Temp file removed successfully
\[2026-05-21 12:54:05.708\] \[info\] \[ExtractionManager\] Starting extraction b85f83e4-507d-49d4-b4d6-b1ad871b8ee4
\[2026-05-21 12:54:05.709\] \[info\] \[ExtractionManager\] File: C:\\Users\\kostex\\AppData\\Local\\Programs\\navigraph-hub\\downloads\\64c84ebd-ffbd-4056-8ab2-3cca0a58999a_pmdg-aircraft-77w.7z
\[2026-05-21 12:54:05.709\] \[info\] \[ExtractionManager\] Extract to: D:\\FS2020_Community
\[2026-05-21 12:54:05.709\] \[info\] \[ExtractionManager\] 7zip path: C:\\Users\\kostex\\AppData\\Local\\Programs\\navigraph-hub\\resources\\assets\\bin\\7za.exe
\[2026-05-21 12:54:05.710\] \[info\] \[ExtractionManager\] Checking file accessibility (may be locked by antivirus scanning)
\[2026-05-21 12:54:05.718\] \[info\] \[ExtractionManager\] File access check succeeded on attempt 1
\[2026-05-21 12:54:05.719\] \[info\] \[ExtractionManager\] Using Process Governor to set process priority to BelowNormal
\[2026-05-21 12:54:05.892\] \[info\] \[ExtractionManager\] Process spawned, PID: 1520
\[2026-05-21 12:54:06.602\] \[info\] \[ExtractionManager\] 7za.exe process closed with code 0
\[2026-05-21 12:54:06.603\] \[info\] \[ExtractionManager\] Exit code analysis for task b85f83e4-507d-49d4-b4d6-b1ad871b8ee4:
I have always looked into the first 77f (PDMG folder). PMDG renamed this folder during an update of the 77f. Ok, so far so good …
Now I dug deeper into it:
The MSFS2020 PMDG 777F and 300ER are the only two addons with the following workflow (and that’s per PMDG design, not ours)
Copy the files in the MSFS2020\Community\pmdg-aircraft-77w\Config\NavData folder
When the addon is loaded in the MSFS2020 the addon copies the files in the work folder
Therefore, both are equal; you don´t have any default cycle, so that’s why we must copy the files into the community folder. I have forgotten it because, as you wrote, it should normally be untouched, and I don´t know any addon that copies the files to the community folder too (I guess MilViz, but not sure). So, I´m sorry I was wrong.
…which is now seemingly consistent with your newer statement(s) written while I was composing, including but not limited to:
s/copy/place the files there is what the Hub is doing (or apparently in kostex’s case, attempting to do, unsuccessfully)?
That being said, after deleting the Config > NavData folder then launching the sim and loading the aircraft, said folder remains non-existent (it is not re-created my the addon with default navdata, for example).
Regards,
Tim
P.S. actual/actionable suggestions coming in my next post
Darn, I had an idea on how to re-create the folder without having to re-install the whole aircraft but while testing it, I realized it does not work like I would like it to; please stand by
Hi thanks for joining in, but it has been acknowledged that the HUB does install files in the community folder but only for some pmdg variations and only for FS2020.
There is however no real PROBLEM, just an observation.
