Retail release June 15, 2010
This entry is just for testing the installer of Microsoft Office 2010 (aka Office 14) office suite.
Reports on specific programs included in Office 2010 should be submitted to their respective AppDB entries.
Office 2010 is available in 7 editions and 4 different licenses:
When reporting test results, please follow the Guidelines for Submitting Test Reports below (scroll down to notes section).
Installation (both standard and customised) until 2/3
then it hang for a long time: there are 2 options:
-we kill the installer, so we are able to run winword.exe which display a pretty splash screen and then an error message to say that the microsoft office 2010 is broken, not activated, and corrupted (incomplete installation)
In fact it will never work because as it begin to hang up, it notice update will fail so it already began to delete files to cancel installation
- we wait until the installer say there is an error, and every files are deleted: no winword.exe.
there is no difference between the last set up and X16-32007.exe
What does not
Every programs since as the installation is finished it is automatically try to update, and 0.000001 second later, it fail to find update and begin to cancel installation.
it was impossible to kill the installer at the good time.
What was not tested
Office Pro 2010 Trial
|Fedora 35 x86_64
|Dec 17 2021
|Ubuntu 21.04 "Hirsute" (+ variants like Kubuntu)
|Oct 12 2021
|May 16 2021
|Ubuntu 20.04 "Focal" (+ variants like Kubuntu)
|May 11 2021
|Pop!_OS 20.04 LTS
|Aug 30 2020
|Other apps affected
|Office 2010 Standard, Pro Plus: Volume activation fails
|Office 2007/2010/2013/2016 uninstallation fails
|Microsoft Office 2010 installer crashes at around 50 % mark
|Microsoft Application Virtualization Client installer (click2run.msi) for Office 2010 Starter fails
|Office 2010 & 2016 installers crash
Test reports that do not follow these guidelines will be rejected. Â
These instructions assume you are familiar with the basics of using Wine and Linux, including running apps from the command line. If you are new to Wine and/or Linux, before proceeding further please familiarize yourself with the information in the FAQ, particularly the sections on creating a 32 bit wineprefix, running an installer, and using wineprefixes.
After installing, set riched20 to native, builtin in winecfg to enable Powerpoint to start and selection boxes to display correctly.
Office Professional Plus does not require .NET to be installed, but if it detects that it is installed, it will look for a machine.config file. This will fail on Wine versions without wine-mono installed (i.e., versions prior to 1.5.6).
The recommended solution is to install wine-mono. The instructions below are provided solely for those who are unable to upgrade to a version of Wine supporting wine-mono.
There are two ways to work around this without installing wine-mono:
Installing winetricks dotnet20 will also work around the bug; however, because that will install native dlls that may cause other problems, it is not recommended.
The above workarounds must be done before running the installer. If you do not, and the installer fails, you must delete that wineprefix and start fresh, as the rollback process leaves behind something that prevents subsequent attempts from succeeding, even with one of the workarounds applied. Note also that a rolled-back install leaves running processes that must be killed manually.
There are known regressions affecting the Office 2010 installer in the versions of Wine listed below. Do not attempt to install in them.
In addition, Office 2010 is not installable in any version prior to 1.3.9; this includes all 1.2.x versions.
1) Copy the CD content to a folder on your computer
2) Find the folder named "Standard.WW" (or ProPlus.WW or whatever your version name)
3) Inside that folder should be a file named config.xml.
4) Edit config.xml and make sure that it has the following:
Configuration Product="Standard" (or ProPlus)
PIDKEY Value="XXXXXXXXXXXXXXXXXXXXXXXXX" (use your actual serial key here)
Setting Id="AUTO_ACTIVATE" Value="1"
Each of the above lines in the config.xml file should be between angled brackets, which unfortunately can't be shown here because the AppDB will not display anything between angled brackets. If you are unsure how it should look, see bug 30033 for an example with the brackets.
5) Save the config.xml file and run the installer..
Test reports that do not follow these guidelines will be rejected.