Windows Installer - Upgrade path

Hello, I use couchdb and currently on version 3.5 on Windows 11 clients. I've recently upgraded from couch 1.6 to 2.3 and then to 3.5. I've noticed that in every upgrade the installer is not allowed to run on top of the current versions. It always gives an error saying another version is installed already. The process I follow is to uninstall, save data folder and reuse it after the installation of the new versions. This didn't work on the jump from 1.6 to 2.3, it did on the jump from 2.3 to 3.5.

Now that 3.5.2 is out, I'd like to patch my clients and install the latest version, however the installer is giving the same message. Is this a broken behavior from the installer that could be fixed or any particular reason why is designed like this?

Doing the process to uninstall/ install the new version is not hard for just 1 client but gets complicate with remote clients and in scaled scenarios with dozens or hundreds of clients.

Thank you

No file or test is named in the report. Reproduce the Windows 3.5.2 upgrade attempt, then trace the installer entry point that rejects an existing installation; done means an in-place upgrade is accepted without requiring uninstalling and restoring the data folder, or the behavior is documented as intentional.

Written by the indexing model from the issue text.