yes twice allready, restart my pc several times, my internet is working perfect…
When i click ok to the error message i am in the fsdt installer app. When i press update for gsx the update starts but stops suddonly at around 50%. i can repeat this several times, no difference…
Since the newest update I can’t start GSX in MSFS2020.
There always remains a circling symbol that says “LOADING”…
This update is silent, meaning the version number has not been changed. To get the update if you are already on 3.7.6, press “Check” in the FSDT installer.
If you are still experiencing issues after this, please try the Offline Installer linked below. Using Box.com is recommend as that is more frequently updated.
Version 3.7.6 SILENT HOTFIX
February 4th, 2026
-
GSX Pro Fix: GSX now detects the release of parking brakes when using the new Mototok and Towbarless pushback variants.
-
GSX Pro Fix: Issue with GSX menu not loading has been fixed.
From the discord
I wouldn’t call this a “silent” hotfix, on the FSDT forum (which is the only place were official support is offered), it has been discussed here:
https://www.fsdreamteam.com/forum/index.php/topic,34315.msg213843.html#msg213843
GSX Pro Fix: Issue with GSX menu not loading has been fixed
This, instead, is completely made up.
There has never been any loading issue with GSX, it’s the usual, normal, longer startup time when a new update is applied caused by the model cache rebuild process, and somebody must have assumed was “silently fixed” just because he ran the update again and the next time the sim started he maybe waited long enough to let the first startup to complete.
1 Like
I’m now (for the first time ever) getting a windows security warning blocking FSDT Installer.
In windows defender I have an exclusion already set up for the AddOn manager folder
The installer had been working fine up until now.
EDIT: Note FSDT Live Update seems to be working, but FSDT Installer is what is spitting out this windows defender issue.
EDIT (update): FSDT Installer now working after FSDT Live Update (separate program) ran and updated it all.
In my opinion, when a hotfix or any other update is released, the version number should be changed so we can easily notice that a new update is available.
3 Likes
When the update is so small and appeared so quickly after the issue was reported, it’s not worth posting an official update, which will prompt thousands of users to go back again to update, which will trigger a cascade of updates across all cloudflare nodes, possibly making the replication that was already undergoing from the previous update slower.
I understand your reasoning, but from the user’s point of view, infrastructure-related limitations shouldn’t impact update transparency. As customers, we rely on versioning to know when something has changed.
1 Like
If you find an issue, wouldn’t go to support to ask about it or read if it has been discussed ?
That’s why I pointed to the thread on our forum where I said to update again, precisely because we had an hotfix, it’s not as if it was a secret.
The thing is, unless I actually run MSFS and GSX, I won’t know if something is broken, so I won’t be checking support or forum threads. Even if I launch MSFs and GSX, I might not notice the issue - it could be there, but I simply won’t see it. I usually just check version numbers from time to time, and if a new version doesn’t appear, I don’t mess with updates. That’s why it’s important for the version number to change, even for small fixes.
1 Like
And I already explained why we don’t change the version for an issue that has been fixed so quickly after the update came out.
In fact, an user even suggested a more extreme method: to prevent issues caused by network replication delays, he said we should push updates completely silently, without even telling immediately, and instead wait a few days to advertise the fix, to be sure it has spread across the whole CDN.
He even suggested that “everybody does it”, but I don’t think it’s a very good idea having a fix ready and don’t tell, just because some users might be in a node that has been slower to replicate and being frustrated the fix that is supposed to be out, is not out for them, which of course would penalize the vast majority of users not affected by network delays, so they can get the fix as soon as it is available so, so nothing is done in secret.
Of course, we also tried increasing the version each time a tiny update came out, and some users complained of being annoyed by their frequency and it was discomforting having to start the sim and seeing GSX reported to be outdated every day.
There’s just no way to please everybody.
2 Likes
Exactly how often does GSX release such a patch on such a short notice?
So here, as earlier with the BATC Simbrief dependency (we had this same discussion there), you seem to be pressing on a seldomly occurring issue from a very theoretical standpoint.
I understand that a software developer in such cases does his weight and balance calculation to come to the conclusion that he is well within the safety envelope.
Can’t say it any clearer than this 
1 Like
How often a quick hotfix is released doesn’t really matter - if an issue is going to occur, it will occur. For example, saying it happens “very rarely” doesn’t change the fact that if it’s going to happen, it will happen and when it does, a hotfix might be necessary.
My point of view is simple - I’ve always been concerned with the benefit of the community, not the developers. We have the right to expect certain things, and whether something can or cannot be done is the developer’s responsibility. This topic has nothing to do with BATC or SimBrief so I’ll leave it at that.
Fair enough.
1 Like
What’s the point of the new percentage slider on the installer?
It sometimes moves in increments in the scale of 0.01% at like 1 second intervals and sometimes like increments of 5% at 1 second intervals..
It makes one absolutely non the wiser in knowing at what stage you are in the install/update process.
Your concern with the community is 100% true, and appreciated!
Of course it’s telling you exactly in what stage you are in the install process, that’s exactly what it does and it’s clearly a big improvement over the previous version, where there was no real “overall” installation task. Now it’s real, and it takes into account the download, the extraction, the installation, and the update check so yes, you know exactly where you are in the process, but it goes through predefined steps we defined to be the “milestones” of the installation/update.
Maybe you wanted to say that it doesn’t tell you how much TIME you’ll have to wait, but that’s because it’s not really possible to make an estimation that would be useful, because the variance is so high, that it would cause an eventual “eta” to fluctuate wildly between extremes, because some processes cannot estimated, especially the update process, due to its length depending on the number of files you have locally that requires an update (which will in turn trigger a download, which comes with its own variance), so a real-time estimate would keep changing, and it won’t be that useful, is like when you copy lots of files with Windows Explorer: the ETA is almost useless when you have a combination of big and small files, with the big ones usually going very fast, and the small ones very slow, making the eta an ever changing guesswork, and GSX is also made of many big files (models and texture), but also thousands of small files, that’s exactly the kind of mix that would make ETA prediction not that useful.
I agree @TenPatrol . Having assurances you have the latest update with the most recent fixes, big or small, is important to me as a user. Especially when there is a plethora of issues the user has to “forum” their way through on a consistent basis for things to “work”.
Your assurance to always have the latest update is the Check button in the installer, that’s the only sure way to know you have the latest version.
Because, as I tried to explain so many times that a version number is not that useful, is the version number you see there, is JUST the version number of a single file: the manifest.json in the GSX package, that’s it.
It won’t tell you if each and every file of the almost 100K files that makes a full GSX installation is the “last” version, in order to do that, you would need to check each and every file with a checksum against the server.
Which is exactly what the Check button does.