Search the Community

I've been trying to recreate my character sheet for the Marvel Super Heroes RPG using publisher. On Windows 10, it causes a BSOD on save. On my Mac Pro (mid-2010) running macOS Mojave, it will cause a beachball of death after about ten to twenty minutes of use. At which point I have to power off the system and continue on the next boot. Rinse and repeat until finished. This is totally unacceptable for a pro product.

I just bought Publisher via the Microsoft store, this morning. That's how I previously purchased Photo, as well. Photo opens and runs just fine. Publisher is giving me a BSOD before it even completes opening. I've run the scan from the command app. I've done the stop service thing, that I read on here. This is frustrating because I wanted to use the software for something that I need to get done today.

My new install of AF keeps crashing with a BSOD screen and a cldflt.sys error. Windows 10, latest updates, on a Surface Book 16 GB. If there is no solution - other than temper with OneDrive - I will have to give up on this software. Please help me out....

Hi, the Test-Version runs great, so i decided to buy the full Version on the Microsoft Store.. No chance to get this to work! :((( Just BSOD caused by Cldflt.sys (tips like disabling OneDrive etc doesn`t work) when there is no way to fix this i have to give it back. Can`t believe that this Version is sold over Microsoft store What can i do to get it to work? I mean it`s unbelievable that a payed store Version makes trouble like this!!! PS i have a clean, new installed Version of Windows 10 pro on a PC

Can you follow the advice given by @- S - below to see if that resolves your BSOD:

I am not sure when it happened but the grid lines were turned on with my Photo on Windows. When I go to turn that setting off (View - Grid), my computer goes BSOD, collects data, and then reboots. It does this as well when trying to turn off the View - Guides. I assume this is a bug and want to make it aware. I have the most recent version as it is updated via the Windows Store. Anyone seen this before and know what to do?

Hi neosukhy, Welcome to the forums This issue, although triggered when launching Affinity applications, is unfortunately not caused by the Affinity app, as we have no way of causing a BSOD on Windows. Microsoft Support have confirmed this issue is related to the latest Windows 10 update and OneDrive, and affects many other apps - not just Affinity. We've written an FAQ, which I've linked below, detailing steps we recommend taking. If you're still experiencing crashing after this, you will need to contact Microsoft directly. I hope this helps!

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.

Tried that suggestion, and then I could start AF without BSOD. But I als had no longer access to files in my OneDrive folders, so that is definitely not an option. The fixes that are being mentioned in the posts are not installed on my sytem (??), which is completely oup to date. So deinstalling those isnt posible, and no solution either. Im starting to regret buying AF and AD in de MS Store in a BlackFriday heat of the moment.

Hi GerardLakke, Welcome to the forums Please could you try the suggestions found here: https://forum.affinity.serif.com/index.php?/topic/102715-faq-i-get-a-blue-screen-of-death-bsod-relating-to-cldfltsys-when-trying-to-launch-affinity-why/ Thanks C

Hi Ulaxes, I'm sorry to hear Publisher is causing a BSOD on your computer Please could you try the suggestions found here: Thanks C

Hi Mark, thank you for the reply. i saw these faqs and solutions before i wrote this here. I mean it`s the first time i have this kind of problem with a new installed software on a clean installed Windoes 10 (only using "onedrive' --> disabling it makes no difference) and it is definitely caused (in what way ever) by starting Affinity Photo (nothing else caused a BSOD before) and Windows (store). So there must be any ambitions by your company to solve this problem (speak with Microsoft etc). You are earning money with this and the software is still sold over the microsoft store. The problem exists a long time now and nothing seems to be solved.. So what shall i do now? Give it back and try to buy it not over the microsoft store (the demo version not from the store runs good)? Very unhappy with this right now!

From https://answers.microsoft.com/en-us/windows/forum/all/onedrives-cldfltsys-causing-ntfssys-bsod/d2ef7f16-9e45-406f-95ca-6e595271e6d9?auth=1#&page=1 you might try opening a Windows command prompt and entering the following commands:

Hi Claude Chen, Welcome to the forums This issue has been confirmed by Microsoft as a bug in the latest Windows 10 update in conjunction with OneDrive. Although launching the Affinity app can trigger the BSOD, it is unfortunately not the cause of the issue. We've written an FAQ for help troubleshooting this issue, please follow the steps found here - If you're still having problems after following these instructions then please contact Microsoft directly, as they will need to assist here. I hope this helps!

Hi Kin.kerlitzchen, Welcome to the forums I can see from the image you've provided this is the BSOD issue that Microsoft have reported, you can find our repair steps in the thread Walt has linked above. If you're still having trouble please contact Microsoft directly as Affinity is not the cause of this issue, many thanks!

Welcome to the Serif Affinity forums, @Kin.kerlitzchen. Does your PC display the Blue Screen of Death (BSOD)? If so, this FAQ entry might help:

The fix is actually so simple. Be certain that the "OneDrive" app has actually been downloaded and installed on your computer! Head to the Microsoft Store app, search for "OneDrive" then Get and Launch. On reboot, the BSOD will be gone for all aps Affinity and others. https://www.microsoft.com/en-us/p/onedrive/9wzdncrfj1p3?activetab=pivot:overviewtab

I likewise had this same problem, but after a few hours found a solution! Despite the presence of the OneDrive image icon on lower right, as well as the presence of cldflt.sys in c:\windows\system32\driver folder ... you must ensure that the OneDrive App is installed on your system. Simply click the "Microsoft Store" icon, type "OneDrive" in search box, download, launch, reboot. That's all that's needed to end the BSOD!

Do you get a Windows Blue Screen of Death (BSOD)? If so, please see this FAQ entry, especially if the error is for cldflt.sys: If some other error is shown, what error was it?

@walt.farrell Did you try uninstalling and reinstalling OneDrive and Google Drive? Although I've seen a couple of cldflt.sys blue screen reports with other software (I.E. Keepass, Plex, Paint.net, a few AAA games) I've been watching a cldflt.sys bluescreen bug report with Visual Studio (due to it being a Microsoft product) and they've just replied with following: Although this is for a different issue (this is a cldflt.sys BSOD when installing Visual Studio), it may be worth trying if you haven't already. Looking at the release notes, there was a OneDrive client update on 02 October 2019 (19.152.0927.0012); I'm not sure whether or not this is related to the issue. The official OneDrive download page is currently offering 19.174.0902.0013 (17 October 2019), however on the Release Notes page there is a link to an even newer version: 19.192.0926.0012 (13 November 2019), so I'd just skip straight to installing that version, instead of the version on the official download page. You can see what version is currently installed on your machine as per this support article.

Maybe on your computer. Just type "cldflt.sys BSOD" into Google.

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

They can, they will and they are doubtless correct! Sorry. There are a number of threads where Serif Staff have pointed out exactly why Affinity software cannot cause a BSOD. If you do a forum search for "cldflt.sys" you will see that a number of users have reported the same issue, apparently caused by a change made by M$ in a recent Win 10 update (?1903). I am pretty sure the Affinity Developers are as concerned by this problem as you are but i strongly suspect the "resolution" is actually in M$ hands, not Affinity. Can you not use the solution proposed at the end of @HarriK's post two above this one, at least for the time being? Jeff

If you are not using OneDrive for your Cloud storage you can try uninstalling the OneDrive app and if you are still getting the BSOD with Affinity Photo right click the icon on the Start bar and then click More>App Settings and then from the new screen click the Repair option

Yesterday I purchased Publisher through the Microsoft Store. The app has crashed every time I opened it. I get a BSOD and a cldfit.sys failure error message. I tried repairing, resetting, uninstalling and reinstalling, all to no avail. I then deleted the app again and downloaded a trial version directly from Affinity and it seems to be working as it should. I then asked Affinity to honor the Microsoft Store purchase and give me credentials to convert my trial into a full license. Affinity says, without any explanation, that it "would not be possible" and that "[w]e are not able to provide for customers who have bought from other companies." Aside from the fact that we all know it IS possible to simply issue me a product key, does anyone have any suggestions on how to fix this mess? I provided Affinity with proof of purchase, my computer is fully up-to-date and has never had any of the issues caused by the Microsoft version of the Publisher app.