Share via

  • Article

64-bit editions of Office 2010

 

Applies to: Office 2010

Topic Last Modified: 2012-11-29

Banner stating end of support date for Office 2010 with link to more info

Processors that are 64-bit are becoming the standard for systems that range from servers to desktop computers. The 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. For example, this additional capacity is needed only by those Microsoft Excel users who require Excel spreadsheets that are larger than 2 gigabytes (GB). 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.

Note

Are you looking for information about which edition of Office 2010 to install (32- or 64-bit)? If so, see Choose the 32-bit or 64-bit version of Microsoft Office (https://go.microsoft.com/fwlink/?LinkID=245825).

Office 2010 also provides support for 32-bit Office 2010 applications that run 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 Microsoft ActiveX Controls, Component Object Model (COM) add-ins, and Visual Basic for Applications (VBA), which are primarily 32-bit because no 64-bit versions are available yet for many add-ins. Supporting 32-bit Office 2010 applications that run on 64-bit operating systems allows for better compatibility with controls, add-ins, and VBA.

The recommendations for which edition of Office 2010 to install are as follows:

  • 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 (x86) Office 2010 (the default installation) on computers that are running both 32-bit and 64-bit supported Windows operating systems.

  • 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 (x64) 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.

This article applies to the current release of Office 2010. For a visual representation of this information, see 64-bit Client Installation of Microsoft Office 2010 (https://go.microsoft.com/fwlink/p/?LinkId=168620), which includes supported scenarios, deployment considerations, and an overview of the Setup process.

64-bit Client Installation of Office 2010 - Model

In this article:

  • Supported Windows operating systems

  • Architecture-specific folders and customization tools

  • Supported scenarios

  • Deployment considerations

  • Setup process

  • Assessing your current environment for application compatibility

Supported Windows operating systems

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

  • 64-bit editions of Windows Vista with SP1

  • 64-bit editions of Windows Server 2008 with Service Pack 1

  • Windows 7

  • Windows Server 2008 R2

The following statements apply:

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

  • The 32-bit Office client is supported as a WOW64 installation. This is the default installation on 64-bit Windows operating systems. The 32-bit Windows-based applications run on 64-bit Windows, which allows for compatibility with 32-bit Office applications and add-ins.

  • 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. For more information, see the following resources:

  • For click-to-run scenarios, the supported version is Office 2010 32-bit (WOW64) on computers that run the supported 64-bit editions of Windows operating systems.

Architecture-specific folders and customization tools

Office 2010 includes two architecture-specific folders: one for 32-bit and one for 64-bit.

Each of these folders contains the following:

  • A separate Config.xml file and Updates folder.

  • An architecture-specific Office Customization Tool (OCT). The OCT files are located in the Admin folder for the x86 (32-bit) and x64 (64-bit) folders, respectively.

    The 64-bit version of the OCT provides the same user interface, capabilities, and configurable settings as the 32-bit version. Office 2010 introduces XML versions of OPA files: OPAX files (.opax) for non-language specific resources and OPAL files (.opal) for language-specific resources.

    The OCT provides support for importing Setup customization files (.msp files) as follows:

    • 64-bit Setup customization files can be imported into 32-bit OCT and can then be used to customize 32-bit Office products.

    • 32-bit Setup customization files can be imported into 64-bit OCT and can then be used to customize 64-bit Office products.

      A 32-bit Setup customization file that is imported to 64-bit OCT is converted to 64-bit, and a 64-bit customization file that is imported to 32-bit OCT is converted to 32-bit. For more information about how to use the Import feature, see Import an Office 2010 Setup customization file.

If you have installed Office 2010 including Microsoft Outlook 2010, Outlook sets a registry key named Bitness of type REG_SZ on the computer on which it is installed. The Bitness registry key indicates whether the Outlook 2010 installation is 32-bit or 64-bit. This might be useful to administrators who are interested in auditing computers to determine the installed versions of Office 2010 in their organization.

  • Registry path: HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0\Outlook

  • Registry key: Bitness

  • Value: either x86 or x64

Supported scenarios

The scenarios that are supported in the Office 2010 64-bit client are as follows.

  • Enterprise   In enterprise environments, the default is to install Office 2010 32-bit on computers that run either 32-bit or 64-bit editions of Windows operating systems.
 We recommend this option.

    An alternate approach in enterprise environments is for administrators to do the following:

    • Install Office 2010 32-bit on computers that run 32-bit editions of Windows.

    • Install Office 2010 64-bit on computers that run 64-bit editions of Windows to take advantage of additional memory on the 64-bit computers.

  • Retail   For users who install Office 2010 from DVDs onto computers that run a supported 64-bit Windows operating system, the installation is by default the 32-bit version of Office 2010 (WOW64).

    Retail users who run 64-bit Windows operating systems and do not have 32-bit Office products installed can install the native 64-bit version of Office 2010 from the x64 folder on the DVD.

  • Side-by-side installations   No support is provided for side-by-side installations of 64-bit and 32-bit editions of Office, including across applications. For example, there is no support for side-by-side installations of the 2007 Microsoft Office system 32-bit with Office 2010 64-bit, or for Microsoft SharePoint Workspace 2010 64-bit and Microsoft Excel 2010 32-bit.

  • Upgrades   The Office client upgrade scenarios are as follows:


    • A 2007 Office system 32-bit installation on a computer that runs a 32-bit Windows operating system can be upgraded to an Office 2010 32-bit version.


    • A 2007 Office system installation on a computer that runs a 64-bit Windows operating system can be upgraded to an Office 2010 32-bit (WOW64).

    • A 2007 Office system installation cannot be upgraded to a native Office 2010 64-bit version.

Deployment considerations

Before you deploy 64-bit editions of Office 2010, you must evaluate the advantages and disadvantages and determine whether it is an appropriate deployment option for your specific environment. The following sections highlight benefits and issues that might affect compatibility, describe Outlook considerations, and list the applications that block and those that do not block a 64-bit Office 2010 installation.

A key consideration is that you cannot install native 64-bit Office 2010 on computers that have 32-bit Office applications and third-party add-ins installed. You must uninstall the 32-bit Office applications and add-ins before you can install 64-bit Office 2010. If you have 32-bit third-party Office applications and add-ins that are required for users, you can install the default option, which is 32-bit Office 2010 (WOW64 installation) on computers that run supported 64-bit editions of Windows. A list of applications that block and those that do not block a 64-bit Office 2010 is included. See Blocking and nonblocking Office applications in 64-bit installations.

In this section:

  • Advantages

  • Disadvantages

  • General feature deprecations

  • Considerations for Outlook applications

  • Blocking and nonblocking Office applications in 64-bit installations

Advantages

Running Office 2010 64-bit provides the following advantages:

  • Ability to use additional memory.

  • Excel 2010 can load much larger workbooks. Excel 2010 made updates to use 64-bit memory addressing to move beyond 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.

  • Enhanced default security protections through Hardware Data Execution Prevention (DEP).

Disadvantages

The following issues might affect compatibility:

  • Microsoft Access MDE/ADE/ACCDE files   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.

  • ActiveX controls and COM add-ins   ActiveX controls and add-in (COM) DLLs (dynamic link libraries) 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. Installations of 64-bit Office 2010 will run only 64-bit controls. Computers can have 64-bit and 32-bit controls installed, and 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 64-bit Office 2010. However, the functionality is available if you install 32-bit Office 2010.

  • In-place activation   The following issues might occur if there is not a match between the bitness of Office 2010 and registered applications:

    • An OLE server might not instantiate in place and might fail to open if the application registered is not the same bitness as the version of Office installed. (For example, if the OLE Server application is 32-bit and the version of Office installed is 64-bit.)

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

  • Graphics rendering   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.

  • Visual Basic for Applications (VBA)   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. For more information about VBA, see the “64-bit VBA Overview” and “Declare Statement” articles in the Microsoft Visual Basic for Applications online Help in Office applications.

  • Windows Mobile Device Center (WMDC) synchronization   WMDC does not synchronize with Microsoft Outlook 2010 if you use the 64-bit version of Outlook 2010. In such cases, an error message displays that states that there is no default mail client or the current mail client cannot fulfill the messaging. WMDC synchronizes correctly with the 32-bit version of Outlook 2010. To synchronize a Windows Phone with Outlook 2010 by using Windows Mobile Device Center, uninstall Outlook 2010 64-bit. Then use the original installer that you used to obtain Outlook 2010 64-bit to install Outlook 2010 32-bit. Outlook 2010 32-bit is the default option.

General feature deprecations

The following feature deprecations might affect compatibility:

  • Microsoft Access   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 the ReplicationConflictFunction Property. ReplicationConflictFunction is a Microsoft Visual Basic for Applications (VBA) routine in the running database that can be used to resolve synchronization conflicts. For more information, see “How to: Set Properties of Data Access Objects in Visual Basic” in Access 2007 Developer Reference (https://go.microsoft.com/fwlink/p/?LinkId=150854).

  • Publisher   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.

  • Word   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).

    WLL (Word Add-in libraries)   WLL files are deprecated for 32-bit Office 2010 and are not supported in 64-bit Office 2010.

Considerations for Outlook applications

If you developed 32-bit Messaging Application Programming Interface (MAPI) applications, add-ins, or macros for Outlook, there are actions that you should take to change and rebuild the 32-bit applications to run on a 64-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 64-bit) and the edition of Office 2010 (32- or 64-bit) that is installed on the computer, if Office is already installed on that computer.

Factors that determine the feasibility of installing a 32-bit or a 64-bit version of Outlook include the following:

  • You can install 32-bit Office 2010 and 32-bit Microsoft Outlook 2010 on a supported 32-bit or 64-bit edition of the Windows operating system. You can install the 64-bit version of Office 2010 and 64-bit Outlook 2010 only on a supported 64-bit operating system.

  • The default installation of Office 2010 on a 64-bit edition of the Windows operating system is 32-bit Office 2010.

  • 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. That is, 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 64-bit 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.

MAPI applications include stand-alone applications such as Microsoft Lync, Microsoft Office 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 Outlook applications for 32-bit and 64-bit platforms, see Building MAPI Applications on 32-bit and 64-bit Platforms (https://go.microsoft.com/fwlink/p/?LinkId=165489) and Developing Outlook 2010 Solutions for 32-Bit and 64-Bit Systems (https://go.microsoft.com/fwlink/p/?LinkId=208699).

Blocking and nonblocking Office applications in 64-bit installations

If 32-bit Office applications are installed on a computer, a 64-bit Office 2010 installation is blocked by default. The following section (Applications that block a 64-bit Office 2010 installation) lists the applications that block a 64-bit Office 2010 installation. The next section (Applications that do not block a 64-bit Office 2010 installation) lists exceptions; that is, applications that do not block the installation. In such cases, installation of 64-bit Office proceeds even if the listed 32-bit applications are installed on the computer.

Applications that block a 64-bit Office 2010 installation

The following applications block a 64-bit Office 2010 installation:

  • Microsoft Office Excel Viewer

  • Access database engine of Microsoft Access 2010

  • Microsoft Office 2010 (Click-to-run)

  • Compatibility Pack for the 2007 Office system

Applications that do not block a 64-bit Office 2010 installation

The following applications do not block a 64-bit Office 2010 installation:

  • Microsoft Visual Studio Web Authoring Component 2007

  • 2007 Microsoft Office system 64-bit components

  • Microsoft Office 2010 (OEM pre-installation)

  • Microsoft Office 2003 Web Components

  • Expressions Web Designer

  • Microsoft Office XP Web Components

  • Microsoft Expression Web 1

  • Microsoft Expression Web 1 Language Packs

  • Microsoft Expression Web 2

  • Microsoft Expression Web 2 Language Packs

  • Visual Basic for Applications 6.4 SDK

  • Visual Basic for Applications 6.4 SDK International Components

Setup process

This section describes the Setup sequence for a 64-bit Office client installation.

The Office 2010 installation DVD contains both the 32-bit and 64-bit versions of Office 2010 with two architecture-specific folders: one for 32-bit and one for 64-bit, as noted previously. Each of the architecture folders contains a Setup.exe file for the specific platform. There is also a Setup.exe file at the root folder. This is referred to as the platform chooser. The following figure shows the folder structure.

64-bit Office 2010 client DVD

The Setup sequence is the same as for a standard 32-bit Office client installation with the addition of specific checks that are performed for 64-bit Office 2010.

The following figure shows the checks that Setup performs for 64-bit installations.

Office 2010 Setup checks

The following figure shows how Setup determines whether to install the 32-bit or 64-bit version of Office 2010 when Setup is run from the root of the media source (DVD) that contains both the 32-bit and 64-bit versions of Office 2010.

Office 2010 Setup chooser

The following section summarizes the Setup sequence of events.

  1. Setup checks for 64-bit Office 2010 prerequisites.

    When you run Setup.exe from the x64 folder, Setup determines whether 32-bit Office applications are installed. If Setup detects 32-bit Office applications, it displays an error message that informs users that they must first uninstall all 32-bit Office applications if they want to continue with the installation of Office 2010 64-bit. The error message lists the installed 32-bit Office applications. If Setup does not detect 32-bit Office applications, it installs the 64-bit edition of Office 2010.

    Note

    When you run Setup.exe from the x86 folder, Setup determines whether there are 64-bit Office 2010 applications installed. If Setup detects 64-bit Office 2010, an error message is displayed and Setup is blocked. If Setup does not detect 64-bit Office 2010, it installs the 32-bit edition of Office 2010.
    Office Professional Plus 2010 and Microsoft Office Professional 2010 will also be available as a combination release (DVD media) that includes both the 32-bit and 64-bit editions of Office 2010. If Setup is run from the root folder of the Office 2010 DVD that contains both 32-bit and 64-bit Office 2010, Setup performs the installation as follows:

    • On a computer that runs a supported 32-bit edition of Windows, Setup installs the 32-bit edition of Office 2010.

    • On a computer that runs a supported 64-bit edition of Windows, Setup checks for installed 64-bit Office applications, and then continues as follows:

      • If no 64-bit Office applications are installed on the computer, Setup installs Office 2010 32-bit. Office 2010 32-bit is the default installation on a 64-bit Windows operating system (uses WOW). This also applies if the administrator upgrades an existing 32-bit Office installation.

      • If 64-bit Office applications are installed, Setup installs Office 2010 64-bit.

  2. Setup reads XML data.

  3. Setup builds the feature tree.

  4. Setup creates the local installation source.

  5. Setup installs Office 2010.

  6. Setup applies the 64-bit OCT customization .msp file.

  7. Setup applies software updates.

For more information about the Setup sequence, see Setup process in Setup architecture overview for Office 2010.

Assessing your current environment for application compatibility

Office 2010 provides the following new application compatibility tools to help IT professionals evaluate application compatibility issues:

  • Office Environment Assessment Tool (OEAT)   A tool that you can use to assess your existing environment before you deploy Office 2010. OEAT is designed to help you determine the kinds of add-ins and the extent to which add-ins for Microsoft Office applications are used in your environment. OEAT collects and reports add-in information about Microsoft Office 2000, Microsoft Office XP, Microsoft Office 2003, and the 2007 Microsoft Office system. It also determines the applications that interact with Office 2010 (by using COM) and provides a summary of the general state of the systems that are scanned. For more information, see Office Environment Assessment Tool (OEAT) user's guide for Office 2010.

  • Microsoft Office Code Compatibility Inspector   A tool that you can use in Excel 2010, PowerPoint 2010, Word 2010, and Microsoft Visual Studio 2008 to troubleshoot issues with Microsoft Visual Basic for Application (VBA) macros and add-ins. The tool scans your code for known compatibility issues, and then notifies you if it finds items in the code from the object model that have changed in some way or have been removed. The code inspector tools find code that is incompatible because of changes and deprecations in the Office 2010 object model. The inspector tools can be used to scan code for Declare statements and can update the statements so that they are compatible with the 64-bit version of Office 2010. For more information, see Microsoft Office Code Compatibility Inspector user's guide.

  • Office Migration Planning Manager (OMPM)   A tool for the 2007 Office system that can also be used to scan for conversion issues that are common to both the 2007 Office system and Office 2010. For more information, see Office Migration Planning Manager overview for Office 2010. A new version of OMPM for Office 2010 will be available shortly after the product releases.

For more information, see Office 2010 application compatibility guide.

Along with the introduction of 64-bit editions of Office 2010, Microsoft is releasing Microsoft Visual Basic for Applications 7.0 (VBA 7) to work with both 32-bit and 64-bit applications. For more information, see Compatibility Between the 32-bit and 64-bit Versions of Office 2010 (https://go.microsoft.com/fwlink/p/?LinkId=179546). The article discusses the changes that apply to the 64-bit version of Office 2010, introduces the new VBA 7 code base, and discusses compatibility issues between the 32-bit and 64-bit versions of Office 2010 and suggested solutions.

IT administrators can choose a version of Office 2010 (32- or 64-bit) client to download from the TechNet Evaluation Center’s Download Microsoft Office Professional Plus 2010 page. Developers can download Office 2010 from the MSDN Evaluation Center’s Download Microsoft Office Professional Plus 2010 page. Note that the recommended version is the 32-bit edition of Office 2010 in most scenarios. See the Introduction section for recommendations on which version of Office 2010 to install.