Microsoft warns against using 64-bit Office 2010


Recommended Posts

Microsoft is advising its customers to install the 32-bit, rather than the 64-bit, version of Office 2010.

The advice is tucked away in an FAQ about the Office 2010 Tech Guarantee programme, which will ensure that buyers of Office 2007 will get a free upgrade to the new Office suite when its launched.

From the FAQ:

Will a 64-bit version of the Office 2010 product be available?

Yes, 64-bit Office 2010 product upgrades will be available. However we strongly recommend most users install 32-bit version of Office 2010 on both 32 and 64-bit Operating Systems because currently many common add-ins for Office will not function in the 64-bit edition. The 64-bit installation of Microsoft Office 2010 products will be available for users who commonly use very large documents or data set and need Excel 2010 programs to access greater than 2GB of memory. There may be technical issues with the 64-bit version and in order to install a 64-bit version of Office 2010 product users must have a 64-bit supported operating system on their PC.

"We strongly recommend most users install 32-bit version of Office 2010 on both 32 and 64-bit operating systems because currently many common add-ins for Office will not function in the 64-bit edition," Microsoft warns.

"The 64-bit installation of Microsoft Office 2010 products will be available for users who commonly use very large documents or data sets and need Excel 2010 programs to access greater than 2GB of memory.

"There may be technical issues with the 64-bit version and in order to install a 64-bit version of Office 2010 product users must have a 64-bit supported operating system on their PC," Microsoft adds.

Even some of Microsoft's own Office plugins are not yet compatible with the 64-bit software, including the Outlook Social Connector, which hooks the software into social networks such as Facebook. Third party plugins from LinkedIn and Symantec are also 32-bit only.

Source : PCPro

Looks like I'm safe to use 64-bit Office....I never use any add-ins in office.....I simply install Word, Excel and Powerpoint and use them as-is.

Now, I probably do not need to use 64-bit Office, as I doubt I will be opening large files, but I prefer to run 64-bit software on a 64-bit OS.

Using 64bit programs just for the sake of it is stupid anyway.. People that go out of their way to find only 64bit programs that gives them no advantage, and often carries it's own problems like the ones MS just stated, general compatibility, in addition to being on average more prone to bugs due the code being less tested ( by the test of time, or by general release ).

I don't need add-ins so 64bit version is not an issue for me.

I will assume you dont 'use very large documents or data set and need Excel 2010 programs to access greater than 2GB of memory' either lol.

Having win 7 x64 I will go with 32bit office 2010 because the probability of me needing add-ins is higher than me needing to use documents that exceed 2gigs of memory :p

I don't need add-ins, or work with 2GB+ files, but this bit concerns me.

"There may be technical issues with the 64-bit version"

I wouldn't expect to see any more issues than with the 32bit version, unless I'm just misreading this and it's just elaborating more on the add-ins bit.

The only issue I have noted with the 64-bit version is that outlook refuses to sync with mobile phones. Both my windows mobile and android phone is affected. However the ability to work with a couple of hundred thousand data points in excel and plot them more than makes up for that issue.

Yeah, I don't use add ins either... But this is an interesting point. I hope add ins get updated soon to work with 64 bit, because this could really be an issue for people that don't see this warning...

I will assume you dont 'use very large documents or data set and need Excel 2010 programs to access greater than 2GB of memory' either lol.

Having win 7 x64 I will go with 32bit office 2010 because the probability of me needing add-ins is higher than me needing to use documents that exceed 2gigs of memory :p

Yeah, I have to say that that would be a heck of a large document... I can't imagine. LOL

Designers and stuff I'm sure get large files sometimes, but wow...

because this could really be an issue for people that don't see this warning...

Probably not. The Office 2010 setup will install the 32-bit version by default; you have to actively browse to and manually run the 64-bit setup. So most people who know to install the 64-bit version (like people on Neowin) will probably be aware of its potential disadvantages.

