Uninstaller leaves behind services, scheduled tasks, and firewall rules without prompting

[yoshen78-png]

I confirm that

• I have searched for an existing feature request matching the description.

Feature Description

I recently evaluated AMP and ultimately decided it wasn't the right fit for my setup, so I uninstalled it. During the cleanup process, I noticed that several Windows components were left behind after the uninstall completed.

Specifically, I found:

A registered Windows service (AMP-ADS01)
A scheduled task (\CubeCoders\AMP Pending Tasks)
Multiple Windows Firewall rules (AMP Instances)
The C:\AMPDatastore directory containing the instance data

The Windows service was especially surprising because it remained registered even after the application itself had been removed. The web service was still running and set to delayed auto start which needed to be manually removed.

I understand there are valid reasons to preserve instance data and configuration for users who intend to reinstall AMP later. However, I think the uninstall experience could be improved by giving users an explicit choice.

For example:

☑ Remove Windows services
☑ Remove scheduled tasks
☑ Remove Windows Firewall rules
☑ Remove AMP datastore/configuration
☐ Keep server instances and configuration for future reinstall

Alternatively, if the current behavior is intentional, mentioning it during uninstall (or in the documentation) would help set expectations.

I don't consider this a security issue, but from a Windows administrator's perspective it feels like the uninstall is incomplete because several system-level objects remain and require manual cleanup.

Overall I thought AMP was well put together—I just wanted to offer some feedback that I think would make the uninstall experience feel much cleaner for users.

[BroOtti]

Looks like you didn't read the docu: https://discourse.cubecoders.com/t/how-to-uninstall-amp/2273

[yoshen78-png]

Looks like you didn't read the docu: https://discourse.cubecoders.com/t/how-to-uninstall-amp/2273

I realize AMP expects users to delete their instances from within the Instance Manager before uninstalling. That makes sense.

However, I think many Windows users (myself included) will naturally uninstall AMP through Add/Remove Programs without first consulting the documentation. In that scenario, Windows is left with services, scheduled tasks, firewall rules, and the datastore still present.

In my case, the remaining service was configured for delayed automatic start and later bound to port 8080, which conflicted with another service I wanted to use on that port.

I think the uninstall experience could be improved by either:

Detecting existing instances and prompting the user to remove them first.
Launching the Instance Manager automatically before uninstall.
Or displaying a message that explains exactly what will remain if the user proceeds with a standard Windows uninstall.