64-bit Client Installation of Microsoft Office 2010

Overview

Supported 64-bit Windows operating systems

64-bit editions of Windows Vista with Service Pack 1

64-bit editions of Windows 7

64-bit editions of Windows Server 2008 with SP1

64-bit editions of Windows Server 2008 R2

Notes:
The 64-bit Office client can be installed only on 64-bit editions of
Windows Vista with Service Pack 1, 64-bit editions of Windows Server
2008 with Service Pack 1, Windows 7, and Windows Server 2008 R2.

The 32-bit version of Office 2010 provides the same functionality and
is also compatible with 32-bit add-ins. Therefore, the 32-bit version of
Office 2010 is installed by default.

Office 2010 also provides support for running 32-bit Office 2010
applications on 64-bit Windows operating systems by using
Windows-32-on-Windows-64 (WOW64). WOW64 is the x86 emulator
that enables 32-bit Windows-based applications to run seamlessly on
64-bit Windows systems. Office 2010 lets users continue to use
existing 32-bit Microsoft ActiveX Controls, Component Object Model
(COM) add-ins, and Visual Basic for Applications (VBA).

Scenario

32-bit Office on
64-bit operating
system

New
installations

Default

Upgrades

64-bit Office on
64-bit operating
system

Not supported

32-bit Office on
32-bit operating
system

The 32-bit Office client is the default installation on 64-bit Windows

operating systems. It is installed as a WOW64 installation.

Advantages

Disadvantages

Running Office 2010 64-bit provides the following advantages:

The following issues might affect compatibility.

Ability to utilize additional memory.

Excel 2010 can load much larger workbooks. Excel 2010 made updates to use 64-bit
memory addressing to break out of the 2-GB addressable memory boundary that limits
32-bit applications.

Microsoft Project 2010 provides improved capacity, especially when you are dealing
with many subprojects to a large project.

Office 2010 server products (Microsoft SharePoint Server 2010,

Microsoft SharePoint Foundation 2010, and Microsoft Project Server
2010) support the 64-bit edition of Windows Server 2008 with Service
Pack 2, and Windows Server 2008 R2.

Enhanced default security protections through Hardware Data Execution Prevention

(DEP).

For click-to-run scenarios on supported 64-bit operating systems, the

only supported version is Office 2010 32-bit (WOW64).

General feature deprecations

The following section lists feature deprecations.

Microsoft Access

COM Add-ins and ActiveX controls

Add-in (COM) DLLs (dynamic link libraries) and ActiveX controls that were written for 32-bit Office will not
work in a 64-bit process. As a result, Office 2010 64-bit solutions that try to load 32-bit ActiveX controls or
DLLs will not work. 64-bit Office 2010 installations will only run 64-bit controls. Computers can have 64-bit
and 32-bit controls installed and Microsoft Office 2010 64-bit can only run the 64-bit versions of the controls.
The workaround for resolving these issues is to obtain 64-bit compatible controls and add-ins or to install
Office 2010 32-bit (WOW).
In addition to controls that load into Office applications, there are also Web-based solutions that use ActiveX
controls in Microsoft Internet Explorer. Office 2010 64-bit editions install some Office 32-bit client-side
controls for supporting solutions in a 32-bit browser (the default browser on current 64-bit Windows
systems). The Edit in Datasheet View functionality is not supported if you install Office 2010 64-bit clients.
The Datasheet View functionality is available if you install Office 2010 32-bit.

Microsoft Access MDE/ADE/ACCDE files

Installation recommendations

Architecture-specific folders and customization

tools

The recommendations for which edition of Office 2010 to install are

as follows:

Deployment considerations

The supported Windows operating system editions for 64-bit Office 2010
client include:

Processors that are 64-bit are becoming the standard for systems
that range from servers to desktop computers. 64-bit systems can
use more virtual and physical memory than 32-bit systems. This lets
users work with much larger data sets than they could previously,
and to analyze and solve large computational problems. Microsoft
Office 2010 introduces native 64-bit versions of Microsoft Office
products to take advantage of this larger capacity, but many users of
Office are unlikely to require the 64-bit version. For example, this
additional capacity is needed only by those Microsoft Excel users
who require Excel spreadsheets that are larger than 2 gigabytes
(GB).

