Updated C++ but having some odd exception

[Bainerr]

Hi all,

Demon buddy doesn't seem to be starting up post C++ update, can anyone verify the below errors?

System.MissingMethodException: Method not found: '!!0[] System.Array.Empty()'.
at Demonbuddy.MainWindow.*‎**‬‪‪‫‪‎​*‫**​***‪‬*​​‫*()
at Demonbuddy.MainWindow.>8CplJWz7abyzux!wUY2H"\.J%.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Demonbuddy.MainWindow.;C$l@>)7ts<1aF1 'c\,Yb5^\,$.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__0(Object state)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
System.MissingMethodException: Method not found: '!!0[] System.Array.Empty()'.
at Demonbuddy.MainWindow.*‎**‬‪‪‫‪‎​*‫**​***‪‬*​​‫*()
at Demonbuddy.MainWindow.>8CplJWz7abyzux!wUY2H"\.J%.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Demonbuddy.MainWindow.;C$l@>)7ts<1aF1 'c\,Yb5^\,$.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__0(Object state)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

Thanks in advance,

 

[Tony]

use support issues section providing the full log file as attachment plz


closed