I have a WIndows XP machine that I am unable to uninstall a security client (CA eTrust), to the point where I followed a manual uninstall guide from CA which has not worked.

THe entry no longer exists in ARP, and I can not install a new security client as eTrust is detected as installed.

ANy help?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
http://msdn.microsoft.com/en-us/library/aa370523(v=vs.85).aspx
Answered 04/14/2011 by: GrGrGr
Orange Belt

Please log in to comment
0
MSIZap will remove the installation data from the registry but I don't think that that really helps the OP.

@OP, I presume that the manual uninstall has removed only the product's files and registry data and not its installation data?

Use ProcMon to determine how the installer is detecting its installed state, then simply rename the relevant file/registry entry. The installer will now believe that the product isn't present. Now, you can either re-install the old version (to assist in diagnosing why the uninstall failed, something I'd certainly want to know) or go ahead and install the new.
Answered 04/14/2011 by: VBScab
Red Belt

Please log in to comment
0
VBScab, valid point. If the installer has custom logic to read a specific registry entry/file the msizap tool will not help.

If the installer file is an .msi, the OP can also try to make a detailed log (/l*vx) and see which condition is failing or what custom action is causing it and investigate further.

If the installer is not an .msi - procmon is definitely the way to go.
Answered 04/14/2011 by: GrGrGr
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity