That means you still have another instance Installed.
Once the app is running access the user interface with a bookmark in the browser at http://localhost:3875 or wherever other port you’ve configured
There is a legitimate usecase to have it installed for each user and in the system concurrently, but it takes care to assign unique ports to each instance.
Its a balance between flexibility and ease of use.
In your case your have multiple instances installed, using the same port, and you are launching them indiscriminately from multiple locations.
My suggestion would be to uninstall all instances, (search your drive for duplicacy_web), delete all shortcuts you might have created, and then install one instance the way you want — to the system for the single user. Then it will work in a consistent and predictable way.
What duplicacy can do better if the second instance is being installed (user one when system one exists or vice versa):
- warn the user from the installer and confirm that that’s what they want. Give a choice — [un]install system instance, [un]install user instance.
- create separate, clearly labeled shortcut Duplicacy System vs Duplicacy
- automatically configure different port.
. I still don’t understand why it would be so easy to install or run several instances of a program designed for regular users.
The current behavior that the install target is determined by whether the installer was launched as admin is very bad: unintuitive and non-discoverable, and is the source of confusion for windows users all the time.
Regardless of how it was launched there always has to be a choice to be made on how to install. And if user chooses system — the privilege elevation shall be requested right there.
It’s likely will require writing an installer as opposed to using an off the shelf one — but this needs to be done.