Supported scenarios

The Office 2010 DVD sources include two architecture-specific folders:

one for 32-bit systems and one for 64-bit. A separate Config.xml file and
Updates folder is included in each of these folders.

If users in your organization depend on existing extensions to

Office, such as ActiveX controls, third-party add-ins, in-house
solutions built on previous versions of Office, or 32-bit versions of
programs that interface directly with Office, we recommend that
you install 32-bit Office 2010 (the default installation) on
computers that are running both 32-bit and 64-bit supported
Windows operating systems.

This section highlights the tasks to perform when installing 64-bit Office 2010 in an
enterprise.

Prepare 64bit installation

Verify that
computers meet
hardware
requirements for
64-bit Office

Determine if 32bit Office

applications are
installed

Uninstall 32-bit
Office
applications
before running
64-bit setup

Microsoft Office Document Imaging (MODI) and all its components are deprecated for both 32-bit and 64-bit
Office 2010. The legacy Equation Editor is not supported on 64-bit Office 2010, but is supported for 32-bit
Office 2010 installations (WOW64).

If you developed and installed 32-bit Messaging Application Programming Interface (MAPI) applications,
there are actions that you should take to change and rebuild 32-bit MAPI applications to run on a 64-bit
platform. This also applies for 64-bit applications to run on a 32-bit platform.
Starting with Office 2010, Outlook is available as a 32-bit application and a 64-bit application. The version
(bitness) of Outlook that you choose depends on the edition of the Windows operating system (32-bit or 64bit) and the edition of Office 2010 (32- or 64-bit) that is installed on the computer, if Office is already installed
on that computer. The bitness of an installed version of Outlook is always the same as the bitness of Office
2010, if Office is installed on the same computer. A 32-bit version of Outlook 2010 cannot be installed on the
same computer on which 64-bit versions of other Office 2010 applications are already installed, such as 64bit Microsoft Word 2010 or 64-bit Microsoft Excel 2010. Similarly, a 64-bit version of Outlook 2010 cannot be
installed on the same computer on which 32-bit versions of other Office applications are already installed.

Inserting an object into an Office 2010 application document may fail in cross-bitness scenarios. For
example if you insert a 32-bit object in a 64-bit Office 2010 application document.

There are differences between the 32-bit and 64-bit Graphics Device Interface (GDI) that might have
performance implications because of the lack of MMX support on 64-bit. Intel's MMX technology is an
extension of the Intel architecture (IA) instruction set. The technology uses a single-instruction, multiple-data
(SIMD) technique to speed up multimedia and communications software by processing data elements in
parallel.

Macros with Visual Basic for Applications (VBA)

Tasks: Installing native 64-bit

Office 2010 in enterprise
environments

Word

In-place activation

Graphics rendering
For the latest information, see 64-bit editions of Office 2010 in the
Office 2010 Resource Kit.

The Microsoft Works database converter (wdbimp.dll) is removed from both 32-bit and 64-bit installations of
Office 2010. This converter was previously used in the Mail Merge functionality to connect to a data source
created in Microsoft Works.

WLL (Word Add-in libraries) WLL files are deprecated for both 32-bit and 64-bit Office 2010. A WLL is an
add-in for Microsoft Word that you can build with any compiler that supports building DLLs.

If some users in your organization are Excel expert users who

work with Excel spreadsheets that are larger than 2 gigabytes
(GB), they can install the 64-bit edition of Office 2010. In addition,
if you have in-house solution developers, we recommend that
those developers have access to the 64-bit edition of Office 2010
so that they can test and update your in-house solutions on the
64-bit edition of Office 2010.

Publisher

Databases that have had their source code removed (such as .mde, .ade, and .accde files) cannot be
moved between 32-bit and 64-bit editions of Office 2010. Such databases that are created by using 32-bit
Office (any version) can be used only with 32-bit Office, and a database that is created on 64-bit Office can
be used only on 64-bit Office.

The following issues might occur if there is not a match between the bitness of Office 2010 and registered
applications:
An OLE server may not instantiate in place and may fail to open if the application registered is not the
same bitness as the version of Office installed. For example, if your OLE Server application is 32-bit and
the version of Office installed is 64-bit.

