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:
|Version:||2013 (32 bit)|
|Latest Wine Version Tested:||7.21|
Maintainers: About Maintainership
Selecting my Microsoft Office 2013 Pro Subscription from the "Subscriptions" tab under my Microsoft account and downloading either the Office Professional 2013 32-bit/64-bit installers and running them under a clean 32-bit/64-bit WINE prefix, will result in the installer going to about 50% completion and crashing with the Error Code: 30175-4.
Downloading the offline installer, mounting it and running either "setup.exe", "setup32.exe" or "setup64.exe" in a fresh WINE prefix every time will cause the installer to error out at around 10% completion and the user is forced to close it.
What does not
The online and offline installers do not complete correctly.
What was not tested
Running Microsoft Office.
Some users managed to get Microsoft Office 2013 and Office 2013 Pro working with these methods:
However, I attempted using an older version of WINE (3.1) with PlayOnLinux to install Microsoft Office 2013 Pro, but had the same errors as WINE 6.0.1. The method used was from this video:
However, I believe the issue might lie in the Office 2013 Pro installer, since the installer I am using for Office 2013 Pro is the latest version at the time of posting, which could cause errors in the installer that were not present in older versions of the installer.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Debian 11||Nov 17 2022||7.21||Yes||Yes||Yes||Silver||Alois Schlögl|
|Current||Linux Mint 20.1||Jun 17 2021||6.0.1||No||Not installable||No||Garbage||Metalinux|
|Show||Pop!_OS 20.04 LTS||May 09 2020||5.7||Yes||Yes||Yes||Silver||Rodrigo Vega Moreno|
|Show||Ubuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)||Nov 03 2019||4.19||Yes||Yes||Yes||Gold||nomadmz|
|Show||Debian 10.x "Buster"||Jul 14 2019||4.12.1-staging||No, but has workaround||No||Yes||Garbage||boskar|
|Bug #||Description||Status||Resolution||Other apps affected|
|31349||Office 365 (Office 2013) web installer aborts early (needs support for string alias for common RID in sid strings)||CLOSED||FIXED||View|
|31468||Office 2013 installer crashes with a "serious problem" error||CLOSED||DUPLICATE||View|
|31487||Multiple applications and installers crash on unimplemented function KERNEL32.dll.InitOnceExecuteOnce (MS Office 2013, Windows Live Essentials 2012, .NET Framework 4.5, Skydrive, Adobe Lightroom, WinRT/ARM Applications)||CLOSED||FIXED||View|
|34869||Microsoft Office 2013 full offline installer crashes on startup (TEB access with NULL TLS array pointer, failure to handle case where only late-bound modules have TLS directory)||CLOSED||FIXED||View|
|35342||Office 2013 full offline install setup crash at startup||CLOSED||FIXED||View|
|36092||Microsoft Office 2013 (15.0) and OneNote web installer crashes on unimplemented function IPHLPAPI.DLL.CreateSortedAddressPairs||CLOSED||FIXED||View|
|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)||CLOSED||FIXED||View|
|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)||CLOSED||FIXED||View|
|43783||Office2013 activation crashes when using HTTP proxy||UNCONFIRMED||View|
|44036||Multiple installers fail (affects MS Office 2010/2013, Notation Composer 3)||CLOSED||FIXED||View|
|45284||Multiple Microsoft Office installers crash with Windows 8+ setting due to missing 'user32.RegisterPointerDeviceNotifications' stub (Office 2013)||CLOSED||FIXED||View|
Test reports that do not follow these guidelines will be rejected.
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.
by nomadmz on Saturday April 11th 2020, 19:20
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.
by nomadmz on Saturday April 11th 2020, 15:35
WINEPREFIX=~/.wine/Office2013 WINEARCH=win32 winecfg
by nomadmz on Saturday April 11th 2020, 19:24
by Peter on Wednesday April 1st 2020, 10:06
by Peter on Wednesday April 1st 2020, 10:05
by nomadmz on Saturday April 11th 2020, 19:22
WINEPREFIX=~/.wine/Office2013 WINEARCH=win32 winecfg
by Henrique de Sousa on Saturday January 30th 2021, 12:08
by braytac on Sunday October 7th 2018, 12:48
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
by Benjamin D. on Saturday October 7th 2017, 8:14
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!
by Rosanne on Saturday October 7th 2017, 8:27
by Benjamin D. on Saturday October 7th 2017, 9:40
by nomadmz on Sunday November 3rd 2019, 16:11
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!