Please describe what you are doing to trigger the bug:
Create a new job with Wasabi destination in GUI.
In my case I run GUI as admin to create jobs that run in the service.
Using the EU instance of Wasabi.
Please describe what you expect to happen (but doesn’t):
Destination path should use protocol wasabi://
Please describe what actually happens (the wrong behaviour):
Destination path is both in GUI and in .duplicacy/preferences as s3://
I tried to manually change it to wasabi:// - CLI then asked me credentials again on first run and worked without problems. GUI did not work neither before nor after entering credentials in CLI. Most likely because if I understand correctly the credentials when running as admin are stored in registry while CLI stores them in a file
Other details: Win10 x64, latest Duplicacy version (2.1.2)