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: 12
Latest Rating: Gold
Latest Wine Version Tested: 2.15

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

After playing with a few more options, overrides, and workarounds, I managed to get the installer to get quite a bit further.  It gets past the setup phase, and into the download/install phase, and even prompts for activation.  However, it all falls apart around then.

What does not

Installation eventually still fails.  The WINE console output spits out lots of messages about Direct3D errors.  The installer then reports "Something went wrong" and "Sorry, we ran into a problem.".  There is a window that pops up that is full of garbled pixels.  Another window pops up prompting for activation.  Another window pops up telling you that Office is being prepared, and that it should only take a few minutes.  The progress bar just cycles forever (I let it sit for a half hour).

App icons show up in Gnome, but launching Word or Excel reports errors with the installation, so it's clear the install didn't complete.

Workarounds

What was not tested

Completed installation, uninstall.

Hardware tested

Graphics:

  • GPU:
  • Driver:
  • Additional Comments

    Getting this working involved some research and experimentation...what finally worked: 1) use 32-bit arch (WINEARCH=win32) and installer 2) Use winetricks to install msxml6 (WINEPREFIX=... winetricks msxml6)...without this, it will error out during initial setup at around 68% with an XSD parse error. 3) Use winetricks to install dotnet40 (WINEPREFIX=... winetricks dotnet40)...without this, the installer will get past initial setup, then fail at ~21% during download/install. 4) Use Windows 7 environment 5) Supposedly, using regedit (WINEPREFIX=... wine regedit) to cap Direct3D GL to v3.2 (which includes support for compatibility profiles) to workaround missing features in GL v4 (HKEY\CURRENT_USER\Software\Wine\Direct3D\MaxVersionGL = (DWORD) 0x30002...note, you will probably need to create the Direct3D key) is supposed to fix the D3D errors. dotnet35, dotnet45 both don't install, nor work. Also, there is an override (riched20) you may need to add AFTER installation has completed. I also used winetricks to install corefonts. It seems that installing the following Arch Linux packages got some more errors to go away and get as far as the activation prompt, but install still fails: lib32-libxslt libwbclient lib32-libxml2

    selected in Test Results table below
    Operating systemTest dateWine versionInstalls?Runs?Used
    Workaround?
    RatingSubmitter
    ShowArch Linux x86_64Aug 24 20172.15Yes Yes YesGoldJason Cone 
    CurrentArch Linux x86_64Feb 26 20172.2No Not installable GarbageMK 
    ShowArch Linux x86_64Feb 26 20172.2No Not installable GarbageMK 
    ShowArch Linux x86_64Mar 24 20172.1Yes Yes PlatinumTormen 
    ShowArch Linux x86_64Feb 08 20172.1No Not installable GarbageAurélien 

    Known Bugs

    Bug # Description Status Resolution Other apps affected
    38648 Multiple games and applications need support for Mesa OpenGL >= 3.2 core profiles, Shader Model 4, GLSL 1.50 (Microsoft Office 2013 installer, .NET/XNA games) NEW View
    39810 Office 2010/2013/2016 Pro Plus uninstallation fails NEW View
    43581 Office 2013 365 installer: Something went wrong NEW 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 2013 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. ­

    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.

    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