Jump to content

ASUPDATER crash on startup


Recommended Posts

when I open the Aerosoft Updater, it crashes after a white window appears for some seconds.

Installed version 1.6.0.0.

I have checked all the xml files in the Products directory and all appear to be fine.

I uninstalled all products and reinstall only AS330 for p3dv4

but is the same issues

i tried to install old version 1.4.0.0 but at startup he update it automaticlly and crash after it.

Thanks for your help.

 

 

 

Please login to display this image.

Link to comment
Share on other sites

  • Deputy Sheriffs

Please check the Windows Eventviewer for an entry at the time of the crash.

Did you change anything (updates, new software) before the crash happens?

Link to comment
Share on other sites

i change nothing i uninstall all products and  clean the register

but after when i reinstall the A333 product all fine when i start the AS updater white window open and automaticlly he start an update and then he crash few second later (in admin mode)

 

 

 

Link to comment
Share on other sites

  • Deputy Sheriffs

So you "cleaned" the Windows registry manually? maybe something went wrong. And no need to run the ASUpdater as Admin.

And again, any error message in the eventviewer?

 

Link to comment
Share on other sites

Application : ASUpdater.exe
Version du Framework : v4.0.30319
Description : le processus a été arrêté en raison d'une exception non gérée.
Informations sur l'exception : System.NullReferenceException
   à ASUpdaterLib.SimUtils.GetMSFSSteamVersion()
   à ASUpdaterLib.SimUtils.GetMSFSSteamPath(System.String ByRef, Boolean ByRef, System.String ByRef)
   à ASUpdaterLib.SimUtils.GetMSFSPath(System.String ByRef, Boolean ByRef, System.String ByRef)
   à ASUpdaterLib.SimUtils.GetFSPaths()
   à ASUpdater.MainWindow.GetFSPaths()
   à ASUpdater.MainWindow.InitApp()
   à ASUpdater.MainWindow.ASUpdaterWindow_Loaded(System.Object, System.Windows.RoutedEventArgs)
   à System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
   à System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   à System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
   à System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs)
   à System.Windows.BroadcastEventHelper.BroadcastEvent(System.Windows.DependencyObject, System.Windows.RoutedEvent)
   à System.Windows.BroadcastEventHelper.BroadcastLoadedEvent(System.Object)
   à MS.Internal.LoadedOrUnloadedOperation.DoWork()
   à System.Windows.Media.MediaContext.FireLoadedPendingCallbacks()
   à System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
   à System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object)
   à System.Windows.Media.MediaContext.RenderMessageHandler(System.Object)
   à System.Windows.Media.MediaContext.Resize(System.Windows.Media.ICompositionTarget)
   à System.Windows.Interop.HwndTarget.OnResize()
   à System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)
   à System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   à MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   à MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   à System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   à System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   à System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   à MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

 

Nom de l’application défaillante ASUpdater.exe, version : 1.6.0.0, horodatage : 0x5f3b902c
Nom du module défaillant : unknown, version : 0.0.0.0, horodatage : 0x00000000
Code d’exception : 0xc0000005
Décalage d’erreur : 0x029cdc61
ID du processus défaillant : 0x36cc
Heure de début de l’application défaillante : 0x01d690dad7679faf
Chemin d’accès de l’application défaillante : C:\Users\xavie\Documents\Aerosoft\ASUpdater\ASUpdater.exe
Chemin d’accès du module défaillant: unknown
ID de rapport : addf4972-7f38-4dbe-bed1-86842eefd8b1
Nom complet du package défaillant : 
ID de l’application relative au package défaillant : 

 

Détecteur d'erreurs 1692502247853114535, type 5
Nom d’événement : CLR20r3
Réponse : Non disponible
ID de CAB : 0

Signature du problème : 
P1 : ASUpdater.exe
P2 : 1.6.0.0
P3 : 5f3b902c
P4 : ASUpdaterLib
P5 : 1.6.0.0
P6 : 5f3b902a
P7 : 6f
P8 : 65
P9 : System.NullReferenceException
P10 : 

Fichiers joints :
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EEB.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FF6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5007.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5014.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5035.tmp.txt

Ces fichiers sont peut-être disponibles ici :
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ASUpdater.exe_bca43287cfb9dadbe988d2a89c2a85783879987_be89ea7c_55080b8e-1a52-462f-a412-9b2d9b85f423

