Uninstall scripts say they ran successfully but software is not uninstalled
I used the Uninstaller Configuration Policy to create scripts to remove a few different versions of some software that we no longer use in our environment. Testing on a few machines worked fine but I have a few computers left for each version where the script runs and says it completed successfully, but the software is not being uninstalled. I've included s screenshot of the script as created by KACE. I also modified the script to just launch the msiexec program without the 'verify' and 'set' steps. Either way I got the same results, it appears to run successfully but the software does not get uninstalled.
I looked through some log files on one of the computers but could not find anything that stood out to explain the failure.
Any ideas on what I'm missing here?
Answers (2)
If you can, post the script log.
Try changing the launch step with $(KACE_SYS_DIR) instead of 'SYS'
Comments:
-
Which script log are you referring to? The 'pskill.vbs' that was auto-created when the uninstall script was created, or one from a computer that it has been run on?
I'll try the change you suggested and see if that helps.
Update: Changing SYS to $(KACE_SYS_DIR) did not make any difference in the results when the script was run. - ScottAday 2 years ago-
The log in scripts > Run Now Status - IgorAngelini 2 years ago
-
Output Log
Running as SYSTEM
Checking if registry 'HKEY_LOCAL_MACHINE\SOFTWARE\Kace\KBot Configuration\Uninstall0' value 'key' is equal to '1978856733' succeeded
Activity Log
verify - registry_value_is
Checking if registry 'HKEY_LOCAL_MACHINE\SOFTWARE\Kace\KBot Configuration\Uninstall0' value 'key' is equal to '1978856733'
verify - on_verify_success
verify - on_verify_failure
Debug Log
Running kbot: runkbot 468 1643139204
KBotScript::LogScriptInfo - Start
id=468 name=Uninstall Netskope Client (91.0.6.812) version=1643139203 type=policy
execute disconnected=true logged_off=true
execute events
KBotScript::LogScriptInfo - Finish
KBotScript::LogScriptInfo - Start
id=468 name=Uninstall Netskope Client (91.0.6.812) version=1643139203 type=policy
execute disconnected=true logged_off=true
execute events
KBotScript::LogScriptInfo - Finish
KBotScriptManager::CleanupDependencies - clean up dependencies in kbot directory C:\ProgramData\Quest\KACE\kbots_cache\\packages\kbots\468\
CleanupDependencies: file pskill.vbs is part of the dependency list, keep the file - ScottAday 2 years ago -
In this particular log, it failed because the registry key was set ("[...] value 'key' is equal to '1978856733' succeeded"). Try removing the "Verify" step, move the msiexec command to "On Success" and send the log again. - IgorAngelini 2 years ago
-
The last change you recommended did make a difference. It ran successfully on a number of machines and failed on a couple. Here is the log from one on which it failed.
Output Log
Running as SYSTEM
A
Creating process returned non-zero: C:\WINDOWS\System32\msiexec.exe /qn /x{C869737E-0563-49A8-B255-5C7C1F1C6A2B}: (0) The operation completed successfully.
Error Code: 0
Status Code: 1618
Activity Log
verify - on_verify_success
verify - on_verify_failure
verify - launch_program
Launching program: 'C:\WINDOWS\System32\msiexec.exe' '/qn /x{C869737E-0563-49A8-B255-5C7C1F1C6A2B}' wait='true'
Debug Log
Running kbot: runkbot 473 1643204232
KBotScript::LogScriptInfo - Start
id=473 name=Copy of Uninstall Netskope Client (91.0.6.812) version=1643204230 type=policy
execute disconnected=true logged_off=true
execute events
KBotScript::LogScriptInfo - Finish
KBotScript::LogScriptInfo - Start
id=473 name=Copy of Uninstall Netskope Client (91.0.6.812) version=1643204230 type=policy
execute disconnected=true logged_off=true
execute events
KBotScript::LogScriptInfo - Finish
KBotScriptManager::CleanupDependencies - clean up dependencies in kbot directory C:\ProgramData\Quest\KACE\kbots_cache\\packages\kbots\473\
CleanupDependencies: file pskill.vbs is part of the dependency list, keep the file
runkbot ----- launching [path='C:\WINDOWS\System32' program='msiexec.exe' parms='/qn /x{C869737E-0563-49A8-B255-5C7C1F1C6A2B}' wait='true'] ----- - ScottAday 2 years ago-
Msiexec returned error 1618 which means it already running, maybe waiting for a restart, here are some references to help you troubleshoot the issue, try contacting the user of one of these failed machines and ask them to restart the system, then try running it again.
https://help.pdq.com/hc/en-us/articles/220530907-MSI-Installation-Already-In-Progress-Error-1618
https://docs.microsoft.com/en-us/windows/win32/msi/error-codes - IgorAngelini 2 years ago-
OK, thanks for the help with this! - ScottAday 2 years ago
-
Glad I could help :) - IgorAngelini 2 years ago
Try changing the launch step with $(KACE_SYS_DIR) instead of 'SYS'
the registry key was set ("[...] value 'key' is equal to '1978856733' succeeded"). Try removing the "Verify" step, move the msiexec command to "On Success"