John_Stuart

It appears to have worked. A new installation from MS is up and running. Sad to say, I bought the direct copy in March - rather more than 14 days ago. Many thanks again.

Hi Alfred This looks like a workaround. It seems I may have bought the second licence unnecessarily. Though I'm not sure how to check with the MS store how many installations are allowed, the site does still give me the option to download so I'll try replacing the version from Serif with one from Microsoft. Doesn't really excuse the failure of the copy bought direct from Serif to update, though. Many thanks John

Thanks for replying. As best I recall, for my old machines I got the program from Microsoft but the licence only covered 2 machines. For the new one, I got it from Serif. The update behaviour is quite different. The old machines updated almost invisibly and no installation files were left over. The new one merely points me to the download link when I start Affinity and click the "download" button; the alternative is "OK" which appears to do nothing. My point here is that Affinity is choosing this link, not me. Downloading then works, but installation fails.

Hi On my old PC, Affinity photo, bought from the Microsoft store, updated automatically. On my new one, I had to download the file manually. However, it refuses to run properly. The OS is Windows 10 21H1 Build 19043.1165. Currently loaded Affinity Photo is 1.9.2.1035 Simply double clicking on the downloaded file produces a splash screen saying that Affinity will be updated; clicking on "update", it then prompts for an administrator password. Given the password, it enters a loop, going back to the splash screen, with no error or other information. Running as administrator produces an access error, and says "you may not have permission to access the file" (moving the file to the administrator desktop and trying to run it from there did not help). Looking at the Security tab in the file's properties suggests that the permissions are incorrectly ordered. Reordering them and editing them to allow "everyone" full access seems to have no effect - double clicking leads to the loop and running as administrator runs into the access issue, as before. Regards John