Microsoft Office (installer only)

Retail release January 29, 2013

This entry is just for testing the installer of Microsoft Office 2013 (aka Office 15) office suite.

Reports on specific programs included in Office 2013 should be submitted to their respective AppDB entries.

Office 2013 is available in 5 editions:

  • Home & Student (Retail, OEM)
  • Standard (Volume)
  • Home & Business (Retail, OEM)
  • Professional (Retail, OEM)
  • Professional Plus (Volume)
When reporting test results, please follow the Guidelines for Submitting Test Reports below (scroll down to notes section).

Application Details:

Version: 2013 (32 bit)
License: Retail
Votes: 10
Latest Rating: Gold
Latest Wine Version Tested: 4.19

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

Tested HUP (home use program) version of 2013 Pro Plus.  This comes with a specially downloaded installer from MS that includes the license key/activation (no option for phone in, etc.).

Make sure you use a 32-bit wine prefix.

What does not

Initially was getting error 30175-4 partway through installer setup.


Ran down error 30175-4, turned out it's an activation error.  Then, I noticed some errors pertaining to missing encrypted authentication on the console when running the installer in Wine.  Office in Wine has a dependency on libgnutls, and since it's a 64-bit Arch distro but 32-bit installer, I needed to add (note, requires multilib access in Arch/pacman....see Arch Multilib Wiki):

pacman -Syu lib32-gnutls

Also, disabled firewall (not sure if this was necessary), installed libxml6 via winetricks (again, not sure if necessary, was trying many things to resolve failed install), and added the following registry key and DWORD (some users have reported it fixes black screen in installer, not sure if necessary):

KEY_CURRENT_USER\Software\Wine -> create a new key in the Wine folder named "Direct3D"
New DWORD Value named "MaxVersionGL" and set the hex value data to 30002

I have a slow internet connection, so retesting without some of the above workarounds would take many hours at this point.

What was not tested

Only the installer was tested for the HUP (home use program).

Hardware tested


  • GPU: AMD
  • Driver: open source

Additional Comments

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowUbuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)Nov 03 20194.19Yes Yes YesGoldnomadmz 
ShowDebian 10.x "Buster"Jul 14 20194.12.1-stagingNo, but has workaround No YesGarbageboskar 
ShowFedora 29 x86_64Feb 03 20194.0No Not installable NoGarbageClément Duveau 
ShowUbuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)Oct 29 20183.19Yes Yes YesGoldJonathan 
CurrentArch Linux x86_64Oct 14 20183.17Yes Yes YesGoldMK 

Known Bugs

Bug # Description Status Resolution Other apps affected
39810 Office 2007/2010/2013/2016 uninstallation fails NEW View
43581 Microsoft Office 365 edition of Office 2013 installer fails with 'cache_entry_from_xsd_doc failed to parse doc' (non-standard '\u####' sequence) NEW View
43783 Office2013 activation crashes when using HTTP proxy UNCONFIRMED 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 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.

Known regressions


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

2.18--3.0-rc4 (bug 44036)


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

Further info:
by Peter on Wednesday April 1st 2020, 10:06
I am installing MS Office 2013 Professional Plus and on a clean Wine installation.
msiexec.exe error
by Peter on Wednesday April 1st 2020, 10:05
Hi, I am having trouble installing 32-bit MS Office 2013 in my Arch Linux PC. The installation does fine until it finds an msiexec.exe error, which terminates it. Any clue why that happens?
Solution for custom installation -> drop down menu
by braytac on Sunday October 7th 2018, 12:48
You will not see anything in selecting, but finally the status is changed (by example: if option is not install -> you will see the "X" )

1)- Left click
2)- If major item is selected for [ install sub-items complety OR partialy ]
-> Press up arrow once for not install any (X)
If major item is selected for [ not install any (X) ]
-> Press down arrow once for install ALL
3)- Press Enter

Similar for subitems:

If subitem marked for not install (X) -> change to install: left click->Enter
If subitem marked for install -> change to not install: left click->arrow Up -> Enter
Where is the HKCU\Software\Wine\Direct3D\ entry?
by Benjamin D. on Saturday October 7th 2017, 8:14
I just managed to install office 2013 with the help of this entry! Thanks a lot!
But when i run Word I also entcounter the black window problem. I searched out fot the HKCU\Software\Wine\Direct3D\ reg entry but i couldn't even find the Direct3D entry anywhere. Am I missing something?

Besides: I used playonlinux to install office 2013 but before i did the installation auf the setup.exe i installed msxml4 followed by msxml6. This did the job for installation....

Thanks anyway cool job!

Best Benjamin.
RE: Where is the HKCU\Software\Wine\Direct3D\ entry?
by Rosanne on Saturday October 7th 2017, 8:27
RE: Where is the HKCU\Software\Wine\Direct3D\ entry?
by Benjamin D. on Saturday October 7th 2017, 9:40
Damn it works! Great! Thanks and sorry for the newbie stuff ;) But I am not an expert on wine!

Best Benjamin.
RE: Where is the HKCU\Software\Wine\Direct3D\ entry?
by nomadmz on Sunday November 3rd 2019, 16:11
You should create this folder in the registry. You won't find it!!
Really strange problem: With msxml6 installed, no product key works anymore!
by Tormen on Friday March 24th 2017, 13:39

It seems really bizzarre, but I tried it several times:

With the trial version (both German (de-de) and English (en-us)) downloaded from
And mount the img file OfficeProfessionalPlus_x86_en-us.img to /mnt/iso.

When I create a fresh WINEPREFIX, set it to win7 and then install winetricks msxml6 and then run the setup, like so:

mkdir -p /virt/wines/ms.office2013
WINEARCH=win32 WINEPREFIX=/virt/wines/ms.office2013/ winetricks settings win7
WINEARCH=win32 WINEPREFIX=/virt/wines/ms.office2013/ winetricks msxml6
WINEARCH=win32 WINEPREFIX=/virt/wines/ms.office2013/ wine /mnt/iso/setup.exe

The behaviour of the setup changes!

It starts with first asking you to enter a product key.
And no matter what product key I entered, they all never worked (even though they should).

Without installing the msxml6, I saw a bunch of xml related messages in the output when launcching the setup, but in this case the setup right away offers to configure and install ms office!

Is that logical that with the msxml6 installed, this would then actually /break/ something ?
If helpful, I could provide debug output and/or file a bug report.

Thanks a lot in advance for any feedback!