F64Images Posted September 13, 2020 Share Posted September 13, 2020 Neither Affinity Photo nor Affinity Designer will Start after upgrade to Window 10 Pro 64bit Version 2004. Both Photo and Designer are versions 1.8.5. This is the error shown in the Windows event log Application: Photo.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ArithmeticException Exception Info: System.OverflowException at System.Windows.Media.Imaging.ColorConvertedBitmap.FinalizeCreation() at System.Windows.Media.Imaging.BitmapImage.FinalizeCreation() at System.Windows.Media.Imaging.BitmapImage.EndInit() at Serif.Affinity.ResourceManager.GetBitmapSourceCore(System.String) at Serif.Affinity.UI.AboutDialog..ctor(Boolean) at Serif.Affinity.Application.RunSingleInstance() at Photo.Application.Main(System.String[]) Application: Designer.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ArithmeticException Exception Info: System.OverflowException at System.Windows.Media.Imaging.ColorConvertedBitmap.FinalizeCreation() at System.Windows.Media.Imaging.BitmapImage.FinalizeCreation() at System.Windows.Media.Imaging.BitmapImage.EndInit() at Serif.Affinity.ResourceManager.GetBitmapSourceCore(System.String) at Serif.Affinity.UI.AboutDialog..ctor(Boolean) at Serif.Affinity.Application.RunSingleInstance() at Designer.Application.Main(System.String[]) Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted September 14, 2020 Share Posted September 14, 2020 Welcome to the Serif Affinity forums. Some other users have reported similar failures which seem to arise due to Windows installing corrupted color profiles. You might try the solutions suggested in these topics: Chris B 1 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.1.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
F64Images Posted September 14, 2020 Author Share Posted September 14, 2020 Thank you very much Walt. It was a color management profile issue. Both Photo and Designer now work. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted September 14, 2020 Share Posted September 14, 2020 You're welcome. Glad to hear it worked. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.1.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
Mark Ingram Posted September 15, 2020 Share Posted September 15, 2020 18 hours ago, F64Images said: Thank you very much Walt. It was a color management profile issue. Both Photo and Designer now work. What was the problem? Was there a colour profile that you had to remove? Can you tell us what it was? Quote Link to comment Share on other sites More sharing options...
F64Images Posted September 15, 2020 Author Share Posted September 15, 2020 Hi Mark, I went into the Windows color management module. Clicked on the Advanced Tab. Clicked on Change System Defaults. Clicked on the Advanced Tab and changed the Windows default device profile from "scRBG virtual device model profile" to "sRBG IEC61966-2.1". I don't know if "scRBG virtual device model profile" was the originally delivered Windows system default or whether I changed it to that at some point in the distant past. It had probably been that way for years though. I can tell you that it wasn't a problem until I upgraded to Windows 10 Pro release version 2004 from the previous release version of Windows 10 Pro. I can also tell you that "sRBG virtual device model profile" does not work either. Apparently there is something about virtual device model profiles that causes problems now. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.