Hello,
The installer for our product contains a custom action (RemoveReadOnlyAttribute.CA.dll) to remove a read only attribute from a desktop shortcut during uninstall. The problem is that on some computers, the custom action can't be run because it was built by a runtime newer than the one available during the uninstall (and so the uninstall is aborted). This prevents me from uninstalling or upgrading our software. Even if I remove the custom action from a new installer, it's the old one that is run to remove the previous version.
Although I wan't to fix the root cause of my problem (the custom action), a more pressing problem is how to upgrade the version of our software on a customer's computer that is experiencing this problem. I am a little limited due to not being able to reproduce the problem on my computer (not that I really want to without knowing how to fix it!).
I have seen the forum post http://www.advancedinstaller.com/forums ... f=2&t=4959, which upgrades the installation using a new installer (same product code) with the msiexec options REINSTALL=ALL REINSTALLMODE=vomus". Unfortunately, running the installer with these options results in the installer running for a bit then aborting with the error "the specified account already exists".
I have also seen programs like Microsoft's "Fix problems that programs cannot be installed or uninstalled ", and third party software like Repo Uninstaller. But I'm not keen to recommend them to my customer without having seen it run and fix the problem.
Is there way to get this uninstalled? Can I somehow replace the cached uninstaller that windows has kept from the install? I've seen the C:\Windows\Installers directory, but I'm worried if I start messing there I'll only make things worse.
My software is a Java JAR packaged as an exe, and installs a couple of executables and a windows service. It was built using AI 11.7 and I'm currently using 12.0. I don't know what version of windows the customer has installed our software on, but the install log shows "SFXCA: Binding to CLR version v2.0.50727" (just before failing to load the custom action). I'm guessing our custom action is built for .NET 4.
Thanks, Ross
FOLLOW US
Get the latest news in Application Packaging