FSDT Installer Not Loading

[Lude2Envy]

Within the last few days the FSDT Installer stopped loading on my PC. It begins to load and then apparently closes itself out. The only way I can get it to work is to download the installer from the website and install it. The next time I try to run it from the desktop icon after that it doesn't work anymore. Any ideas? Thanks.

[yvesamuel]

And I have about the same problem, with impossible to install anything

[dc1ps2]

I also encountered the same problem. When I installed FSDT Installer version 1.1.5, it ended at this screen after installation and did not open the Addon Manager. However, after re-running the FSDT_Universal_Installer.exe installation, clicking the "Finish" button successfully opened the Addon Manager the first time. After closing it, I failed to start the Addon Manager again when I ran it through FSDT Installer alone. I hope the official will take notice of this problem and fix it.

[ChrzOC]

same issue here, seems like a problem with the CDN or a network issue.

[virtuali]

Try using a VPN, files are not corrupted on our server, it's a local CDN issue.

[Lude2Envy]

Try using a VPN, files are not corrupted on our server, it's a local CDN issue.

Why would this problem just start out of nowhere. I never needed to use a VPN before?

[SKEWR]

Same here. Going crazy trying to figure it out..

[virtuali]

Why would this problem just start out of nowhere. I never needed to use a VPN before?

That's completely outside our control, we just update files on our server and communicate to cloudflare the list of changed files that must be updated, then cloudflare will automatically replicate all its 270+ nodes around the world, and you'll download from the one closest to you, selected automatically by cloudflare.

If your local node hasn't completed replication or got a corrupted file, or maybe you are the first in your area downloading that file, so you are triggering a replication of your local node, it's possible you might get a corrupted file notice, because the file hasn't got there yet, so it might just work later.

That's why we suggest using a VPN, so you might connect to another node that completed replication, without having to wait for yours.

[SKEWR]

If you are having this issue, try the offline installer. It actually worked.

[ChrzOC]

Hasn't worked for three weeks. Still same .NET CLR exception causing instantaneous CTD.
Tried multiple VPN's in varying geographic locations.

I just haven't bothered updating.

I guess at some point I'll have to use the offline installer.


Update (8/27): Still not working, just used the offline Installer, which worked fine to update. However, even after updating the .NET CLR CTD still persists.
It's Annoying because I can't access the GUI to add/adjust/remove exclusions, et al. So, I've been having to edit them manually.

I've tried like 5-7 different VPN's across multiple geographic locations and multiple varying protocols (L2TP/IPSec, SSL-VPN,SSTP, even non encrypted Socks 4/5 proxies) to no avail.
if someone finds a successful public vpn that directs them to a usable cdn node, please post it & I'll give it a shot.

[virtuali]

However, even after updating the .NET CLR CTD still persists.

please provide with the Details about this error.

[lomewolfnz]

Having the same issue.  loads the first installer screen, then that disappears, and nothing. 

Has anyone found a fix?

[Lude2Envy]

Having the same issue.  loads the first installer screen, then that disappears, and nothing. 

Has anyone found a fix?

Nope. Tried uninstalling and reinstalling, but that didn't work. Only option is to download the installer from the website and run it every time you want to install a new scenery or update an old one. Umberto says it an issue with my ISP and to use a VPN, but that's not the problem either.

[ChrzOC]

However, even after updating the .NET CLR CTD still persists.

please provide with the Details about this error.

It's throwing an exception with the .NET CLR.
specifically, in the clr.dll dynamic link library. The same exception multiple others have posted about.

Totally unable to launch the update GUI, instant CTD.
This has been ongoing for about a month now, persistent through multiple updates.

watching the TCP pipes as I launch the updater, it occurs as right around the time the Couatl_Updater.exe tries to open a socket on the http port (80).
(Ref IMG attached). Two seconds after that, the process crashes, throwing the below .NET CLR exception.

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.2.0, time stamp: 0x68a7353a
Faulting module name: clr.dll, version: 4.8.4300.0, time stamp: 0x5f7e61bb
Exception code: 0xc0000005
Fault offset: 0x00073b5a
Faulting process id: 0x49ec
Faulting application start time: 0x01dc1cb3af8c2a38
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: ac81985f-0d81-4a98-83d2-6d86dfe69925
Faulting package full name:
Faulting package-relative application ID:

There is no further information in the WER dumps. I grabbed ownership and piped them out to see if there was any debug offsets, but it's just the
same standard Application error crash event data.

I tried using multiple VPN protocol variants from assorted geolocations, figuring it was the local cloudfare node causing the exception to be thrown, and as also it appears this alleviated the CTD for some people, Not for me though, still doesn't work. Crashes every time. Even if I route the requests from the other side of the planet.

It started occurring about a month ago randomly, haven't been able to open the Install Manager UI since.
Only way to update is via the offline installer, however it makes managing exclusions and liveries a huge PITA.

Looks like the updater executable is built with the classic .NET 4.8.x Framework, per the Fault data. I have the 8.0.15 .NET Core installed though, which obviously has portability/backward compatability with classic framework apps. (see attached)
never had an issue before.

[ChrzOC]

Also, just to make sure/test that I have no issues opening a socket with that IPv6 address,
I manually Ping'd it and Trace Routed it. No issues, 0% loss.