This installer has the /quiet option according to /?, but when you use it, it does not work.

So then i extracted the contents, copied the \Admin folder from the full Office 2010 install disk to the extracted folder, so that i could use the setup /admin, which worked.

I customised the installation to make it both silent, and with no completion message (I SAID NOT COMPLETION MESSAGE). Saved the msp.

Then i run setup, if obviously uses the MSP file the cusomisation tool generates, because it doesnt prompt for any info/EULA acceptance etc. but its not silent AND DISPLAYS A STUPID COMPLETION MESSAGE AT THE END prompting the user to go to M$ online.

So lets get this right, the largest software company in the world has released an installer which is NOT deployable by any system admin tools, because they will all time out and report the installation as failed, well done M$ you complete bunch of tools.

Can anyone offer any assistance with this? Is there a way to create a custom xml that forces the installation to be silent?

Any assistance much appreciated.
1 Comment   [ - ] Hide Comment


  • @MCompton69 did you ever find a way to NOT show the "Welcome to Microsoft Office 2010" "Help Protect and Improve Microsoft Office" with 3 choices:
    1) Use Recommended Settings
    2) Install Updates Only
    3) Don't Make Changes

    I do not want my users to have to see this and have to make a selection.
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.
Answer this question or Comment on this question for clarity


Why not find the dialog (or, the CA, if the dialog is triggered by a CA) and disable it?
Answered 07/21/2010 by: VBScab
Red Belt

Please log in to comment
I am surprised that VBScab did not suggest that you generate a verbose log of your MSI install and find the reason for the final dialog that way.  If you do a logged manual install of this runtime, and then wait for, say, 60 seconds before OK'ing the final dialog, the logfile, which has a time log of all actions, will show a 60 second delay after the offending action is called, before the action terminates.  In over 20 years of packaging, I have yet to find a Microsoft app that cannot be packaged silently.
Answered 01/15/2015 by: EdT
Red Belt

Please log in to comment