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).
* Extraction of Files * Installation of Product * Validation of Product * Activation of Product * Applications in Suite start. * Typical Installation Only. * Restarting installation after (purposeful) hard failure. (CTRL-C of terminal window)
What does not
* Installation Icons There was one glitch during installation with MSCORSVW.EXE (a .net piece) generating an error. Clicking "Close" on the generated error dialog continues the installation and did not seem to adversely affect the install, though it might affect applications after the fact. It's worth examining.
What was not tested
* The ISO installation.
* The trial installation.
* Custom Installation.
My installation was based on the most recent downloadable Microsoft Office 2010 Professional Plus x86 from MSDN, using a valid MSDN license. Since this entry is about the INSTALLER only, I would choose a gold for this, unfortunately there was one glitch during installation with MSCORSVW.EXE (a .net piece) generating an error. This did not seem to adversely affect anything. Following Neil Andersons instructions: > export WINEPREFIX=$HOME/.wine-office10/ > winetricks dotnet20 msxml6 corefonts > winecfg msxml6 --> Native * Note, this works in Native, Builtin as well. I saw no difference on two separate installs. > wine en_office_professional_plus_2010_x86_515486.exe Install > winecfg riched --> Native gdiplus --> Native * These were added for post-installation, they resolve some display errors. Response on these will be kept top particular applications.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||FreeBSD 13.0-RELEASE||May 16 2021||5.0.5||Yes||Yes||No||Silver||Michael Ziehm|
|Show||Ubuntu 20.04 "Focal" (+ variants like Kubuntu)||May 11 2021||6.1||Yes||Yes||Yes||Gold||C. Leu|
|Show||Pop!_OS 20.04 LTS||Aug 30 2020||5.16||Yes||Yes||No||Silver||Parrottos|
|Show||Arch Linux x86_64||Aug 04 2020||5.14||Yes||Yes||Yes||Gold||Ky Nguyen|
|Show||Slackware64 -current||Jul 21 2020||5.0.1||Yes||Yes||No||Platinum||anonymous|
|Bug #||Description||Status||Resolution||Other apps affected|
|30033||Office 2010 Standard, Pro Plus: Volume activation fails||NEW||View|
|39810||Office 2007/2010/2013/2016 uninstallation fails||NEW||View|
|45208||Microsoft Office 2010 installer crashes at around 50 % mark||REOPENED||View|
|47537||Microsoft Application Virtualization Client installer (click2run.msi) for Office 2010 Starter fails||UNCONFIRMED||View|
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.