WineHQ

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
URL: http://www.office.com
Votes: 10
Latest Rating: Silver
Latest Wine Version Tested: 7.21

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

installation suceeded partially with winetricks msxml6

What does not

The installation/registration somehow died because of "Click to run" was not working properly. 


Basically I

1. Downloaded current installer

2. Found out it suffered from msxml bug

3. In a clean wineprefix installed msxml6 from winetricks

4. Tried to install it again - deadloop at ~83%, but it is mostly installed (even winemenubuilder did their job)

5. Killed the installer

6. Tried to start Word from the menu: Click to Run service starts, WINWORD.EXE starts, then WINWORD.EXE stops and OfficeC2RClient.exe starts and stalls.

Workarounds

msxml6 from winetricks allowed the installer to reach 83%

What was not tested

actual programs, registration

Hardware tested

Graphics:

  • GPU: Nvidia
  • Driver: proprietary

Additional Comments

Tested Professional Plus downloaded yesterday from MS. 

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
ShowDebian GNU/Linux 11.x "Bullseye"Nov 17 20227.21Yes Yes YesSilverAlois Schlögl 
ShowLinux Mint 20.1Jun 17 20216.0.1No Not installable NoGarbageMetalinux 
ShowPop!_OS 20.04 LTSMay 09 20205.7Yes Yes YesSilverRodrigo Vega Moreno 
ShowUbuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)Nov 03 20194.19Yes Yes YesGoldnomadmz 
CurrentDebian GNU/Linux 10.x "Buster"Jul 14 20194.12.1-stagingNo, but has workaround No YesGarbageboskar 

Known Bugs

Bug # Description Status Resolution Other apps affected
39810 Office 2007/2010/2013/2016 uninstallation fails 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

(2018-01-07)

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)

Comments

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

Updating Office 2013 - Security and performance fixes
by nomadmz on Saturday April 11th 2020, 19:20
There could be some strategies to keep Office 2013 update:

1. To clone a current office 2013 update scheme in Windows OS and transfer it to the Wine instalation
2. Use an automated software to identify which updates are required in the current Wine instalation and deploy it under Linux

For these two options the outcome is the same: you will have to re-install office 2013 in order to get it full patched, the only difference is the source of these update files.

For the first case (1. To clone a current office update database):

The Office installer has an option to install any .msp file stored in /update folder under the installation path.

You can clone a current office 2013 updates database following the directions here: supportishere.com/how-to-download-microsoft-office-2013-updates-the-easy-way/ and place the files in the /updates folder, so then, you install office using: WINEPREFIX=~/.wine/Office2013 WINEARCH=win32 wine ~/office/setup.exe

And setup.exe will detect any .msp file in the /update folder and will apply them.

Pros: you will have a full updated office using files directly from Microsoft.


Second option (use an automated software)
I've tested wsusoffline www.wsusoffline.net, it has two executables: UpdateGenerator.exe and UpdateInstaller.exe (in "client" folder).

With the first one you can scan your current office installation and check for the missing updates: WINEPREFIX=~/.wine/Office2013 WINEARCH=win32 wine ~/wsusoffline/UpdateGenerator.exe

Then, you will have all the .cab files stored in the client/wsus/ folder. Now, you have to run UpdateInstaller.exe (at this point it failed, I couldn't get it running fine).

The option here is to convert all the .cab files to .msp files, so you can copy them to the /setup folder under the office 2013 install folder, and run setup.exe as instructed in option 1 (clone an existing full patched office installation).

Pros: You can update your office without access to a Windows running machine
Cons: You rely on a third party to get security software and fixes.

Overall cons: With any of these strategies you still have to reinstall your Office from time to time.
msiexec.exe
by nomadmz on Saturday April 11th 2020, 15:35
Hi, check if your wineprefix is 32bits: if your Linux is 64bits, Wine will make 64bits wineprefix by default too, so, check that you've created a 32bits wineprefix by this way:

WINEPREFIX=~/.wine/Office2013 WINEARCH=win32 winecfg
RE: msiexec.exe
by nomadmz on Saturday April 11th 2020, 19:24
Please delete: repeated post
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?
RE: msiexec.exe error
by nomadmz on Saturday April 11th 2020, 19:22
Hi, check if your wineprefix is 32bits: if your Linux is 64bits, Wine will make 64bits wineprefix by default too, so, check that you've created a 32bits wineprefix by this way:

WINEPREFIX=~/.wine/Office2013 WINEARCH=win32 winecfg
RE: msiexec.exe error
by Henrique de Sousa on Saturday January 30th 2021, 12:08
I'm also having the same issue, mid installation crashes with msiexec.exe error. Wine-staging-6.0, Linux Mint 20.0 (Ubuntu 20.04 based). 32 bit prefix, msxml6
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
Hi,

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

With the trial version (both German (de-de) and English (en-us)) downloaded from
www.microsoft.com/de-de/evalcenter/evaluate-office-professional-plus-2013
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!

Tormen
Back