Leigh

I know a similar issue was originally logged back in 2017 but that was fixed. Just to confirm, do you have the latest version of our apps installed? I will check with our QA team to see if they've been able to replicate the issue in 1.7. @ssystem @ekwkosox & @pic are you able to zip up all of your fonts and upload to our dropbox account using this the below link? Please rename the zip file to your forum username so I know who uploaded to the file https://www.dropbox.com/request/nWysgFrcmGDWpiI0bwZ1 I will then get our QA team to look into this further for you all.

When you launch the app it will tell you how many days are remaining of your trial. You can press the Unlock with Product Key button to enter your details and unlock the app.

I've tried again and they're working fine, strange. Did you manage to try manually removing fonts at your end to see if you could narrow it down to a particular font?

Thanks David - I will give it another try.

We've had users report that when trying to launch our apps on Windows they're getting a Blue Screen of Death message relating to cldflt.sys. This is also affecting other apps including Microsoft's Visual Studio as reported on the Microsoft Developer Forums. This BSOD error started appearing after Microsoft released the Windows 10 KB4517389 update. Below are several methods that have been known to fix the issue for Affinity users: Disable or remove/reinstall OneDrive - this is the suggestion offered by Microsoft on their Developer Forum here. Manually disable the cldflt service by opening Command Prompt as an Administrator and running the below commands: sc config cldflt start=disabled sc stop cldf Remove the KB4517389 update - do this at your own risk

Welcome to the forum MrSwitch AFAIK, our apps don't make use of Intel MKL. I know that @Anstellos tried our apps with an AMD Ryzen 7 3700X CPU and was happy:

Thanks for sending my your fonts. Unfortunately, I've been unable to replicate your issue. We can only suggest that you try temporarily removing all fonts that are not default to Windows 10 and try adding several fonts back at a time to see if you can find out which font is causing your issue.

I've download that font but i've been unable to replicate the issue. Is it possible to go to C:\Windows\Fonts and copy all of the fonts to a .zip file and upload it to our Dropbox account using the following link: https://www.dropbox.com/request/G1JDIhKfkCFi2RnN2a1T Alternatively, you can try temporarily removing all non-system fonts and see if you get the same issue. We would like to find out which font is causing the issue.

I'm back Looking at your EventViewer Logs, it appears that a font is causing the issue: Have you installed any new fonts recently or just before installing the 1.7.3 update? Do you use a font manager? We're going to have to try and narrow down which font is causing the issue.

Thanks. I'm going to hide them while I take a look. I'll get back to asap.

Thanks for replying and trying my suggestion. I'm sorry that you're still having this issue. Is it possible to send me your Application Logs from EventViewer? It might have some additional information related to your issue. Please follow the instructions provided on Microsoft's TechNet article: How to save a copy of the Event Viewer Application and System logs

Common errors shown in SetupUI.log There are several known errors that can be easily spotted within the SetupUI.log file that might allow you to resolve your own issue. The SetupUI.log file can be opened in a text editor, such as NotePad, to be viewed. The Installer has Insufficient Privileges to Access this Directory If you see the below error in the middle of your log file, please restart your machine and try installing Affinity again. +Error: The installer has insufficient privileges to access this directory: C:\Program Files\Affinity\<APP Name>. The installation cannot continue. Log on as administrator or contact your system administrator. +Info: Action ended 18:20:43: InstallFinalize. Return value 3. FastPictureViewer Codec Pack We know that it's possible for the FastPictureViewer Codec Pack to cause our app to crash on startup, but it's also possible for it to cause .NET to crash and stop our installer from working. If you see the below information at the bottom of your log file, please temporarily remove or Install version 1.4.7.6 or later and try installing Affinity again. Message: Operation caused an invalid state. StackTrace: at System.Windows.Media.Imaging.BitmapDecoder.SetupDecoderFromUriOrStream(Uri uri, Stream stream, BitmapCacheOption cacheOption, Guid& clsId, Boolean& isOriginalWritable, Stream& uriStream, UnmanagedMemoryStream& unmanagedMemoryStream, SafeFileHandle& safeFilehandle) at System.Windows.Media.Imaging.BitmapDecoder.CreateFromUriOrStream(Uri baseUri, Uri uri, Stream stream, BitmapCreateOptions createOptions, BitmapCacheOption cacheOption, RequestCachePolicy uriCachePolicy, Boolean insertInDecoderCache) 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) Corrupted Colour Profile Sometimes a colour profile assigned to your display(s) can be corrupted and cause .NET to crash and stop our installer from working. If you see the below information at the bottom of your log file, please try temporarily changing your display's colour profile to sRGB and try installing Affinity again. Message: The operation completed successfully. (Exception from HRESULT: 0x80070000) StackTrace: at System.Windows.Media.ColorContext.FromRawBytes(Byte[] data, Int32 dataLength, Boolean dontThrowException) at System.Windows.Media.ColorContext.FromStream(Stream stm, String filename) at System.Windows.Media.ColorContext.Initialize(Uri profileUri, Boolean isStandardProfileUriNotFromUser) at System.Windows.Media.ColorContext..ctor(PixelFormat pixelFormat) 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) More information about changing your display's colour profile can be found on Microsoft's website here.

Thanks for attaching your log file. Just to confirm, did you try resetting the app as suggested by Callum in his reply to Chicane00? I can see from the log file that you have a NVIDIA GeForce GT 630 GPU. We've had similar issues in the past where out of date GPU drivers were to blame. Can you download and install the drivers again from Nvidia and when prompted, select the Perform clean install option. If that doesn't change anything. Can you try opening the app until it stays open and then go to Edit > Preferences > Performance and let me know which options you have in the Renderer drop down menu.

Thanks for replying. When the app loads and then disappears from screen, does the process continue to run? When the app next fails to load, can you go to %appdata%\Affinity\Photo\1.0\ and attach the log.txt file to your post. You could check out EventViewer to see if there is anything listed in the Applications Log relating to Affinity.

Thanks for the information David. Can you try running the app using the No Hardware Flag? You can do this by pressing the Windows Key + R on your keyboard to open the Run dialog and then type CMD and press Enter. This will launch Command Prompt. Presuming you have the app installed in the default location, type in cd "C:\Program Files\Affinity\Photo\" and press Enter. Now type Photo --no-hw-ui and press Enter - does the app now open correctly?