Affinity Photo not installing

[noelw]

I have run Photo since v1.5, with updates through to v1.8.3.  Neither 1.8.4 or 1.8.5 would install and my existing installation then failed to load.  I have removed Photo with a view to reinstalling, but without success.  I'm on W10 and the only changes that will have occurred are MS updates including 2004.  The SetupUI.log states that image data generated an overflow during processing.

Any suggestions which will allow the restoration of Photo would be appreciated

Noel

[Lee D]

Try the suggestions in this FAQ post, especially the Corrupted Colour Profile. If these fail to resolve the issue, please attached the log files so they can be checked over.

[noelw]

Thanks for the response - I've looked at the FAQs.  As Photo was previously installing and then running, I've a gut feeling that one of the MS recent updates has caused the problem.  The text from SetupUI.log is below.

+Startup: 01/11/2020 3:10:30 PM
+OS version: 10.0.19041
+ProductName: Photo
+ProductType: Retail
+Opening HKLM...
+    OK
+Opening registry key: 'SOFTWARE\Serif\Affinity\Photo\1'...
+    Failed
+Getting ProgramW6432 environment variable...
+    OK
+Install path not found, using default: C:\Program Files\Affinity\Photo
+Opening MSI database: Affinity.msi
+Opening database view: SELECT `Value` FROM `Property` WHERE `Property`='ProductVersion'
+    OK
+MsiViewExecute
+    OK
+MsiViewFetch
+    OK
+MsiRecordGetString
+    Value: 1.8.5.703
+Opening database view: SELECT `Value` FROM `Property` WHERE `Property`='ProductCode'
+    OK
+MsiViewExecute
+    OK
+MsiViewFetch
+    OK
+MsiRecordGetString
+    Value: {E0A227B9-8299-48C6-9FB2-71140FEF82B4}
+Install state: -1
+    IsThisVersionInstalled: False
+Opening database view: SELECT `Value` FROM `Property` WHERE `Property`='UpgradeCode'
+    OK
+MsiViewExecute
+    OK
+MsiViewFetch
+    OK
+MsiRecordGetString
+    Value: {21399BDD-4C2C-4565-9426-410BDC894DA7}
+MsiEnumRelatedProducts: 259
+    IsAnyVersionInstalled: False
+ProductCode: {E0A227B9-8299-48C6-9FB2-71140FEF82B4}
+ProductVersion: 1.8.5
+InstallType: Normal
+Initialising main window...
+    OK
+Main window loaded
+Unhandled exception:
+  Message: The image data generated an overflow during processing.
+  StackTrace:
   at System.Windows.Media.Imaging.ColorConvertedBitmap.FinalizeCreation()
   at System.Windows.Media.Imaging.ColorConvertedBitmap..ctor(BitmapSource source, ColorContext sourceColorContext, ColorContext destinationColorContext, PixelFormat format)
   at System.Windows.Media.Imaging.BitmapImage.FinalizeCreation()
   at System.Windows.Media.Imaging.BitmapImage.EndInit()
   at System.Windows.Media.Imaging.BitmapImage..ctor(Uri uriSource, RequestCachePolicy uriCachePolicy)
   at System.Windows.Media.Imaging.BitmapImage..ctor(Uri uriSource)
   at SetupUI.MainWindow.UpdateImage()
   at SetupUI.MainWindow.OnLoaded(Object sender, RoutedEventArgs e)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   at System.Windows.UIElement.RaiseEvent(RoutedEventArgs e)
   at System.Windows.BroadcastEventHelper.BroadcastEvent(DependencyObject root, RoutedEvent routedEvent)
   at System.Windows.BroadcastEventHelper.BroadcastLoadedEvent(Object root)
   at MS.Internal.LoadedOrUnloadedOperation.DoWork()
   at System.Windows.Media.MediaContext.FireLoadedPendingCallbacks()
   at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
   at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
   at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)
   at System.Windows.Media.MediaContext.Resize(ICompositionTarget resizedCompositionTarget)
   at System.Windows.Interop.HwndTarget.OnResize()
   at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

+  Inner message: Overflow or underflow in the arithmetic operation.
+  Inner stackTrace:

[walt.farrell]

1 hour ago, noelw said:

As Photo was previously installing and then running, I've a gut feeling that one of the MS recent updates has caused the problem.

Yes, that's quite possible, in fact likely. Did you try resetting your Windows color display settings as suggested in the FAQ?

Here are some additional threads about similar problems:

 

[noelw]

Thanks.  That'll teach me to put my brain in gear, as I missed the relevant bit in Colour Management (so used to looking at the icc profiles for printing).  Changed from the virtual device profile, restarted and Photo then installed without a hitch.

[walt.farrell]

You're welcome.

I suspect that Serif is going to have to do something to allow those virtual profiles, or at least to detect the problem and tell the user how to fix it.

[Patrick Connor]

20 minutes ago, walt.farrell said:

You're welcome.

I suspect that Serif is going to have to do something to allow those virtual profiles, or at least to detect the problem and tell the user how to fix it.

I believe windows betas 1.9.0.815 and 1.9.0.820 have addressed this, as you say it is needed.

From the 815 release notes

Quote

Fixed crash when the current monitor profile is set to a virtual profile