WineHQ

Microsoft Office (installer only)

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:

  • Starter (OEM)
  • Home & Student (Retail)
  • Standard (Retail or volume)
  • Home & Business (Retail)
  • Professional (Retail)
  • Professional Academic (Academic)
  • Professional Plus (Retail or volume)

When reporting test results, please follow the Guidelines for Submitting Test Reports below (scroll down to notes section).

Application Details:

Version: 2010 (32 bit)
License: Retail
URL: http://www.office.com
Votes: Marked as obsolete
Latest Rating: Bronze
Latest Wine Version Tested: 9.12

Maintainers: About Maintainership

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

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.

Workarounds

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

Hardware tested

Graphics:

  • GPU: AMD
  • Driver: open source

Additional Comments

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.

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
ShowUbuntu 22.04 "Jammy" (+ variants like Kubuntu)Jul 03 20249.12Yes Yes YesBronzeRodri 
ShowUbuntu 24.04 "Noble" (+ variants like Kubuntu)May 31 20249.9Yes Yes YesSilverLe 
ShowFedora 35 x86_64Dec 17 20217.0-rc1-stagingYes Yes YesGoldDiscover 
ShowUbuntu 21.04 "Hirsute" (+ variants like Kubuntu)Oct 12 20216.0.1Yes Yes YesGoldC. Leu 
ShowFreeBSD 13May 16 20215.0.5Yes Yes NoSilverMichael Ziehm 

Known Bugs

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
55325 Office 2010 & 2016 installers crash NEEDINFO View

Show all bugs

HowTo / Notes

Guidelines for submitting test reports
  1. Test in a clean wineprefix, using plain Wine. 
  2. Specify exactly which edition of Office 2010 you tested (Standard, Pro, etc.). This is crucial--bugs that affect one edition may not affect others.
  3. Specify exactly what type of ­install you tested (Typical, Custom, Minimal, etc.)
  4. Limit your report to the installer only. Reports on the performance of individual apps should be filed under their respective AppDB entries. Problems with running any of the apps should only be mentioned if it is clear that it is due to a problem with the installer.
  5. If you used any overrides during the install, please list them and explain exactly what problem each override was needed to solve.
  6. Test reports that do not follow these guidelines will be rejected. ­

­­
HOWTO

­(2017-04-10)

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.

  1. Make sure all dependencies of Wine are installed on your system, including wine-mono and winbind.
  2. If installing a volume-licensed copy of Office 2010 that requires MAK activation, please read the note below for the workaround for bug 30033
  3. Create a clean 32 bit wineprefix for Office 2010 (use WINEARCH=win32 if on a 64 bit system).
  4. For Wine 2.2 and later, set the Windows version to XP. (For older versions, the default was XP, and should not be changed.)
  5. Install Office 2010 to the newly-created wineprefix simply by running the installer. 

After installing, set riched20 to native, builtin in winecfg to enable Powerpoint to start and selection boxes to display correctly.

  • Do not use winetricks; Office installs its own riched20 to a private directory.
  • This override may be set globally if Office is installed to a separate wineprefix (recommended).
  • If other applications are installed to the wineprefix (strongly discouraged), either set the override individually for each Office application, or set riched20 to builtin individually for the non-Office applications, as non-Office applications will not be able to find the riched20 installed by Office.
HOWTO: Office Professional Plus Workarounds for Wine versions without wine-mono

 (2012-06-04)

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:

  1. Copy a machine.config file from a native Mono install to the wineprefix's drive_c/windows/Microsoft.NET/Framework/v2.0.50727/CONFIG directory. 
  2. Delete all .NET-related registry keys.

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. 

Known regressions

(2018-01-07)

There are known regressions affecting the Office 2010 installer in the versions of Wine listed below. Do not attempt to install in them.

  • 2.18--3.0-rc4 (bug 44036)
  • 1.5.18
  • 1.3.30

In addition, Office 2010 is not installable in any version prior to 1.3.9; this includes all 1.2.x versions.

Workaround for bug 30033 (MAK activation)

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" 

/Configuration

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..

Guidelines for Submitting Test Reports

 

  1. Test in a clean wineprefix, using plain Wine. 
  2. Specify exactly which edition of Office you tested (Standard, Pro, etc.). This is crucial--bugs that affect one edition may not affect others.
  3. Specify exactly what type of install you tested (Typical, Custom, Minimal, etc.)
  4. Limit your report to the installer only. Reports on the performance of individual apps should be filed under their respective AppDB entries. Problems with running any of the apps should only be mentioned if it is clear that it is due to a problem with the installer.
  5. If you used any overrides during the install, please list them and explain exactly what problem each override was needed to solve.
  6. Test reports that do not follow these guidelines will be rejected.

Comments

The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

