I am targeting the uninstall registry key for Visio 2000. msiexec /x {0B438E9A-D40F-47B6-95A3-9AD8ED796EA2} /qn . On the test machines, where I recently installed a copy of Visio 2000, the uninstall runs with success. But on the majority of machines, it fails. (The uninstalls are deployed via SCCM). The following verbose log is the output of the failed uninstall.

Can anyone shed any light on why this may be happening?

 

=== Verbose logging started: 06/06/2012  12:31:36  Build type: SHIP UNICODE 3.01.4000.4039  Calling process: C:\WINDOWS\system32\msiexec.exe ===

 

MSI (c) (88:F4) [12:31:36:565]: Resetting cached policy values

 

MSI (c) (88:F4) [12:31:36:565]: Machine policy value 'Debug' is 0

 

MSI (c) (88:F4) [12:31:36:565]: ******* RunEngine:

 

           ******* Product: {0B438E9A-D40F-47B6-95A3-9AD8ED796EA2}

 

           ******* Action:

 

           ******* CommandLine: **********

 

MSI (c) (88:F4) [12:31:36:565]: Client-side and UI is none or basic: Running entire install on the server.

 

MSI (c) (88:F4) [12:31:36:565]: Grabbed execution mutex.

 

MSI (c) (88:F4) [12:31:36:627]: Cloaking enabled.

 

MSI (c) (88:F4) [12:31:36:627]: Attempting to enable all disabled priveleges before calling Install on Server

 

MSI (c) (88:F4) [12:31:36:627]: Incrementing counter to disable shutdown. Counter after increment: 0

 

MSI (s) (08:50) [12:31:36:643]: Grabbed execution mutex.

 

MSI (s) (08:A0) [12:31:36:643]: Resetting cached policy values

 

MSI (s) (08:A0) [12:31:36:643]: Machine policy value 'Debug' is 0

 

MSI (s) (08:A0) [12:31:36:643]: ******* RunEngine:

 

           ******* Product: {0B438E9A-D40F-47B6-95A3-9AD8ED796EA2}

 

           ******* Action:

 

           ******* CommandLine: **********

 

MSI (s) (08:A0) [12:31:36:643]: Machine policy value 'DisableUserInstalls' is 0

 

MSI (s) (08:A0) [12:31:36:643]: MainEngineThread is returning 1605

 

MSI (c) (88:F4) [12:31:36:643]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

 

MSI (c) (88:F4) [12:31:36:643]: MainEngineThread is returning 1605

 

=== Verbose logging stopped: 06/06/2012  12:31:36 ===

 

 

Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1

In theory this is a disk space issue based on the 1605 error, but anecdotal evidence on the internet says this most often occurs when the program is installed as a user-specific installation rather than machine specific, and you are trying to uninstall as a different user than the original installation used.  My bet would be that the machines the uninstall is working on were installed per machine, or by SCCM.

You may be able to run a repair install as administrator and then try the uninstall again, or try a complete reinstall as administrator before uninstalling.  If you know what user was originally used to uninstall and they still exist, you can try running the uninstall as that user.

Answered 06/06/2012 by: philologist
Red Belt

  • More information on the ALLUSERS property: http://msdn.microsoft.com/en-us/library/windows/desktop/aa367559(v=vs.85).aspx
Please log in to comment
Answer this question or Comment on this question for clarity