Using 64bit programs just for the sake of it is stupid anyway.. People that go out of their way to find only 64bit programs that gives them no advantage, and often carries it's own problems like the ones MS just stated, general compatibility, in addition to being on average more prone to bugs due the code being less tested ( by the test of time, or by general release ).

I doubt that there is no "advantage"... I would bet that 64bit Office loads quicker and runs better than it's 32bit counterpart. Most 64bit apps do run better and faster than their 32bit counterparts. At least that's what I see. While add-ins are not 64bit, there are probably a lot of companies that can probably use the advantages of 64bit, so I doubt it will take too long for development of 64bit add-ins.

I would love to see more development of 64bit personally. I would love to see flash go 64bit because on my system 64bit IE runs a lot faster than 32bit IE (I bet other browsers would too) and frankly I bet flash would run a whole lot better as well (as long as they do it right).

I would bet that 64bit Office loads quicker and runs better than it's 32bit counterpart. Most 64bit apps do run better and faster than their 32bit counterparts. At least that's what I see.

What you "see" is probably what you want to see. The 64-bit versions may even startup slower since they have to allocate more memory, but the slow step in startup will be file IO, so ultimately I would expect very little difference between the two. Go to the Office 2010 team blogs; they say very frankly that the 64-bit code is often slower than the 32-bit counterparts, but sometimes faster. They note that Excel consumes up to 1.5 times more memory on x64 when doing the same tasks as the 32-bit version.

Certain 64-bit applications clearly benefit from proper 64-bit coding: all cryptography operations can be optimized, imaging applications can perform filters faster, etc. But don't make the mistake that 64-bit code = faster code; it's simply a widespread misconception. And how many of you are actually doing real-world time-measurement comparisons with the 64-bit versus 32-bit versions of Office 2010? I'll answer that: none of you are.

What you "see" is probably what you want to see. The 64-bit versions may even startup slower since they have to allocate more memory, but the slow step in startup will be file IO, so ultimately I would expect very little difference between the two. Go to the Office 2010 team blogs; they say very frankly that the 64-bit code is often slower than the 32-bit counterparts, but sometimes faster. They note that Excel consumes up to 1.5 times more memory on x64 when doing the same tasks as the 32-bit version.

Certain 64-bit applications clearly benefit from proper 64-bit coding: all cryptography operations can be optimized, imaging applications can perform filters faster, etc. But don't make the mistake that 64-bit code = faster code; it's simply a widespread misconception. And how many of you are actually doing real-world time-measurement comparisons with the 64-bit versus 32-bit versions of Office 2010? I'll answer that: none of you are.

Well, assuming I won't want/need any plugins for the various office programs, why would I want to use 32bits on a 64bits Windows?

You're forgetting that 32 bits programs use the WOW64 compatibility layer which does indeed makes more calls for every Windows API call.

People often compare 32 bits to 64 bits forgetting that some programs use assembly optimizations on 32bits and NO optimizations (yet) on 64bits.

What you "see" is probably what you want to see. The 64-bit versions may even startup slower since they have to allocate more memory, but the slow step in startup will be file IO, so ultimately I would expect very little difference between the two. Go to the Office 2010 team blogs; they say very frankly that the 64-bit code is often slower than the 32-bit counterparts, but sometimes faster. They note that Excel consumes up to 1.5 times more memory on x64 when doing the same tasks as the 32-bit version.

Certain 64-bit applications clearly benefit from proper 64-bit coding: all cryptography operations can be optimized, imaging applications can perform filters faster, etc. But don't make the mistake that 64-bit code = faster code; it's simply a widespread misconception. And how many of you are actually doing real-world time-measurement comparisons with the 64-bit versus 32-bit versions of Office 2010? I'll answer that: none of you are.

Yeah I learned that right away, I absolutely saw no difference in my use for Windows 64 but I simply was pushing the 2GB physical ram barrier on my previous notebook so I got this ASUS that came with 4GB.

Well, assuming I won't want/need any plugins for the various office programs, why would I want to use 32bits on a 64bits Windows?

You wouldn't and I didn't make that recommendation. I just said that you shouldn't expect some blazing increase in speed. If you do, you'll be disappointed.

