Failure to Start Affinity Photo

[markbs]

Affinity Photo 1.10.6 ie most recent, but also in 1.10.5 before update.  Not sure when this started to happen.

Shows splash screen and then terminates. Windows event log shows an unhandled application exception.

Application: Photo.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
   at <Module>.PersonaController.InitPersona(PersonaController*, Kernel.StringT<Kernel::TEncUtf8>*, Int32, Int32, Kernel.StringT<Kernel::TEncUtf8>*, Kernel.StringT<Kernel::TEncUtf8>*, Kernel.StringT<Kernel::TEncUtf8>*, Kernel.StringT<Kernel::TEncUtf8>*, Int32, Int32, Double, Boolean, Boolean, Boolean, Boolean, Boolean, Boolean, Boolean, Boolean, Boolean, Boolean, Kernel.Counted<MigrationPlatformData const >*, Boolean, Boolean, Boolean, Boolean)
   at Serif.Interop.Persona.Services.InteropService.Initialise()
   at Serif.Interop.Persona.Application.OnServicesInitialised(Serif.Interop.Persona.Services.IServiceProvider)
   at Serif.Affinity.Application.OnServicesInitialised(Serif.Interop.Persona.Services.IServiceProvider)
   at Serif.Interop.Persona.Application.OnStartup(System.Windows.StartupEventArgs)
   at System.Windows.Application.<.ctor>b__1_0(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.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 Photo.Application.Main(System.String[])

 

[Komatös]

Hi @markbs and welcome to the forums.

Please download and install the latest .NET Framework 4.8.1!

https://dotnet.microsoft.com/en-us/download/dotnet-framework

[markbs]

Hi,

I already had the 4.8.1 update for Jul-23. I have installed it again via the MS link. No change. Photo still aborts after the splash screen. Is Photo using 4.8.1 because the event log says 4.0. Now in a different module of Photo.  Noting many other issues in this forum, my graphic hardware acceleration is off.

Application: Photo.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
   at <Module>.Raster.Hardware<Raster::DefaultImplementation>.GetHardwarePossible()
   at Serif.Interop.Persona.Settings.PerformanceSettings.get_CanUseHardwareAcceleration()
   at Serif.Interop.Persona.Settings.PerformanceSettings.get_UseHardwareAcceleration()
   at Serif.Interop.Persona.Services.InteropService.Initialise()
   at Serif.Interop.Persona.Application.OnServicesInitialised(Serif.Interop.Persona.Services.IServiceProvider)
   at Serif.Affinity.Application.OnServicesInitialised(Serif.Interop.Persona.Services.IServiceProvider)
   at Serif.Interop.Persona.Application.OnStartup(System.Windows.StartupEventArgs)
   at System.Windows.Application.<.ctor>b__1_0(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.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 Photo.Application.Main(System.String[])

[markbs]

Further information.

Installed 1.10.6 on a second m/c. Works OK. But this m/c is a laptop with a screen unsuitable for image editing.

Complete uninstall on 1st m/c. Uninstall removed whole of ProgramFiles\Afinity.  Also manually removed residual registry keys. New install of 1.10.6. Problem as reported above, no change. This seems to be something idiosyncratic about 1 PC, so unlikely to be able to solve. 

[DWright]

Can you please confirm the Windows build version that you are running 

[markbs]

Both m/c are Windows 10 Home, version 22H2 (ie, current).

The non-working m/c has build 19045.3271

The working m/c has build 19045.3208

Both flag in Windows Update as fully up to date. The minor difference in build number may be because the non-working m/c also had the optional Jul-23 Windows update installed today but that made no difference to Affinity Photo.

[markbs]

Supplementary, the non-working m/c has processor  i5-2320. The working m/c has processor i3-2330M. So, both are 2nd generation chips, admittedly quite old, but not significantly different to account for the failure of one. 

[markbs]

Further information.

In separate threads about Affinity applications crashing on opening, there is a recommendation to start with the option --no-ocl   (OpenCL). A bit of a fiddle to add this option to the Affinity shortcut, but it is the solution.

So, it's not the Windows updates, and it's not the .NET updates, and its not the graphics driver or the hardware acceleration (which was False anyway). As 1.9.x versions did work OK, it is something introduced by Affinity in 1.10.x