/build/static/layout/Breadcrumb_cap_w.png

Problems uninstalling Office 2007

Evening,

We are having issues with uninstalling office 2007 using the following command

c:\acp\setup.exe /uninstall proplus /config c:\acp\proplus.ww\config.xml

where in the config file its set to silent and reboot = never

My problem is that it restarts the machine after the install finishes.

Bit of backgroud info:

We have a core installation for office (Word, Excel, Outlook and Powerpoint) which is installed using a custom msp and the config file from the proplus folder. we have then also packaged up access and publisher as seperate packages. everything installs fine as we push all the installation files to the clients and run the command remotely.

when running the uninstall as above it uses the config to make it silent but looking at the log file it says theres a file locked and windows installer requires a reboot

has anyone else seen this before??

0 Comments   [ + ] Show comments

Answers (2)

Posted by: anonymous_9363 15 years ago
Red Belt
0
ORIGINAL: mdlister
when running the uninstall as above it uses the config to make it silent but looking at the log file it says theres a file locked and windows installer requires a reboot?
So all that needs to happen is for you to use your favourite process/file/registry monitor to determine what process is holding the file open. Then, add a mechanism to stop/kill that process when an uninstall is taking place. It's probably one of Microsoft's "Let's run this tool just in case the user wants to do that thing he does once every four years" processes.
Posted by: mdlister 15 years ago
Senior Yellow Belt
0
Sorry was at home when posting this so i couldnt get the exact message, the file it has looks to be the actual uninstaller?

FILESINUSE: One or more (windowless) processes are holding filse in use.
FILESINUSE: No files have been reported in use, yet a reboot is requested from windows installer. Reboot will be required.
FILESINUSE: Scheduling reboot operation: Deleting file c:\config.msi\40374.rbg. Must reboot to complete operation.

then at the end of the log it exits on a return code: 1641
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