Microsoft Office (installer only)

What works

Everything.

What does not

Add winetricks dotnet20 msxml6 corefonts

This is because it needs samba which is installed by dotnet20.

Workarounds

Add winetricks dotnet20 msxml6 corefonts

What was not tested

I just used word and powerpoint. Everything else was not tested.

Hardware tested

Graphics:

• GPU: AMD
• Driver: open source

Additional Comments

It worked great for me.

sudo dpkg --add-architecture i386
sudo apt remove wine*
wget -qO- https://dl.winehq.org/wine-bui... | sudo apt-key add -
sudo apt-add-repository 'deb http://dl.winehq.org/wine-buil... bionic main'
sudo apt-get install --install-recommends winehq-devel
wine --version
sudo apt install winetricks
WINEARCH=win32 WINEPREFIX=~/.wineoffice2010 winetricks dotnet20 msxml6 corefonts
WINEPREFIX=~/.wineoffice2010 wine Download/office/setup.exe
install with this and working all good

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.

Test reports that do not follow these guidelines will be rejected. ­

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

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

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

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

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.

Test reports that do not follow these guidelines will be rejected.