WineHQ

Microsoft Office (installer only)

64 bit version of Microsoft Office 2010 installer.

Retail release June 15, 2010

Application Details:

Version: 2010 (64 bit)
License: Demo
URL: http://www.office.com
Votes: 0
Latest Rating: Garbage
Latest Wine Version Tested: 5.6

Maintainers: About Maintainership

Free Download Trial

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

First window describing a progress of extraction of the files.

What does not

Actual installation of application.

Workarounds

What was not tested

Everything possible was tested.

Hardware tested

Graphics:

  • GPU:
  • Driver:

Additional Comments

Testing platform: AMD Phenom II X2 550 BE [OC 3.6 GHz] Palit GeForce 7300GT [256MB; 512MHz core and memory] Realtek 7.1 sound 4 GB 800 MHz Kingston HyperX DDR2 RAM 23 XI 2009 - Terminal stated an error connected to the 64-bit architecture just before start of installation. I will investigate further and submit new data daily. All operations are made using PlayOnLinux application. Standard procedure: Terminal > playonlinux > Install > Install unsupported application > Existing Environment > Set & configure wine version > 1.1.33 > tweaking > installation 23 XI 2009 - Wine basic configuration, set to Windows 7: Running install menu fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:reg:GetNativeSystemInfo (0x32f9bc) using GetSystemInfo() err:process:create_process starting 64-bit process L"C:\\windows\\temp\\OWPe132.tmp\\setup.exe" not supported on this platform 24 XI 2009 - Wine basic configuration, set to Windows 2008: Running install menu fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:reg:GetNativeSystemInfo (0x32f9bc) using GetSystemInfo() err:process:create_process starting 64-bit process L"C:\\windows\\temp\\OWPe0.tmp\\setup.exe" not supported on this platform 24 XI 2009 - Wine basic configuration, set to Windows Vista: Running install menu fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:reg:GetNativeSystemInfo (0x32f9bc) using GetSystemInfo() err:process:create_process starting 64-bit process L"C:\\windows\\temp\\OWPe7.tmp\\setup.exe" not supported on this platform 24 XI 2009 - Wine basic configuration, set to Windows 2003: Running install menu fixme:reg:GetNativeSystemInfo (0x32f9bc) using GetSystemInfo() err:process:create_process starting 64-bit process L"C:\\windows\\temp\\OWPe1.tmp\\setup.exe" not supported on this platform 24 XI 2009 - Wine basic configuration, set to Windows XP: Running install menu fixme:reg:GetNativeSystemInfo (0x32f9bc) using GetSystemInfo() err:process:create_process starting 64-bit process L"C:\\windows\\temp\\OWPfe.tmp\\setup.exe" not supported on this platform 24 XI 2009 - I can't think of any other wine manipulations that can be can done to bypass these errors. Later I will test 32-bit beta. This version seems impossible to install because of lack of wine 64-bit support.

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
ShowDeepin Linux OS 15.5 desktopApr 13 20205.6No, but has workaround Yes YesGarbageJoseph Moreno 
ShowUbuntu 18.10 "Cosmic" amd64 (+variants like Kubuntu)Apr 01 20205.5No Not installable NoGarbageJonathan Alfonso 
ShowArch Linux x86_64Feb 07 20194.0-rc2No Not installable NoGarbageJonas Erbe 
ShowopenSUSE Leap 42.3 x86_64Mar 19 20183.0No Not installable NoGarbageMichaelOF 
ShowopenSUSE Tumbleweed (rolling release)Oct 29 20151.7.53No Not installable Garbagean anonymous user 
ShowopenSUSE 13.1 x86_64Jul 15 20141.7.22No Not installable GarbageRaf J 
ShowUbuntu 13.10 "Saucy" amd64 (+ variants like Kubuntu)Jan 25 20141.7.11No Not installable Garbagean anonymous user 
ShowLinux Mint 14 "Nadia" x86_64Feb 18 20131.5.24No Not installable Garbagean anonymous user 
ShowLinux Mint 14 "Nadia" x86_64Feb 18 20131.5.19No Not installable Garbagean anonymous user 
ShowFedora 17 x86_64Oct 20 20121.5.13No Not installable Garbagean anonymous user 
ShowUbuntu 13.04 "Raring" amd64 (+ variants like Kubuntu)May 06 20131.4.1No Not installable Garbagean anonymous user 
ShowUbuntu 12.04 "Precise" amd64 (+ variants like Kubuntu)May 24 20121.4No Not installable Garbagean anonymous user 
ShowUbuntu 10.04 "Lucid" amd64 (+ variants like Kubuntu)Oct 02 20101.2No Not installable GarbageJose Luis Triana 
ShowLinux Mint 8 "Helena"Jan 23 20101.1.37No Not installable Garbagean anonymous user 
CurrentUbuntu 9.10 "Karmic" amd64 (+ variants like Kubuntu)Nov 23 20091.1.33No Not installable GarbageMarek PaÅ›nikowski 

Known Bugs

Bug # Description Status Resolution Other apps affected
44753 64-bit Microsoft Office 2010 installer crashes 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 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.
  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

Back