If you buy it on a DVD, both 32-bit and 64-bit versions of Office 2010 will be available. If you install 32-bit Office, for example, and you decide later you want to use 64-bit Office instead, the 32-bit version must be uninstalled (it?s as simple as uninstalling any other program) before installing the 64-bit version.

On the DVD, you?ll notice that the file structure looks like this:

image_2.png

On a computer with no Office products installed, the setup.exe file denoted by the red arrow is the ?platform selector.? If you run it, it will automatically install 32-bit Office 2010 by default, even on 64-bit Windows. The only time it will install 64-bit Office is if it detects 64-bit Office already installed on your computer. If you want to install 64-bit Office, then open the x64 folder and run setup.exe from there. Similarly, running the setup.exe file in the x86 folder will install 32-bit Office directly.

You?ll see these instructions if you run setup.exe on 64-bit Windows, select Customize, and click on the Platform tab.

image_4.png

There you have it. Most people 64-bit Windows users will install Office 2010 32-bit by default.

  • Like 1

Using 64bit programs just for the sake of it is stupid anyway.. People that go out of their way to find only 64bit programs that gives them no advantage, and often carries it's own problems like the ones MS just stated, general compatibility, in addition to being on average more prone to bugs due the code being less tested ( by the test of time, or by general release ).

So you are saying I should use 32-bit version even though a stable 64-bit version is available and runs fine for me but gives no real performance advantages? When are we going to change to 64-bit software then? When all applications are made readily for 64-bit? And how is that going to happen if everybody keeps using 32-bit versions and not asking for a change or increased 64-bit support?

The news post clearly stated Microsoft stance on this, if you need to run plug-ins run the 32-bit version. If you have huge datasets and documents, use the 64-bit version. As I don't have any plug-ins for Office now, I don't see why I should not run the 64-bit version (if I upgrade).

