Jon W

We did change the default - several years ago. I'm guessing you've uninstalled this time (which would delete your previously saved install location and product key) where before you always did an upgrade?

Yes it is. The thumbnail handler is used by Explorer to generate thumbnails for all our file types (.afdesign, .afphoto, afpub). Only one DLL can be registered for each file type. It absolutely has to be a shared component - sorry!

Hi meadow, The thumbnail handler is a shared component, which means that if you install multiple Affinity products there will be only one thumbnail handler, shared between all the products. This is why it's in a folder called "Common", and not the one you chose for the application specific files.

Hi monzo, This will be fixed in Publisher 1.7.2.

Hi karlchen68, Can you confirm that the problem only occurs when you drag an image, not when you open it from the File menu? The dragging bug is not fixed in the current beta (1.6.3.96), but it will be in the next one.

Hello, It should be fixed in the next beta. We'll post in the beta forum when we release it.

This is known to happen in 1.6.2 when dragging images into the app. Opening via File > Open should load the Exif data properly. This will be fixed in 1.6.3.

Hi sleepy0827, We have found a bug which might explain your problem. The bug is that Exif information is not loaded when a file with a non_English path is dragged into Photo from another app (e.g. Windows Explorer). Is this how you are opening your file? If it is, please try opening it from File > Open. Does that work? Thanks, Jon

What about %TMP%? You would need to change that too (in 1.6.0) ExifTool in 1.6.1 should work regardless of any non-ANSI characters in your user name or TEMP/TMP path. However, it may still fail if you have installed Photo to a non-ANSI path.

It's OK, I've found the problem - on Windows 7 (and maybe also Windows 8), you'll need to copy some more files: api-ms-win-*.dll ucrtbase.dll Alternatively you could just install the Visual C++ Redistributable for Visual Studio 2015: https://www.microsoft.com/en-gb/download/details.aspx?id=48145 Thanks, Jon

OK, we've found the problem - there are some DLLs missing from the Common folder. We'll fix this in the next release, but for now you can fix it yourself by copying these files from the application folder to the Common folder (e.g. from "C:\Program Files\Affinity\Affinity Designer" to "C:\Program Files\Affinity\Common"): vcruntime140.dll msvcp140.dll Thanks, Jon

Itanium-based CPUs were not being detected, due to an oversight. This will be fixed in the next release. Thanks, Jon

It sounds like you didn't add the "/log" option. We would really like to see the resulting Setup.log file - could you try again please? In Step 3 of Sean's instructions, the "Run" dialog should look something like this:

Jonopen, It doesn't matter whether Designer is running or not; the thumbnail handler is completely separate. Thanks for helping us look into this problem. There are a few more things we can try, which I'll post tomorrow. Jon

Hi Jeff, This sounds like there might be some blank thumbnails in your thumbnail cache. If you use the Windows "Disk Clean-up" utility to delete your cached thumbnails or the relevant drive, they should all appear. Assuming this fixes the problem, please let us know if it ever happens again. Thanks, Jon