Symbole d’analyse : 
Nouvelle recherche de la solution : 0
ID de rapport : addf4972-7f38-4dbe-bed1-86842eefd8b1
Statut du rapport : 268435456
Récipient avec hachage : 92dd92ac5f5c8933f77cf9d3c0d5c4a7
GUID CAB :0

Link to comment
Share on other sites

AS app log

 

New Log started: mardi 22 septembre 2020
Retrieving Resource Dictionary
Culture: fr-FR
Selected source: ..\Resources\StringResources.fr-FR.xaml
Dictionary merged
Loading URIs
LoadURIs: Create path
LoadURIs: Reading server URIs
LoadURIs: Server EU done
LoadURIs: Server World done
URIs loaded
Loading configurations
Configurations loaded
Seuls des mises à jours régulières sont disponibles pour l'installation


Before CheckUpdaterUpdates()
Update found. Exiting ASUpdater
After CheckUpdaterUpdates()
Before GetFSPaths()
Before GetFSPaths()
 

Link to comment
Share on other sites

Hi

Since the ASupdater-update this  summer. The updater does not work for me. My issue was not solved either. This is not a critique.. Just to stress, when this issue keep popping up,  that there seem to be a problem with updater... And it would be nice to find the issue so the updater will work again..

 

Thank you

 

Jens Michlas

Link to comment
Share on other sites

  • Developer

As I can not reproduce the problem, I added some error handling code to the updater which should, at the very least, avoid any crashes while retrieving the version number from the Steam MSFS.

 

Please give this version a try and let me know if it fixes the issue: ASUpdater_1600_Test.zip  (unzip to <Documents>\Aerosoft\ASUpdater and replace existing files). Thank you.

Link to comment
Share on other sites

  • 1 month later...
On 9/25/2020 at 1:20 PM, Hans Hartmann said:

As I can not reproduce the problem, I added some error handling code to the updater which should, at the very least, avoid any crashes while retrieving the version number from the Steam MSFS.

 

Please give this version a try and let me know if it fixes the issue: ASUpdater_1600_Test.zip  (unzip to <Documents>\Aerosoft\ASUpdater and replace existing files). Thank you.

This did not fix the crash on startup I use MSFS from the Microsoft Store not Steam but it looks the ASUpdater is closing right when it looks for MSFS. I removed the xml MSFS scenery and opened the updater with no crashing. Working normal only with P3D addons in.

Link to comment
Share on other sites

  • 2 weeks later...

I might have the same issue as I recently uninstalled all P3D addons and the sim itself on my main system.

Currently only MSFS (1.10.8.0) is installed and 3 Aerosoft Addons (EDDK, Trondheim and Paderborn 1.0.1.0). 

 

The product xml files look normal, no weird typos at the beginning. It seems the updater also has no issues with my default document folder being adjusted to another location, according to the log:

 

Quote

New Log started: Sunday, November 8, 2020
Retrieving Resource Dictionary
Culture: en-US
Selected source: ..\Resources\StringResources.xaml
Dictionary merged
Loading URIs
LoadURIs: Create path
LoadURIs: Reading server URIs
LoadURIs: Server EU done
LoadURIs: Server World done
URIs loaded
Loading configurations
Configurations loaded
Only regular updates are available for installation


Before CheckUpdaterUpdates()
Update found. Exiting ASUpdater
After CheckUpdaterUpdates()
Before GetFSPaths()
Before GetFSPaths()
Before trimming FSX path
Before trimming FSX-SE path
Before trimming P3Dv3 path
Before trimming P3Dv4 path
Before trimming P3Dv5 path
After trimming paths
After GetFSPaths()
Before output FSX version
After GetFSPaths()
Before CheckXPPaths()
After CheckXPPaths()
Before GetProductList()
Document folder: D:\data\Documents
Product folder: D:\data\Documents\Aerosoft\ASUpdater\Products
3 files found in product folder

 

Please login to display this image.

Link to comment
Share on other sites

10 hours ago, a2h said:

I might have the same issue as I recently uninstalled all P3D addons and the sim itself on my main system.

Currently only MSFS (1.10.8.0) is installed and 3 Aerosoft Addons (EDDK, Trondheim and Paderborn 1.0.1.0). 

 

The product xml files look normal, no weird typos at the beginning. It seems the updater also has no issues with my default document folder being adjusted to another location, according to the log:

 

 

Please login to display this image.

 

It works now, sorry for the confusion. I had at least 2 instances of the ASUpdater installed. I removed those and re-installed the sceneries.

It worked only after the sim was running once though. 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use