Updates leave old versions and support files

[Larrydacula]

I've had Affinity Designer for Windows since the initial release. I have the program on an SSD drive that is not Drive C. Every time I update Designer, two unhappy things occur:

1. The initial update dialog does not ask what drive to install on; it installs a new copy of Designer on Drive C/Program Files leaving my prior version on the other drive (Drive F/Affinity) unchanged. To correct this I go back to the Updater and perform an Uninstall; this removes the new copy from Drive C. Going back to the Updater again the dialog box now gives me a browse box so I can select the correct Drive and File. I would be nice if the Updater had the Browse option initially to avoid this exercise; it would be even nicer if the Updater could look and see where I have Designer already on my system and just go there to do the update.

2. The update process does not really update - it just installs a new copy of Designer exe and support files, leaving the previous version and support files intact. I now have multiple versions plus support files in sub-folders and I don't know what I can safely delete. This is potentially several gigs of trash. It would be nice if an actual update of the prior exe and support files with cleanup happened - or give step-by-step dialogs during update to make the decisions during the process.

Thanks

[walt.farrell]

Welcome to the Serif Affinity forums.

Speaking as a user of the past few releases (since 1.6.something), who always installs on drive E, I can say that the updater has always updated the copy on E, and never installed the update on C. So I have no idea why that's happening for you.

Also, I have Affinity Designer installed in E:\Program Files\Affinity\Affinity Designer, and every update has replaced the appropriate files in that folder. It has never left additional copies around. You're right that it's not a true update, except on Mac. On Windows it is a full reinstallation, but it has never left anything old, for me. Again, I'm not sure why you're experiencing this problem.

[Larrydacula]

Walt-

Thanks for your quick response. Perhaps the problem is my file structure, since my chosen drive F has no Program Files folder. I wonder if the updater is searching for a Program Files/Affinity structure and, finding none, goes to the only Program Files folder on my system (Drive C) and creates the Affinity sub-folder depositing the update there. That is what the updaters are doing on the first pass. As for not correctly updating prior versions, that could also be due to my file structure, since the priors are in separate sub-folders. I've had to re-install several times due to hard drive failures and changing PCs, so my file structure likely got muddied in the process. Version 1.7 is in F:/Affinity/Affinity and 1.6 is in F:/Affinity/Affinity Designer; 1.7 did not update 1.6 and now 1.8 has not updated 1.7.

This is the only program I've had update issues with on Drive F. Most program updates seem to key on version numbers or internal file IDs and not file structure, but perhaps Serif does it differently. I'll just move my project files out of those confusing sub-folders, move the sub-folders to the recycle bin and make sure everything still works. Then next update I'll see what happens.

[walt.farrell]

It shouldn't matter whether your F drive has a Program Files folder; I just made one on my E drive for consistency with C.

I do recall that the directory name used has changed once or twice, which may be what you've seen. Sorry for not remembering that. I'll have to take a look on another of my machines to confirm that.

[John Rostron]

I have always installed my Applications onto drive D:, with the Affinity apps in D:\Affinity, and they have always updated wwith no problems.

John

[Larrydacula]

John and Walt-

Since there were no prior threads on this issue, I suspected that it was not commonly happening. I have three other apps on the same drive that update frequently with no issues, but they do so automatically so it's not quite the same situation. Based on your input I can only conclude that something about my file structure is confusing the Affinity updater. My only criticism then is to note that most installer/updater programs, if they find something unexpected, open an interrogative loop to resolve the issue with user input before installing in an unwanted location. However if my experience is a rare problem it hardly warrants Serif to change how they update Affinity.

Thanks for your interest.

[AnaliseThis]

Larrydacula,  I have the same issue as you, I have just updated all my Affinity suite to 2.2.1 but, if I click on, lets say, the Publisher icon from my start menu, version 2.1.1 opens and then informs me that there is an update to do.

If Affinity updates overwrite previous versions, how come I can still run v2.1.1 after updating to v2.2.1

I have also been able to run v2.0.0 if I click on an .afpub file created in that version and not updated since. Not had that happen though for a long time.

It makes no sense what you say Will, because that is clearly not the case.

My installs are done on drive C:\program files and I have never installed them any where different.  I am however using the msix files instead of the exe updates.  Could this be the problem?

Attached is a copy of two versions that currently run on my PC.  This screen shot was done today 20-Oct-23, straight after updating Publisher to v2.2.1

[carl123]

There are 2 version of each of the Affinity apps, MSIX and EXE

I believe each can co-exist on the same PC

So, it's possible you inadvertently installed the wrong version when you "updated". Resulting in a second installation of the same app

Best course of action is to uninstall the last version you installed (the 2.2.1 version) and to correctly install/update your MSIX or EXE version - depending on which you installed originally

 

 

[AnaliseThis]

carl123,  I think you are correct, I have just downloaded the exe version and installed it, it has definitely fixed the start menu icon problem, version 2.2.1 now opens correctly.

I have looked at all my update files, which I keep and apart from two, they are all exe versions.  The two msix updated were the last two I did.

That's why I had two versions co-existing.

Wont be doing that again.  Sticking with the exe download from now on.

Thanks.