Navigraph Hub: package installation/detection issue

[AstonMartinDBS]

I’m using MSFS 2024. About two weeks ago I installed manually SimBrief Dispatch (I downloaded the package and extracted the content of the archive it to the community folder). SimBrief Dispatch worked without any issues within the MSFS 2024.

A few days later I purchased an unlimited subscription and I installed the Navigraph Hub from Navigraph to get further packages for MSFS 2024. When I first launched the Hub, MSFS 2024 was detected, as well as the manual installation of SimBrief Dispatch. So far, so good.

When I install the Navigraph EFB Charts App via Hub for example, the files will be copied into the MSFS 2024 community folder. But about a minute after the installation the button “REMOVE” changes to “INSTALL”, but the copied files are still remaining in the community folder. The only Package which stays detected by the hub is the manual installation of SimBrief Dispatch. And SimBrief Dispatch is the only Package, which is available in MSFS 2024.

Here you can find a demonstration of the issue: https://youtu.be/GDQWGJ6VqFc

Relaunching the Hub doesn’t solve this issue. Even a deinstallation and reinstallation of the Hub didn’t fix this behaviour.

[AstonMartinDBS]

After reinstalling the Navigraph Hub I was logged in automatically, so apparently not all data is deleted when I uninstall the Hub.
How can I cleanup my system from any old data for the Hub?

BTW: The file “content.xml” contains several duplicated entries for the navigraph packages:

[AstonMartinDBS]

@AstonMartinDBS

How can I cleanup my system from any old data for the Hub?

Well, I deinstalled the Hub once more, deleted the folder %appdata%\navigraph-hub and reinstalled it again. At the first start of the Hub I had to enter my login, but the issue still persists.

[AstonMartinDBS]

Issue detected:
The default community folder is encrypted (Win 11 Pro) and I’ve been unable to open files within those (sub)folders, i. e. the manifest.json. Navigraph Hub and the MSFS 2024 itself obviously had the same problem and couldn’t access those encrypted files.

Workaround:
I changed the default location of the community folder from %USERPROFILE%\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages to another drive/location.