Comment 3 for bug 1552373

No, i am talking about different versions. Every installer of every revision me or Appveyor build contains the same AppID.
So you can only one build at each time on your system.

The last change to installer logic was rev 7721: Widelands does now not require any administrator privileges when installing.
So maybe a problem if you have installed a version <7721 with administrative privileges into a directory which requires admin privs?
And now using a current installer without admin privs? (It won't request admin privs, "run as admin" if desired)

If you download and install Build-18 and then take any installer which was build later up to today: Each should detect the last installed folder and only allow install there if Widelands is already installed.

Because the "normal" user does not want to install different versions of Widelands in parallel, i won't change the scripts (my personal and appveyor ones) to generate unique AppIDs to allow this.

The release (candidates ) of Build-19 will get unique AppIDs.

Setting to won't fix.