Author Topic: FSDT Installer / Updater Crashes on start  (Read 366 times)

zain1291

  • Newbie
  • *
  • Posts: 9
FSDT Installer / Updater Crashes on start
« on: November 20, 2024, 05:58:26 pm »
Hi FSDT,

My FSDT Installer / Live Update crashes as soon as it starts. Event viewer I see the following error:

Code: [Select]
Faulting application name: Couatl_Updater2.exe, version: 2.0.4.7, time stamp: 0x673db117
Faulting module name: KERNELBASE.dll, version: 10.0.22621.4391, time stamp: 0x75ef7fcd
Exception code: 0xe0434352
Fault offset: 0x0014b342
Faulting process id: 0x0x22F0
Faulting application start time: 0x0x1DB3B6D0D9C9298
Faulting application path: C:\Program Files (x86)\Addon Manager\Couatl_Updater2.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 80644cf5-3884-491e-a6e8-33f7aee2064e
Faulting package full name:
Faulting package-relative application ID:


Code: [Select]
Application: Couatl_Updater2.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Xml.XmlException
   at System.Xml.XmlTextReaderImpl.Throw(System.Exception)
   at System.Xml.XmlTextReaderImpl.Throw(System.String, System.String[])
   at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[], Int32, Int32)
   at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32, Char, NodeData)
   at System.Xml.XmlTextReaderImpl.ParseAttributes()
   at System.Xml.XmlTextReaderImpl.ParseElement()
   at System.Xml.XmlTextReaderImpl.ParseElementContent()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.XmlTextReader.Read()
   at System.Configuration.XmlUtil.StrictReadToNextElement(System.Configuration.ExceptionAction)
   at System.Configuration.BaseConfigurationRecord.ScanFactoriesRecursive(System.Configuration.XmlUtil, System.String, System.Collections.Hashtable)
   at System.Configuration.BaseConfigurationRecord.ScanFactoriesRecursive(System.Configuration.XmlUtil, System.String, System.Collections.Hashtable)
   at System.Configuration.BaseConfigurationRecord.ScanFactories(System.Configuration.XmlUtil)
   at System.Configuration.BaseConfigurationRecord.InitConfigFromFile()

Exception Info: System.Configuration.ConfigurationErrorsException
   at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean)
   at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(System.Configuration.ConfigurationSchemaErrors)
   at System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors()
   at System.Configuration.ClientConfigurationSystem.EnsureInit(System.String)

Exception Info: System.Configuration.ConfigurationErrorsException
   at System.Configuration.ClientConfigurationSystem.EnsureInit(System.String)
   at System.Configuration.ClientConfigurationSystem.PrepareClientConfigSystem(System.String)
   at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(System.String)
   at System.Configuration.ConfigurationManager.GetSection(System.String)
   at System.Configuration.PrivilegedConfigurationManager.GetSection(System.String)
   at System.Diagnostics.DiagnosticsConfiguration.GetConfigSection()
   at System.Diagnostics.DiagnosticsConfiguration.Initialize()
   at System.Diagnostics.DiagnosticsConfiguration.get_Sources()
   at System.Diagnostics.TraceSource.Initialize()
   at System.Net.Logging.InitializeLogging()
   at System.Net.Logging.get_On()
   at System.Net.Http.HttpMessageHandler..ctor()
   at System.Net.Http.HttpClientHandler..ctor()
   at System.Net.Http.HttpClient..ctor()
   at Couatl_Updater2.Program..cctor()

Exception Info: System.TypeInitializationException
   at Couatl_Updater2.Program.Main(System.String[])


I have tried offline installer, the addon manager is exlcuded from anti-virus (windows defender), I have resintalled .net framework service, rebooted. I keep hitting the same issue.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51917
    • VIRTUALI Sagl
Re: FSDT Installer / Updater Crashes on start
« Reply #1 on: November 21, 2024, 05:55:43 pm »
Your 2nd log, shows that all errors happened entirely outside our code, which suggest either antivirus interference, or a problem with .NET or any other Windows library.