I didn't run P2A V3 some time, now today, I got an appcrash each time I start it, a reboot didn't resolve the issue.
It may be related to Windows 10 22H2 or DOTNET updates in the last weeks.
Windows event viewer shows me two consecutive error msgs:

1. Application: Pilot2ATC_3.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException
   at System.Windows.DependencyObject.SetValueCommon(System.Windows.DependencyProperty, System.Object, System.Windows.PropertyMetadata, Boolean, Boolean, System.Windows.OperationType, Boolean)
   at System.Windows.DependencyObject.SetValue(System.Windows.DependencyProperty, System.Object)
   at Pilot2ATC_3.ViewModel.MainWindowVM.ShowFltPlan()
   at Pilot2ATC_3.MainWindow.DataLoaded(System.Object, System.ComponentModel.RunWorkerCompletedEventArgs)
   at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(System.ComponentModel.RunWorkerCompletedEventArgs)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at Pilot2ATC_3.App.Main()

2. In the same second:

Faulting application name: Pilot2ATC_3.exe, version: 3.0.0.0, time stamp: 0xc3dd21ff
Faulting module name: KERNELBASE.dll, version: 10.0.19041.5678, time stamp: 0x024a42e4
Exception code: 0xe0434352
Fault offset: 0x000000000003b699
Faulting process id: 0x3988
Faulting application start time: 0x01dbce41fde928eb
Faulting application path: C:\Games\Pilot2ATC_3_x64\Pilot2ATC_3.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 81eefbbe-6cb8-41a9-8de7-fd04d8406c4a
Faulting package full name:
Faulting package-relative application ID:

I found Pilot2ATC_3.exe.xxxxx.dmp files for each incident, if you need them, I will upload.
I can provide a list of Windows/Dotnet Updates (KB...) in this system of the last weeks too on request.

Meanwhile I work with P2A V2, no problem.

Update 1: I remember I did an update of VS C/C++ runtime 64bit for another app some time ago.

Update 2:Sorry, forgot the update Office 2016 (32bit) -> Office 2024 (64bit) last week.

Edited May 26, 20251 yr by QuaxTheSnoopie
update: VS C/C++ runtime 64bit update; office 2016-32 -> 2024-64 update

Thanks.

This should be fixed in the next update, hopefully soon.

Dave

Sorry to say but it seems, update  0.2.1 didn't fix my problem, same crash as before.

Correction: as I would have shown you more of problem data here, I typed in this answer...
...then decided to investigate a little deeper and eventually resolved the crash.

At first, I thought about a parameter error, so I renamed AppData\Roaming\P2A_300\Settings\AppSettings.xml
and as I suspected, P3D V3 created this file from scratch.

Then I prepared copies of old and new AppSettings by deleting unnecessary lines (Notepad++) to review them.

After I extracted the most part of different lines for later analysis,
luckily the different size/position parameters of "MainWindow..." and "FreqWindow..:" caught my eyes

I tried it: renamed the old file back to AppSettings.xml and removed these window size/position parameters and voilà:
Pilot2Atc V3 0.2.1 started without crash.

Problem solved.

Thanks.

I'll see if I can isolate that error and handle it to avoid a crash.

Dave