monsieurgaz

Hi @walt.farrell, @Pšenda, you're correct, this is my experience on my laptop with my applications. I use a wide range of applications from Open Source to commercial and the Serif products are the only ones triggering this behaviour. The difference here is also that AP as a single applciation has a relatively high one-off cost and regardless of where the exact blame lies, Serif should be driving to either make there products robust in not triggering the BSOD's (why are they interacting with a Cloud optimiser?) or driving Microsoft to patch their code if it is truly at fault. I've seen no evidence of this unfortunately. I'll ask again - Is this forum and the format of this post the recommended channel for official support or do I need to repost? I've had to process a refund and am forced to use Adobe products at present instead but may return if this issue is resolved and I can see evidence of good official product support.

Hi @GerardLakke, I was in a very similar position to you, hamstringing OneDrive isn't a reasonable option for me. I contacted MS Store via Chat support and requested a refund, stating I'd tried the support channel here with no official help offered, stating that the SW is in-operable and requested a refund which they did process for me. I had initially contacted the Affinity Refund email and they directed me to MS Store so do press your case with them. Good luck, this may be something deep in Microsoft's code but I personally am having no issues with any other applciation I use and Adobe Illustrator and Photoshop are running fine so I'm forced to use them for the time being.

Hi @emmrecs01, I appreciate your enthusiastic support of Serif but - Microsoft supply lower level mechanisms which clearly are able to be used in a way which causes a BSOD; this should be made more robust BUT it does not mean that the Affinity Photo SW isn't misusing or attempting unrecommended or unsupported methods of using these resources. What is evident is that Affinity Photo is absolutely the only program causing this behaviour which suggests to me that no other program (including Affinity Designer is using the lower level services like Affininity photo is. As @HarriK has said, his workaround is not viable for a professional workflow, particularly if it could have unexpected effects on OneDrive behaviour which we rely on. Is this forum really the only means for support? Thanks

Thanks @DWright and @HarriK - Unfortunately I rely on OneDrive for my daily workflow so cannot uninstall it. I read @HarriK's linked thread, dissapointing its almost a month with no proper response. Nothing else has ever produced a BSOD on this device, it's clearly an interaction from Affinity Photo causing it and they can't keep saying that Photo cannot cause a BSOD - basic logic shows it is. Think I'll push for a refund until this is resolved.

Hi, I've just bought Affinity Photo on the Microsoft store, installed fine but has not started up once correctly. The splash screen loads, then I get a BSOD - every time I've tried to run the application. It's reporting cldflt.sys as having failed. I'm on a Microsoft Surface Pro (5th Gen) Windows 10 Pro Version 10.0.18362 Build 18362 I have designer and it starts and runs fine. I tried running Microsofts DISM Tool and SFC tool as described here: https://support.microsoft.com/en-gb/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system Both completed successfully, Photo still causes BSOD Read it might be linked to OneDrive - Tried exiting OneDrive, still get BSOD This is really dissapointing for a £50 new purchase.