Fixed with rG4c830b240c for gpd5 but after the release. Will fix it for 2.4 too.

Also fixed for 2.4. Don't use the uninstaller on the command line, you should use the Windows method to do this.

Just to explain, if you are executing it from the command line the command line will "lock" the uninstaller until it is finished. In GUI Mode it creates a copy in %TEMP% launches this copy and exits. When run from the command line it requires a session reset to delete the unistaller. So log out / log in and the uninstaller should be removed, but the dir might still exist. I am not sure. To workaround you need to copy the uninstaller to a temporary locationm firs and then execute and delete the copy.

In T7452#195836, @aheinecke wrote:

To workaround you need to copy the uninstaller to a temporary locationm firs and then execute and delete the copy.

thanks for explaining what is happening and why, working with a temporary copy did the trick.

this could also help with T5952, i was testing with ansible as well.

In T7452#195841, @m.eik wrote:

this could also help with T5952, i was testing with ansible as well.

I doubt it as what Gpg4win does here is completely standard. So the win_package module should handle it or there would be multiple results if you search for "NSIS uninstall ansible"