A 64-bit version of the Office Customization Tool (OCT) is also included.

The 64-bit version of the OCT provides the same user interface,
capabilities, and configurable settings as the 32-bit version. The following
figure shows the architecture-specific folders.

The Replication Conflict Viewer is removed from both the 32-bit and 64-bit installations of Office 2010. This
functionality can still be implemented by using a documented custom function, ReplicationConflictFunction.
For information, see the Access 2007 Developer Reference (http://go.microsoft.com/fwlink/?LinkId=150854).

VBA code that uses the Declare statement to access the Windows application programming interface (API)
or other DLL entry points will see differences between 32-bit and 64-bit versions. The Declare statement
must be updated with the PtrSafe attribute after inputs and outputs to the API have been reviewed and
updated. Declare statements will not work in 64-bit VBA without the PtrSafe attribute. New data types are
added to 64-bit Office 2010 VBA: LongLong and LongPtr.

Considerations for MAPI applications

MAPI applications include stand-alone applications such as Microsoft Communicator and MFCMAPI, and
service providers such as address book, store, and transport providers. For MAPI method and function calls
to work in a MAPI application (except for one Simple MAPI function, MAPISendMail), the bitness of the MAPI
application must be the same as the bitness of the MAPI subsystem on the computer on which the
application is targeted to run. The bitness of the MAPI subsystem, in turn, is determined by and is always the
same as the bitness of the installed version of Outlook. For information about how to prepare MAPI
applications for 32-bit and 64-bit platforms, see Building MAPI Applications on 32-bit and 64-bit Platforms
(http://go.microsoft.com/fwlink/?LinkId=165489).

Office 2010 64-bit Setup processes

The Setup sequence for a 64-bit Office client installation is as follows. The sequence is the same as for a standard
32-bit Office client installation with the addition of specific checks done for 64-bit Office 2010, as shown in the
diagrams in this section. For more information, see 64-bit editions of Office 2010 in the Office 2010 Resource Kit.

Create network
installation point

Running Office 2010 Setup.exe from x64 folder

from 64-bit operating system: Setup checks

Office 2010 Setup platform chooser: Running Setup.exe from root folder

Running Office 2010 Setup.exe from x86 folder:

Setup checks

Check for 64-bit

Office 2010
prerequisites

Run Setup.exe

32-bit edition of Windows

Configure 64bit installation

Use 64-bit OCT

to customize
installation

Use Config.xml
(x64 folder) to
customize setup

Configure user
settings through
Group Policy

Install Office
2010 32-bit

32-bit Office
applications
installed?

64-bit edition of Windows

Determine
Windows
operating
system edition

Install 64-bit edition

of Office 2010
Yes

64-bit Office
applications
installed?

No

Install 32-bit edition

of Office 2010

Install Office
2010 64-bit

64-bit Office
application
installed?
No

Yes

Error message displays to

inform users they must
uninstall all 32-bit Office
applications if they want to
install Office 2010 64-bit.
Error lists installed 32-bit
Office applications.

Error message displays.

Setup is blocked if Office
2010 64-bit is detected
when users try to install
Office 2010 by running the
32-bit version of setup (from
the x86 folder).

Install Office
2010 32-bit

Test deployment method you will use to deploy

Note: Office 2010 32-bit is the default install on

a 64-bit Windows operating system (uses
WOW). Also applies if upgrading existing 32-bit
Office installation.
Run Setup.exe
from x64 folder

Precache local
installation
source

Run Setup from

local installation
source

Read XML data

Build feature tree

Yes

Test 64-bit
configuration
in nonproduction
environment

No

64-bit setup sequence

Use enterprise
deployment tool
to install

Create local
installation
source

Install Office

Apply 64-bit
customization
MSP file

Apply software
updates

Install 64-bit
Office 2010
in production
environment

Choose deployment method based on testing

Run Setup.exe
from x64 folder

Precache local
installation
source

Run Setup from

local installation
source

Use enterprise
deployment tool
to install

Enterprise software deployment options include:

Installing from network share
Enterprise software distribution tools such as:

Systems Management Server

System Center Configuration Manager

Microsoft System Center Essentials

Group Policy Computer Startup Scripts

Windows Server Terminal Services

2010 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at FeedORK@microsoft.com.