license activation requires winbind
by James Campbell on Friday May 13th 2022, 5:54
I copied a prefix holding office 2010 from a previous distro to a new ubuntu 22.04 machine. I was having issues with my license activation not working. Turns out the culprit was a missing windbind (which is part of samba?). On Ubuntu 22.04, the fix is just running `sudo apt install winbind`.
Ubuntu 20.04
by Henrique de Sousa on Friday January 29th 2021, 16:56
I tried several times installing Office 2010 and followed the steps on the mentioned thread, but there is one step that breaks the execution:

If you add and change gdiplus to "Native (windows)" I'm getting "IOPL not enabled", so I skipped that and only enabled riched20 on step 4:


2. Choose "Select the default wineprefix" then "Install a windows DLL or component" and from there install the dotnet20 and msxml6, following the instructions.
Again from "Select the default wineprefix" choose "install a font" and select the corefonts.

From winetricks and "Select the default wineprefix" choose run "winecfg". From there go to tab "Libraries" and click on *msxml6 then "Edit" and choose "Native (windows)".

3. Run the MS Office 2010 Professional x86 installer you have.

4. On winecfg as instructed above to the tab "Libraries" and from "new override for library" click the small arrow and choose to "Add" riched20 and gdiplus. Then click on both, "Edit" and as above change their override to "Native (windows)".

Everything works perfectly on a wine-staging-6.0 and 32bit prefix.
RE: Ubuntu 20.04
by Andy on Sunday August 15th 2021, 15:10
Hi. Can you give complete instructions for installing MSOffice2010?
RE: Ubuntu 20.04
by C. Leu on Monday August 16th 2021, 3:07
You should be really able to install one of the "normal" Office 2010 versions under (K)Ubuntu 20.04 when you are following the steps in my Office 2010 AppDB: appdb.winehq.org/objectManager.php?sClass=version&iId=17336&iTestingId=110520

As mentioned, the install worked mostly really good. In some cases there is just a small registry edit needed. (Most likely this is a graphics driver related thing.) Otherwise the overall operation of Office 2010 (32bit) in newer (64bit) Wine 6.x versions seems to be absolutely great.
Office 2010 installations on Debian 8 in 2016
by 0xc004f012 on Saturday September 3rd 2016, 5:10
I've recently installed mso 10 student on Debian 8 32 bit, here are my notes for others:

Office 2010's software protection(licence checker) needs winbind to run. Wine issues a warning for this saying ntlmauth is required, and it's in the distro's winbind package.

Winbind pulls in samba. So on debian, this activates an active directory(samba server) and netbios logon server.

Turns out these processes are nmbd(netbios server) and smbd(samba domain server).

I can stop and disable these processes and office excel, word, powerpoint and onenote will keep working.

You can disable the extra services that come with samba on systemd:

systemctl disable smbd nmbd samba-ad-dc winbind

systemctl stop smbd nmbd samba-ad-dc winbind

With sysv, replace it with:

service servicename disable and service servicename stop

I've used the following link as a baseline guide:

ubuntuforums.org/showthread.php?t=1885051

I've used wine 1.8.x from debian 8 backports instead.

Also this may be of interest for activation:

support.office.com/en-us/article/Activate-Office-2010-1fe7340c-50e2-458f-8677-f57f5a140f46

These are my notes:

What was needed:

* Wine 1.8 backports got activation working, 1.6 bitched about network errors
* Winbind to be installed
* Winetricks to install dotnet2, corefonts
* So for winetricks the code is: apt-get install winetricks -y;winetricks corefonts dotnet20
* Winecfg to set windows version to XP. Setting wine to windows 7 would make excel go about not enough memory errors
* Winecfg to set msxml6 to built-in, then native. Otherwise it seems word bitches about some xml templates being wrong
* There was a dropdown menu in Word that wouldn't appear on the phone activation screen. This prevented me from finding out the phone number plus entering a confirmation number.
* Winecfg to set riched20 and gdiplus to native. Setting these and restarting word let me select the country for phone activation and the confirmation entry field became OK.
* I had to call +44 1290 211 388 which is MSFT Toll free activation number.
* Went through a couple of options, then selected mobile
* Got an SMS with a bitly link
* Had to click through a couple of options then enter the installation I
RE: Office 2010 installations on Debian 8 in 2016
by 0xc004f012 on Saturday September 3rd 2016, 5:13
Fix for last point:

* Had to click through a couple of options then enter the installation ID
RE: Office 2010 installations on Debian 8 in 2016
by Priyank Vashiar on Saturday April 13th 2019, 12:41
Yeah sorry, I didn't add the command- sudo apt install winbind samba. I recently tried installing it again and followed my own tutorial and couldn't do it. After reading the error. I understood the error. Sorry for any inconvenience.
Back