Users cannot uninstall and reinstall to make the add-on available again because their configuration is corrupted

[cary-rowen]

Steps to reproduce:

1. Install NVDA-2023.2;
2. Install an add-on whose API version should be less than 2024.1.0, that is, compatible with 2023.2.
3. Install the NVDA-alpha version (API version is 2024.1.0).
4. Check the add-on status in the add-on store: Add-on installed in stap2 is disabled.
5. Uninstall the NVDA Alpha version through the NVDA uninstaller in the control panel.
6. Restart your computer and install NVDA-2023.2
7. Check the add-on status in the add-on store.

Actual behavior:

Perform step 7: You will find that the status of the add-on is the same as step 4, that is, it is still disabled.

Expected behavior:

Add-on should be enabled.

When I tested using NVDA-2022.1 and NVDA2023.1, it performed as expected. So this could also be considered a regression.

Alternatives I Considered:

1. When uninstalling NVDA, it ask to delete the user configuration.
2. Ask user to delete legacy user configuration or reset add-on status when installing NVDA.

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

NVDA-Alpha Version

Windows version:

Windows 10 22H2 (AMD64) build 19045.3393

Name and version of other software in use when reproducing the issue:

None

Other information about your system:

None

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

When I tested using NVDA-2022.1 and NVDA2023.1, it performed as expected. So this could also be considered a regression.

If NVDA add-ons are disabled, is your problem still occurring?

n/a

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

n/a

[wmhn1872265132]

I'd love to have this bug fixed for the following reasons:

1. As mentioned above, previous versions of NVDA do not have this error;
2. For testers, this behavior is too unfriendly. Many users may use the command line to share a set of configurations for multiple versions of NVDA;

Thanks

[seanbudd]

Note this is a duplicate of #15412

[Adriani90]

Yeah NVDA should really at least ask if an uninstall should also remove user configuration or not. This is also requested in an older issue which I cannot find right now.