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).
I have installed the regular Office 2010 Home & Student (incl. SP1) version in a 64 bit Wine 6.0 prefix under Kubuntu 20.04 LTS.
The installation through the regular Microsoft Office 2010 installer went almost perfectly. No error was found.
With the bellow mentioned workarounds also all Office programs are working correctly, this is true for Word 2010, Excel 2010 and PowerPoint 2010.
What does not
The Office applications are needing some workarounds to function properly.
Some winetricks tweaks are still needed to get the Office 2010 programs working. (Note, it is strongly recommended to use the latest winetricks from the winetricks website, not that one of the repo.)
I followed more or less the recommendations by user Henrique de Sousa in the comments section. My exact steps were:
WINEARCH=win64 WINEPREFIX=~/.wine winecfg
Before the installation:
winetricks -q mfc100
winetricks -q msxml6
After the successful installation:
winetricks -q riched20
winetricks -q gdiplus
Note, there may exist at the first startup some problems with the graphics and maybe also a black window. In such cases the Office 2013 black window fix can be applied, open regedit through winetricks and go into the tree HKCU\Software\Wine\.
Generate a new key with the name Direct3D and add a dword with name MaxVersionGL. Define the value with 30002 (hexa). The full value will be 0x00030002 (196610).
Try to start Word or Excel. If there is still a problem with the display then try to change in winecfg the order at *gdiplus to Builtin, Native. After this I was able to start Word and Excel and finish the basic Office config settings. However, when I try to open a PowerPoint file, the screen was again corrupted. So I changed it again back to Native, Builtin. Since this last switch everything is working great, in any of these three programs.
Final note, I was also able to install flawless the latest Office 2010 service pack 2, SP2.
What was not tested
everything was tested
During the Office setup, I excluded the .NET plugins of all office apps, the hosted webs support, and the Office Download links. I have also manually upgraded the Wine Mono package to version 6.1.2. This seems to work fine with Office 2010, and it looks better then the original Microsoft one. So do not use in newer wine versions the winetricks dotnet20 argument.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Fedora 35 x86_64||Dec 17 2021||7.0-rc1-staging||Yes||Yes||Yes||Gold||Discover|
|Show||Ubuntu 21.04 "Hirsute" (+ variants like Kubuntu)||Oct 12 2021||6.0.1||Yes||Yes||Yes||Gold||C. Leu|
|Show||FreeBSD 13.0-RELEASE||May 16 2021||5.0.5||Yes||Yes||No||Silver||Michael Ziehm|
|Current||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|
|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.