Don't know how this happened. When trying to remove a WFE server from one farm, and then join it to another farm, error 1706 popped up during the configuration wizard.

• Sep 05, 2009 The Problem is a missing file in the installation folder of office 2010. Office 2010 has an Setup Controller directory and uses the directory to check the installed components. Please check the.
• Microsoft Office 2010 Free Download and Install Microsoft Office 2010 is a version of the Microsoft Office productivity suite for Microsoft Windows.
• 2013: 'C: Program Files (x86) Common Files Microsoft Shared OFFICE15 Office Setup Controller setup.exe' /uninstall ProductName Answered by: dragosCI This content is currently hidden from public view.

Initially, the errors are:

Depending on the problem that you are experiencing, you may have to view the Setup log file or the Windows Installer log file for the Office installation. Setup log files. The log file for the Setup.exe file is very short because the number of tasks that Setup.exe performs is limited to tasks like the following: Read the Setup.ini file. SETUP.CHM - Download and Fix Errors. Last Updated: Average Article Time to Read: 4.7 minutes SETUP.CHM is considered a type of Compiled HTML Help file. It is most-commonly used in Microsoft Visio Premium 2010 1 developed by Microsoft.It uses the CHM file extension and is considered a CHM (Compiled HTML Help) file. The first release in the Windows XP Operating System for SETUP.

Product: Microsoft SharePoint Portal English Language Pack -- Error 1706. An installation package for the product Microsoft SharePoint Portal English Language Pack cannot be found. Try the installation again using a valid copy of the installation package 'spsmui.msi'.


Product: Microsoft SharePoint Foundation 2010 1033 Lang Pack -- Error 1706. An installation package for the product Microsoft SharePoint Foundation 2010 1033 Lang Pack cannot be found. Try the installation again using a valid copy of the installation package 'wssmui.msi'.


Product: Microsoft SharePoint Portal English Language Pack -- Error 1706. An installation package for the product Microsoft SharePoint Portal English Language Pack cannot be found. Try the installation again using a valid copy of the installation package 'spsmui.msi'.

Setup Controller File For Office 2010

Some article says this is caused by the change of the path of the installation media. Unfortunately, I don't think this is the reason in my case. From the error message, the only thing I know is the configuration wizard could not find the path of 'Language Pack'. So, instead of trouble shooting, I installed those packages manually. There are totally around 10 msi files in 'Language Pack' setup media. Then, the errors below showed up:
Product: Microsoft Office Server Proof (Russian) 2010 -- Error 1706. Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see SETUP.CHM.


Product: Microsoft Office Server Proof (English) 2010 -- Error 1706. Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see C:Users_SPFAR~1AppDataLocalTemp2Setup00001660SETUP.CHM.

Setup Controller File For Office 2010 Keygen

This still looks like caused by 'Language Pack', so I tried to re-install it. Here is the problem: I could not uninstall it. When I tried to uninstall it through 'Programs and Features', no error message, but 'Language Pack' stuck to the program list and didn't want to leave. And the worse thing is, I also could not uninstall SharePoint server.
After hours of struggling, I felt desperate, and was ready to re-install the whole virtual machine. As the last resort, I removed the entry from registry table 'HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstallOffice14.OSMui.en-us', then try to install 'Language Pack' again. BING! It worked!!
The re-installation of 'Language Pack' fixed all issues.
(My environment is SharePoint 2010 SP1 + CU 2011 Aug)

While there are many how-to's that cover silently installing Office using SCCM or script, there are few methods (that worked for me) for uninstalling it.
Using the msiexec command with the correct product code doesn't work from SCCM, since it invokes a user prompt, and SCCM is set to hide prompts.
Below is what worked for me, using PDQ-Inventory to send a remote command. I expect similar results using something like PSexec or similar tools.

4 Steps total

Step 1: Open Notepad and paste the following

Step 2: Save as an XML file

Click 'File' > 'Save as' and change the 'Save as type' from 'Text Documents (*.txt)' to 'All files (*.*)'
Once you have chosen an appropriate temporary location (Desktop works), choose a name that is meaningful to you; add .xml to the end, and click 'Save'
(I chose UninstallSilently.xml)

Step 3: Copy the file to the PC needing uninstall

On a target machine, navigate to the 'C:Program Files (x86)Common FilesMicrosoft SharedOFFICE14Office Setup Controller' folder.
Place a copy of the .xml file you just created there.

Download font cheeky rabbit for samsung. You may need to perform this uninstall on multiple machines, in which case, copying the .XML file would be tedious. In that case, use your mass-deployment tool of choice (I like PDQ-Deploy for this sort of task) and send a command task to your group of machines, {xcopy DeploySilentScript*.xml 'C:Program Files (x86)Common FilesMicrosoft SharedOFFICE14Office Setup Controller' /Y} (Ommitting the curly braces).

Office 2010 Setup File Location

Step 4: Execute the uninstall script

Using PDQ-Inventory, PSexec (from PSTools) or however else you prefer to run scripts remotely, execute the following command:
'C:Program Files (x86)Common FilesMicrosoft SharedOFFICE14Office Setup Controllersetup.exe' /uninstall PROPLUS /config UninstallQuietly.xml

In a few minutes, your target client(s) should have removed Office 2010 completely, without any notifications or nag screens to the user.
I have run this in two labs in the past two days, hitting 52 machines so far, and haven't had a single one need to reboot yet.
That said, if there is the possibility of disrupting a user on the machine, you may decide to run this script, as this method does not include suppression of reboots, if they are necessary.

Setup Of Microsoft Office 2010

4 Comments

• Thai Pepper
  StandingForChildren Nov 23, 2017 at 10:06pm

  Had to use ProPlusWW in command, line but seemed to work well otherwise, thanks

• Datil
  Peter (Action1) Feb 25, 2019 at 04:32am

  Action1 is a free software which can help to uninstall software on multiple computers at the same time. https://www.action1.com/p/Free-Uninstall-Software-Remotely-73.html

• Poblano
  Chad8135 Jun 4, 2020 at 05:39pm

  Thank you for this, I tried so many different ways to get 2010 to uninstall, because OCT with 2016 doesn't properly remove EVERY 2010 asset and there are leftovers which was annoying to me as I wanted 2010 completely gone in place of 2016. One issue I noticed with your guide was in step 3, after 'program files' and before '(x86) there should be a space, (I copy/pasted your step to avoid any typos) and it created an improper folder structure and thus wasn't working at all.

  The way I did it was I used PDQ Deploy with 2 steps, first step was a simply copy file which copied the XML from a network share over to the local computer. The next step was to run the actual uninstall command, again using PDQ Deploy even though you suggested Inventory. It seems more complicated and unintuitive to do that way, at least from what I understand about PDQ. Thank you though, this helped a lot.

• Tabasco
  Gcracker Jun 8, 2020 at 04:10pm

  @Chad8135

  Thanks for the kind words! Barbie sfilata di moda pc download. It's been a while since I wrote this one, but it is exactly what I needed back then, and I couldn't find it all in one place at the time.

  Thanks for letting me know about the typo! I've corrected the section you mentioned, though I wanted to point out that it was only the description of the command that was missing a space. The command in curly braces {} was correct to being with. I still have the original document that I created for this how-to, and I can see it has the space, so I think something may have been lost in on the SW side when they moved the docs into the newer format.
  Cheers!