Even gamers are switching to Windows 7 64-bit. On Steam the number of 64-bit installations are more than double that of the 32-bit version. That makes for a large base of 64-bit support for games in the future. Which could be beneficial for some games allowing memory addressing over 2GB.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Win11Debloat 2026.06.14 by Razvan Serea Win11Debloat is a lightweight, easy to use PowerShell script that allows you to quickly declutter and customize your Windows experience. It can remove pre-installed bloatware apps, disable telemetry, remove intrusive interface elements and much more. The script also includes many features that system administrators and power users will enjoy. Such as a powerful command-line interface, support for Windows Audit mode and the option to make changes to other Windows users. All changes made by Win11Debloat can be easily reversed, and most removed apps can be restored via the Microsoft Store. A full guide on how to undo the changes is available here. Win11Debloat features: Below is an overview of the key features and functionality offered by Win11Debloat. Please refer to the wiki for more information about the default settings preset. Remove a wide variety of preinstalled apps. Click here for more info. Disable telemetry, diagnostic data, activity history, app-launch tracking & targeted ads. Disable tips, tricks, suggestions & ads across Windows. Disable Windows location services & app location access. Disable Find My Device location tracking. Disable 'Windows Spotlight' and tips & tricks on the lock screen. Disable 'Windows Spotlight' desktop background option. Disable ads, suggestions and the MSN news feed in Microsoft Edge. Hide Microsoft 365 ads on the Settings 'Home' page, or hide the 'Home' page entirely. Disable & remove Microsoft Copilot. Disable Windows Recall. Disable Click to Do, AI text & image analysis tool. Prevent AI service (WSAIFabricSvc) from starting automatically. Disable AI Features in Edge. Disable AI Features in Paint. Disable AI Features in Notepad. Disable the Drag Tray for sharing & moving files. Restore the old Windows 10 style context menu. Turn off Enhance Pointer Precision, also known as mouse acceleration. Disable the Sticky Keys keyboard shortcut. Disable Storage Sense automatic disk cleanup. Disable fast start-up to ensure a full shutdown. ...and more. Once you’ve downloaded the Win11Debloat file (Get.ps1), just follow these quick steps: Locate the Get.ps1 script file. Right-click the file and select Run with PowerShell from the context menu. If prompted by User Account Control (UAC), select Yes to grant the script the necessary administrative permissions. Win11Debloat 2026.06.14 changes: This is a minor release that hopefully addresses the false positives in Windows Defender and Bitdefender that prevented users from downloading and/or running Win11Debloat. Refactor Get-RegFileOperations.ps1 to address false positives by @Raphire in #626 Add logging around WinGet app retrieval and increase timeout to 20s by @Raphire Download: Win11Debloat 2026.06.14 | Open Source View: Win11Debloat Home Page | Screenshots 1| 2 Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Still using Microsoft Money 2005 in 2026 here!
    • I have a couple to mention, and they still run great on Windows 11 Adobe Lightroom Version 2 Alcohol 120% CLZ Book, Comic, Game, Movie, & Music Collector (PC - No longer sold / Grandfathered in - now mobile apps/online only) DVDDecrypter ISO Buster Pro version 1.9.1 (Still supports HD-DVD too) Nero Burning Rom 8 (Only the burning software, no backup, media converter, etc)   OpenAL (Runtime) - GuildWars 1 Reforged still uses it for 3d headphone audio PowerDVD 12 Ultra SPTD (SCSI Pass through Direct Driver) UltraISO Windows Media Encoder 9 WinImage You can tell I still sport an optical drive    
    • Linux 7.1 arrives with an NTFS overhaul and major hardware performance boosts by Paul Hill The founder of the Linux kernel has just announced the availability of Linux 7.1. This is a stable version of the kernel that will now be tested by various Linux distributions before it is shipped to users through update managers. Some users, like those on Debian, for example, might not get it for a long time, if at all, while Fedora users can expect it in the near future. With Linux 7.1 out on time, the merge window for Linux 7.2 is now open, giving contributors the opportunity to send in major new features that have been waiting for the last two months. Torvalds warned that he is currently travelling and will be in another timezone, so timing for the merge window may be irregular due to timezone differences and limited internet access. Torvalds said that he has already fetched early pull requests to allow him to do some offline work, but the travel could still cause disruption. Right now, he is not planning to extend the release, but did consider it. He said he might later regret not extending, though. In terms of this last week of development for Linux 7.1, Torvalds said there were no major or alarming changes. This week consisted mostly of smaller driver updates to GPU, networking, and sound, networking fixes, trace tooling fixes, and misc minor fixes. The shortlog this week lists fixes for driver bugs, memory leaks, I/O and USB fixes, networking and RDMA fixes, DRM/graphics fixes, and tooling and verification improvements. Specific fixes include USB series heap-overflow and buffer overflow fixes, and multiple use-after-free, memory-leak, and refcount corrections across subsystems such as i2c, zram, gpio, and net. There are fixes for graphics drivers, including amdgpu, i915, and virtio, as well as hypervisor and virtualization tweaks affecting mshv, vmbus, and hyperv. According to Phoronix, anyone running Linux 7.1 should look out for the new NTFS driver, Intel FRED for improved performance on Panther Lake and future CPUs, faster graphics with Intel Arc Battlemage, and improvements for older AMD Radeon GPUs. If you are running Linux on your computer and everything is fine, then you don’t need to worry about updating to Linux 7.1 as a priority; just wait for it to be pushed to you. If you have tried Linux on hardware but it didn’t work properly, trying again with a distro that uses Linux 7.1 could cause Linux to work on your machine, thanks to the new hardware support.
    • you can also do this with this tool: PowerSettingsExplorer made by mbk1969 at 3dguru forum.. I found it by accident researching on modern standby and annoying quirks of it in 2022
  • Recent Achievements

    • Week One Done
      Jeroen Wilms earned a badge
      Week One Done
    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      507
    2. 2
      +Edouard
      197
    3. 3
      PsYcHoKiLLa
      139
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      81
  • Tell a friend

    Love Neowin? Tell a friend!