FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: Empire on August 05, 2025, 12:24:07 am
-
Hello,
I'm experiencing a persistent issue with the FSDT Installer. It briefly opens, starts to load, and then immediately closes without launching fully.
As a temporary workaround, I had been redownloading the installer each time I needed to update. However, today I decided to do a complete clean install of GSX and all related components.
After the clean install, the issue persists, the FSDT Installer still won’t open, even after adding it to the list of allowed service executables.
I also tried the offline installer, let it complete its process, and then attempted to run Couatl_Updater.exe. That too opens and immediately closes, just like the main installer.
At this point, I'm unsure what's causing the problem. Any guidance or troubleshooting steps would be greatly appreciated.
Thank you.
Fault bucket 2219618992817541938, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: Couatl_Updater2.exe
P2: 2.3.1.5
P3: 6890859a
P4: mscorlib
P5: 4.8.9310.0
P6: 67db4ec1
P7: 51c
P8: 2f
P9: System.ArgumentOutOfRange
P10:
Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.08f64a7b-c5ba-4061-a735-cb4c8206a227.tmp.WERInternalMetadata.xml
These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Couatl_Updater2._8cad6197da204271d94730e24ededa95d814d7_61f9fd99_858d66ac-9fad-45db-ad79-5ea6b640940a
Analysis symbol:
Rechecking for solution: 0
Report Id: 05513de2-2709-4655-a676-9d08f92cbdd7
Report Status: 268435456
Hashed bucket: 4e200d8f944204d69ecdabb6c3999332
Faulting application name: Couatl_Updater2.exe, version: 2.3.1.5, time stamp: 0x6890859a
Faulting module name: KERNELBASE.dll, version: 10.0.26100.4768, time stamp: 0xb2d039ba
Exception code: 0xe0434352
Fault offset: 0x00160714
Faulting process id: 0x9190
Faulting application start time: 0x1DC058D2CE31944
Faulting application path: D:\Addon & Products\FsDreamTeam\Addon Manager\Couatl_Updater2.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 05513de2-2709-4655-a676-9d08f92cbdd7
Faulting package full name:
Faulting package-relative application ID:
-
Same issue here.
Already posted about it under General Discussions.
-
Same issue here.
Already posted about it under General Discussions.
Yeah, I see that topic myself. I spent 3 hours last night looking for a way to resolve it myself - seems to be there CDN end I say
-
Same issue here.
Already posted about it under General Discussions.
Yeah, I see that topic myself. I spent 3 hours last night looking for a way to resolve it myself - seems to be there CDN end I say
That was my first thought as well, considering it seems to be affecting many clients, and it started occurring totally randomly (not after an update or anything).
Are you in or near the Northeast US?
I'm wondering if it's just one subnet or node of the CDN.
Whatever the cause, it seems to be triggering a crash due to an exception thrown in one of the .NET CLR runtime libraries.
Has anyone tried updating to the most recent version/release of the .NET 8.0 core (8.0.19 is the latest)?
or the .net 9.0 core for that matter?
I'm still on 8.0.15 here (SS attached), but it has always worked without issue.
Application: Couatl_Updater2.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 6C333B5A (6C2C0000) with exit code 80131506.
Faulting application name: Couatl_Updater2.exe, version: 2.3.1.5, time stamp: 0x6890859a
Faulting module name: clr.dll, version: 4.8.4300.0, time stamp: 0x5f7e61bb
Exception code: 0xc0000005
Fault offset: 0x00073b5a
Faulting process id: 0x76c
Faulting application start time: 0x01dc066338278f30
Faulting application path: C:\Program Files (x86)\Addon Manager\Couatl_Updater2.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: f8975299-7a17-454f-bb95-81d8dcb0f496
Faulting package full name:
Faulting package-relative application ID:
-
SNip
I'm from England, and it seems this issue is affecting users on different internet providers as well. I’ve confirmed that it’s still running on the .NET Framework 4.8 — that’s the version being reported. I enabled it through Windows 11, since it's built into the OS, but it was initially disabled. Unfortunately, even after enabling it, the issue persists. 😔
I also tried repairing Windows Update and fixed other related runtime frameworks, but nothing seems to help. I haven’t tried switching my VPN yet to see if that makes a difference, although I don’t really expect it to work. Interestingly, a few of my mates who also have GSX are not having any problems, and they’re on different internet providers.
The only possible explanation I can think of right now is that the issue might be related to the CDN (Content Delivery Network) provider that handles the download requests. It seems like there's either a complete packet loss or severe interruption somewhere along the route between my connection and their CDN servers.
I don’t know which CDN they use, it could be something like BunnyCDN, Cloudflare, or another provider, but whatever it is, there appears to be a failure in delivering the content from their end to mine. Essentially, the data packets that make up the download request may not be reaching my system at all, or are being dropped entirely during transmission. This would explain why the download isn't completing or working as expected.
It’s possible that the problem is affecting users based on specific regions or ISPs, depending on the routing paths or CDN edge servers involved.
-
Update: I had a feeling this might be the issue, and it turns out I was right.
I tried downloading GSX on my secondary PC, which only has .NET Framework 8.0 installed. The download and installation went through without any problems. 😊
However, as soon as I tried to open the FSDT Installer, the issue came back. I tried launching it five times, and it refused to open each time. 😞
So, I decided to test something, I turned on my mobile hotspot (which uses a completely different network) and connected my PC to it. Once I did that, the FSDT Installer opened instantly and continued to work perfectly. I could open and close it multiple times without any failures.
So, it’s clear now, the issue lies with the CDN provider, either on my end (the route from my ISP) or possibly on FSDreamTeam’s side. That being said, FSDreamTeam really should consider setting up an alternative route or at least allowing users to manually select a different server or CDN endpoint. Having a backup route would help avoid these kinds of connectivity problems.
The main issue is that, without knowing which CDN they’re actually using, I can't provide my ISP with the necessary information to investigate or resolve the routing issue on their side.
-
We explained several times we use Cloudflare CDN. It you posted the error details (the "Details" button that usually pop-up on a .NET exception), I might be able to understand where the crash is happening, and provide some error handling for it.
-
I do not get any pop-up, other than via the event viewer
Log Name: Application
Source: .NET Runtime
Date: 07/08/2025 18:36:59
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Empire
Description:
Application: Couatl_Updater2.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentOutOfRangeException
at System.String.IndexOf(System.String, Int32, Int32, System.StringComparison)
at Microsoft.Win32.RegistryKey.ValidateKeyName(System.String)
at Microsoft.Win32.RegistryKey.OpenSubKey(System.String, Boolean)
at Microsoft.Win32.RegistryKey.OpenSubKey(System.String)
at System.Net.ComNetOS.GetWindowsInstallType()
at System.Net.ComNetOS..cctor()
Exception Info: System.TypeInitializationException
at System.Net.ServicePointManager..cctor()
Exception Info: System.TypeInitializationException
at System.Net.ServicePointManager.EnsureConfigurationLoaded()
at System.Net.HttpWebRequest..ctor(System.Uri, System.Net.ServicePoint)
at System.Net.HttpRequestCreator.Create(System.Uri)
at System.Net.WebRequest.Create(System.Uri, Boolean)
at System.Net.WebRequest.Create(System.String)
at Couatl_Updater2.Program.CheckUrl(System.String)
at Couatl_Updater2.Program.Main(System.String[])
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2025-08-07T17:36:59.0748488Z" />
<EventRecordID>18148</EventRecordID>
<Correlation />
<Execution ProcessID="38048" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Empire</Computer>
<Security />
</System>
<EventData>
<Data>Application: Couatl_Updater2.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentOutOfRangeException
at System.String.IndexOf(System.String, Int32, Int32, System.StringComparison)
at Microsoft.Win32.RegistryKey.ValidateKeyName(System.String)
at Microsoft.Win32.RegistryKey.OpenSubKey(System.String, Boolean)
at Microsoft.Win32.RegistryKey.OpenSubKey(System.String)
at System.Net.ComNetOS.GetWindowsInstallType()
at System.Net.ComNetOS..cctor()
Exception Info: System.TypeInitializationException
at System.Net.ServicePointManager..cctor()
Exception Info: System.TypeInitializationException
at System.Net.ServicePointManager.EnsureConfigurationLoaded()
at System.Net.HttpWebRequest..ctor(System.Uri, System.Net.ServicePoint)
at System.Net.HttpRequestCreator.Create(System.Uri)
at System.Net.WebRequest.Create(System.Uri, Boolean)
at System.Net.WebRequest.Create(System.String)
at Couatl_Updater2.Program.CheckUrl(System.String)
at Couatl_Updater2.Program.Main(System.String[])
</Data>
</EventData>
</Event>
-
Still having this ongoing problem. CDN error. And the worst part is that I can't do much on my end unless I use a VPN, maybe?
Even so, I don't need to do that, looking around there are many members/people having the same error. DAMNNnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn
Can't you add another download option? add another CDN backup?