WineHQ
Category: Main Productivity Office Suites Microsoft Office (installer only) 2010 (64 bit)

Microsoft Office (installer only)


View / Submit Screenshot

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: Bronze
Latest Wine Version Tested: 6.0

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

Nothing, even with Workarounds isn't useful.

What does not

Installer starts well. Can select the components to install and the user data, however at 65% of the installation stops and fails.

007c:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0041:err:msi:execute_script Execution of script 0 halted; action L"[VYBBJTRJPBQFQRFQFT4DH3GVB\0080\0080\008017\0080sl.RAC.GENERIC.PRIVATE\008077u/PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz48cjpsaWNlbnNlIHhtbG5zOnI9InVybjptcGVnOm1wZWcyMToyMDAzOjAxLVJFTC1SLU5TIiBsaWNlbnNlSWQ9Ins1ZjcxMzBmOC0xN2Y0LTQ3MzUtOGZkOS05ODI3MmU3ZmQ1ZTV9IiB4bWxuczpzeD0idXJuOm"... returned 1603
0041:err:msi:ITERATE_Actions Execution halted, action L"InstallExecute" returned 1603

This error is similar to the one obtained when trying to install the 32-bit version of Office 2010 without installing winbind. 

Workarounds

Installation can be completed by pre-installing a minimum 32-bit Office 2010 that includes the Office Software Protection Platform Service.
Before starting the 64bit installation, the 32bit installer records must be removed.
However, when trying to run any 64-bit product it will not be able to validate the license as it cannot connect to the Office Software Protection Platform Service as the RPC call apparently tries to use NDR64 that is not implemented.

What was not tested

Nothing.

Hardware tested

Graphics:

  • GPU: Other
  • Driver: unknown

Additional Comments

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?		RatingSubmitter
ShowUbuntu 20.04 "Focal" (+ variants like Kubuntu)Jan 24 20216.0No, but has workaround Yes YesBronzeJoseph Moreno 
CurrentDeepin 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 

Known Bugs

Bug # Description Status Resolution Other apps affected
44753 64-bit Microsoft Office 2010 installer crashes UNCONFIRMED View
51658 Error trying to install Office 2010 x64 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