However, the link/unlink don't seem to work... maybe? The installer tells "active " but NOW, GSX do not even show up in the toolbar
That's because you are confusing "Active", which means the status of the LICENSE, with the Linked/Unlinked status of the product, which is what makes the simulator "see" the product.
The Activation status of the license is completely unrelated to the Linked/Unlinked status, and will persist as long you don't change major hardware components or reinstall Windows from scratch.
The folders "fsdreamteam-gsx-pro" and "fsdreamteam-gsx-world-of-jetways" are there in the community folder but how should things actually look like if there is no unlink? There is also a "fsdreamteam-gsx-pro" folder in the Package folder but no "fsdreamteam-gsx-world-of-jetways"
Please clarify this, especially the part which says "There is also a "fsdreamteam-gsx-pro" folder in the Package folder but no "fsdreamteam-gsx-world-of-jetways"
What do you mean with "Package" folder ? Maybe the "Packages" folder, the one that by default *contains* the Community folder, which is located here:
MS Store:
%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\
Packages\Community
Steam:
%APPDATA%\Microsoft FlightSimulator\
Packages\Community
If that was you really meant, if I read your post correctly, you have something like this ?
%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\fsdreamteam-gsx-pro
%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\fsdreamteam-gsx-world-of-jetways
%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\fsdreamteam-gsx-pro
(of course, changing for the Steam version folders, if you use Steam)
Because that's what you wrote, literally, and that's not normal, and it's impossible you'd end up with that situation when using the FSDT Installer, which surely doesn't install anything
OUTSIDE the Community folder, that really like the result of some manual copy, or possibly having used an external tool to manage packages.
Now the next question, are these real folders or shortcuts because, in normal situations, that is when using only the FSDT installer and not moving anything manually or not using other apps that might cause a mess, you are supposed to have this:
When GSX Pro reports "Installed" in the FSDT Installed ( =Linked )%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\fsdreamteam-gsx-pro (
shortcut)
C:\Program Files (x86)\Addon Manager\MSFS\fsdreamteam-gsx-pro (
real folder)
%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\fsdreamteam-gsx-world-of-jetways (
shortcut)
C:\Program Files (x86)\Addon Manager\MSFS\\fsdreamteam-gsx-world-of-jetways (
real folder)
When GSX Pro reports "Unlink" in the FSDT Installed ( =UnLinked )C:\Program Files (x86)\Addon Manager\MSFS\fsdreamteam-gsx-pro (
real folder)
C:\Program Files (x86)\Addon Manager\MSFS\\fsdreamteam-gsx-world-of-jetways (
real folder)
When the program is Unlinked, you shouldn't have any gsx folder or shortcut in the Community folder, only the Addon Manager folders will still be there, ready to be relinked again, without having to redownload anything from scratch.
Under no circumstances you are supposed to have:
- The gsx folders as "real" folders ( not shortcuts ) in the Community folders
- The gsx folders anywhere outside the Community folder, either as real folders or as shortcuts.
I'm asking this because, a few days ago, I spent so much time troubleshooting a problem that seemed impossible, only to find out the user decided it was a good idea to manually copy the whole fsdreamteam-gsx-pro from the Addon Manager to the Community folder, so HE created a big mess because:
1) the real folder in the Community what was the only thing the simulator used but, since the FSDT Update works only on the package in the Addon Manager (because you are supposed to have a shortcut to there, not a real folder! ), he had the sim running an outdated version, because the one that got updated wasn't used by the sim, because of the folder in Community not being a shortcut, just an outdated copy.
2) the program *code* that runs in the Addon Manager WAS the latest version, but it had to run with outdated packages, and that was the real cause of the mess because, while having "just" an outdated version might not be a problem, the real problem is when you have half product updated ( the code in the Addon Manager folder ) and half of it outdated, the copy he made manually as a real folder instead of a shortcut.
So, please be very precise in clarifying exactly what's your situation is, because from your description ( assuming I understood it correctly ), you have some messed up install, which doesn't seem possible when using "just" the FSDT Installer.