https://bugs.winehq.org/show_bug.cgi?id=41269
--- Comment #31 from Reinhold reinhold.hoffmann@hotmail.com --- Thanks. This is a common issue like the one from Hans here in Comment 19 to 21.
In Hans' case the CustomAction has blocked installations from network drives (where we often have issues therefore we have blocked that). In that case the "Add/Remove" showed as if the app was properly installed. In order to proceed with a next installation the "faulty" needs to be manually uninstalled with "wine uninstaller".
We had many cases where customers were totally confused and we had fix that in remote sessions jointly with customers. That is very service intensive.
May be it is a new bug. I am glad you got it.