32-bit and 64-bit explained

Will this 32-bit software run on my 64-bit operating system? or

Will this 64-bit software run on my computer?

If you've asked these questions then this tutorial should help you to understand the concepts of 32-bit and 64-bit computing. We'll look at your computer system as three parts: the hardware, the operating system and the application programs. At the end we'll look at some of the common questions people have.

32-bit versus 64-bit

As the number of bits increases there are two important benefits.

  • More bits means that data can be processed in larger chunks which also means more accurately.
  • More bits means our system can point to or address a larger number of locations in physical memory.

32-bit systems were once desired because they could address (point to) 4 Gigabytes (GB) of memory in one go. Some modern applications require more than 4 GB of memory to complete their tasks so 64-bit systems are now becoming more attractive because they can potentially address up to 4 billion times that many locations.

Since 1995, when Windows 95 was introduced with support for 32-bit applications, most of the software and operating system code has been 32-bit compatible.

Here is the problem, while most of the software available today is 32-bit, the processors we buy are almost all 64-bit.

So how long will the transition from 32-bit to 64-bit systems take?

The main issue is that your computer works from the hardware such as the processor (or CPU, as it is called), through the operating system (OS), to the highest level which is your applications. So the computer hardware is designed first, the matching operating systems are developed, and finally the applications appear.

We can look back at the transition from 16-bit to 32-bit Windows on 32-bit processors. It took 10 years (from 1985 to 1995) to get a 32-bit operating system and even now, more than 15 years later, there are many people still using 16-bit Windows applications on older versions of Windows.

The hardware and software vendors learnt from the previous transition, so the new operating systems have been released at the same time as the new processors. The problem this time is that there haven't been enough 64-bit applications. Ten years after the PC's first 64-bit processors, installs of 64-bit Windows finally exceeded installs of 32-bit Windows. Further evidence of this inertia is that you are probably reading this tutorial because you are looking to install your first 64-bit software.

Your computer system in three parts

Now we'll look at those three components of your system. In simple terms they are three layers with the processor or CPU as the central or lowest layer and the application as the outermost or highest layer as shown below:

Processor, OS and application hierarchy

To run a 64-bit operating system you need support from the lower level: the 64-bit CPU.

To run a 64-bit application you need support from all lower levels: the 64-bit OS and the 64-bit CPU.

This simplification will be enough for us to look what happens when we mix the 32-bit and 64-bit parts. But if you want to understand the issue more deeply then you will also need to consider the hardware that supports the CPU and the device drivers that allow the OS and the applications to interface with the system hardware.

What 32-bit and 64-bit combinations are compatible and will work together?

This is where we get to the practicalities and can start answering common questions.

The general rule is that 32-bit will run on a lower level 64-bit component but 64-bit does not run on a lower level 32-bit component:

  • A 32-bit OS will run on a 32-bit or 64-bit processor without any problem.
  • A 32-bit application will run on a 32-bit or 64-bit OS without any problem.
  • But a 64-bit application will only run on a 64-bit OS and a 64-bit OS will only run on a 64-bit processor.

These two tables illustrate the same rule:

Table 1 — What is compatible if I have a 32-bit CPU?
Processor (CPU) 32-bit 32-bit 32-bit 32-bit
Operating System (OS) 32-bit 32-bit 64-bit 64-bit
Application Program 32-bit 64-bit 32-bit 64-bit
  Yes No No No
 
Table 2 — What is compatible if I have a 64-bit CPU?
Processor (CPU) 64-bit 64-bit 64-bit 64-bit
Operating System (OS) 64-bit 64-bit 32-bit 32-bit
Application Program 64-bit 32-bit 32-bit 64-bit
  Yes Yes Yes No

The main reason that 32-bit will always run on 64-bit is that the 64-bit components have been designed to work that way. So the newer 64-bit systems are backward-compatible with the 32-bit systems (which is the main reason most of us haven't moved to 64-bit software).

An example of backward compatibility is Windows 64-bit. It has software called WOW64 that provides compatibility by emulating a 32-bit system. See the article How Windows 7 / Vista 64 Support 32-bit Applications if you want to know more. One important point that is made in that article is that it is not possible to install a 32-bit device driver on a 64-bit operating system. This is because device drivers run in parallel to the operating system. The emulation is done at the operating system level so it is available to the higher layer, the application, but it is not available to the device driver which runs on the same level.

Hardware virtualization is the exception to the rule

Another question many people have is whether a 32-bit system can run 64-bit software. As more people are looking to use 64-bit Windows they are wanting to try it out on their existing systems. So we are getting more questions about whether they can run it on their 32-bit processor or under their 32-bit OS.

Following the general rule, we would expect that you cannot run 64-bit software on a 32-bit system. Except that there is one exception called virtualization.

Virtualization creates a virtual system within the actual system. Virtualization can be achieved in hardware or software but it works best if the virtual machine is created in the system hardware. The guest operating system is not aware that there is a host operating system already running. This is the way that a 64-bit operating system can think that it is running on 64-bit hardware without being aware that there is a 32-bit operating system in the mix.

Tables 3 and 4 illustrate the result. Provided that the virtual machine can actually be created and isolated by the virtualizing software then the host OS is effectively removed from the equation, so I've grayed it out. We can now apply the general rules for a non-virtualized system to the three remaining layers.

Table 3 — What is compatible if I have a 32-bit CPU and software virtualization?
Processor (CPU) 32-bit 32-bit 32-bit 32-bit
Host Operating System 32-bit 32-bit 32-bit 32-bit
Guest Operating System 32-bit 32-bit 64-bit 64-bit
Application Program 32-bit 64-bit 32-bit 64-bit
  Yes No No No
 
Table 4 — What is compatible if I have a 64-bit CPU and software virtualization?
Processor (CPU) 64-bit 64-bit 64-bit 64-bit
Host Operating System 32/64-bit 32/64-bit 32/64-bit 32/64-bit
Guest Operating System 64-bit 64-bit 32-bit 32-bit
Application Program 64-bit 32-bit 32-bit 64-bit
  Yes Yes Yes No

Before you hurry away to try running 64-bit in a virtual machine, you must check that your computer BIOS supports hardware virtualization. If it does not then hardware virtualization will not work even if the CPU does support it.

Emulation of the 64-bit CPU is not an option

All the feasible configurations that we have looked at so far have the processors (CPUs) running software that use the instruction set that is native to that processor. Running 64-bit software on a 32-bit processor doesn't work because the 64-bit instructions are not native to a 32-bit processor. But what if I could emulate a 64-bit processor using 32-bit software?

It is theoretically possible but practically impossible to emulate a 64-bit processor while running software on a 32-bit processor. Even if you can get non-native 64-bit emulation to work, the virtual machine that duplicates a 64-bit CPU would run very slowly because every 64-bit instruction has to be trapped and handled by the emulator. 64-bit memory pointers also have to be converted to work within the 32-bit address space.

Furthermore, my understanding is that the x86 (32-bit) processors used in PCs and Apple Macs are not able to completely emulate the x64 (64-bit) instruction set. Some 64-bit instructions cannot be trapped by the emulator. This causes the system to crash when the x86 processor tried to run those x64 instructions.

 

Answers to common questions about 32-bit and 64-bit systems

Will a 64-bit CPU run a 32-bit program on a 64-bit version of an OS?

Yes it will. 64-bit systems are backward-compatible with their 32-bit counterparts.

Will a 64-bit OS run a 32-bit application on a 64-bit processor?

Yes it will. Again, this is because of backward compatibility.

Can 64-bit applications contain 32-bit code?

Yes, many times 64-bit software will contain portions of 32-bit code.

Similarly 32-bit software (usually very old programs) can have some code in 16-bit which is why those 32-bit applications will usually fail to run properly on a 64-bit OS.

Can 16-bit applications or code run on 64-bit systems?

No, as we said previously. 16-bit code will NOT run on 64-bit OS because the designers did not provide backward-compatibility. This is one reason why some 32-bit programs will not work on 64-bit operating systems.

Can a 64-bit CPU with a 32-bit host OS run a virtual machine (VM) for a 64-bit guest OS?

Yes. It all depends upon the level of virtualization.

With software virtualization it is hardly likely to work, or if it does work it may be very slow.

Hardware virtualization will need to be supported by the CPU (e.g. with Intel-VT or AMD-V) and the BIOS.

 

Answers to common questions about 32- and 64-bit Windows

Can I run Windows 2000 and Windows XP on a 64-bit CPU, and use old software?

Yes, a 32-bit OS (Windows 2000 or XP) will run on a 64-bit processor.You should also be able to run older 32-bit software on a 64-bit OS.

Is a Windows Vista or Windows 7 license key valid for both 32-bit and 64-bit versions?

Yes, unless you have an OEM version. If it was installed on your computer when you bought it and you only have one Windows disk then it is almost certainly an OEM version and you will have to buy the other bit version if you want it. If you have two disks, one for 32-bit Windows and one for 64-bit Windows, then you have a non-OEM version so you get to choose which bit version you will use without having to buy another license. See Microsoft Answers for a discussion of these issues.

Remember, if you have only bought one license then, even if you have both bit versions on disk, you are only licensed to install and run one version on one computer.

How do find out if my system is 64-bit?

Microsoft provide resources to help you find out such as FAQ on 32-bit and 64-bit Windows and Taking the mystery our of 64-bit Windows.

I recommend that you look at downloading SecurAble from Gibson Research Corporation (GRC) which will tell you if you have a 64-bit processor with the useful features of hardware DEP and hardware virtualization.

How do I migrate my 32-bit system to 64-bit Windows?

There is no upgrade path from 32-bit to 64-bit Windows only from 64-bit Windows. You will almost certainly have to do a clean install of your 64-bit operating system, copy back your data files, and reinstall your 32-bit applications.

If you want to keep your old install then you can try dual booting or virtualization.

How do I run 32-bit software once I have installed 64-bit Windows?

Windows 7 64-bit provides a 32-bit compatibility mode called WOW32 (Windows 32-bit on Windows 64-bit) that should run most if not all your applications. See How Windows 64-bit supports 32-bit Applications.

If you have 32-bit application you want to run from the Command Prompt then you need to use the WOW64 version of cmd.exe. At the Start Menu select Run and enter the following command. Note that the %systemroot% variable points to your Windows folder so this will work even if Windows is not installed on C: drive:

%systemroot%\SysWOW64\cmd.exe

If your application won't run under Windows 64-bit then try XP Mode, Windows Virtual PC, or other virtualization solution. Be aware that XP Mode reduces your system security and so it should be used as a last resort.

How can I tell if my application is 32-bit or 64-bit?

There are a number of indicators of the bit type for your program but they are not definitive as you will see if you use guidelines like the following.

  • Windows installs your programs to these folders on your system drive:
    • '\Program Files' for 64-bit programs
    • '\Program Files (x86)' for 32-bit programs
  • In Task Manager, 32-bit processes will usually have a suffix of '*32' and 64-bit processes will not.

The reason that these indicators cannot be relied upon relates to the way 64-bit Windows installs software. 64-bit install packages usually install 64-bit applications or a mixture of 32- and 64-bit components but can even install only 32-bit components.

What determines where a component is installed is the registry setting for that component rather than the setting for the install package. Windows also assumes that all components are 32-bit unless told otherwise. This means that a 64-bit component not flagged as 64-bit will install to 32-bit folders and 32-bit registry keys but will execute as 64-bit.

You can, with the necessary knowledge, find the information yourself but there are better solutions:

  • Run a system information or audit tool such as Belarc Adviser. Just be aware that most of these types of applications are helpful but not definitive e.g. SIW, MSINFO.
  • Windows 64-bit Task Manager indicates 32-bit applicationsIf the software is running then you can use the Task Manager: As shown in the example screenshot, 32-bit processes are usually indicated with "(32-bit)" beside the name in Windows 8 or "*32" in Windows 7.
  • If you want more detail about the modules used by a program then try Dependency Walker, which is also part of Microsoft development tools such as Visual Studio and Visual C++. As with other software running under 64-bit Windows you will get the best results if you run the 32- or 64-bit version of Dependency Walker that matches the application you want to check. Remember that Windows 64-bit restricts access to the relevant 32-bit or 64-bit portions of the registry.
  • The Windows Software Development Kit (SDK) tool DumpBin can be used. If the SDK is installed run Windows SDK Command Prompt and enter the following command. Examples of the program path are "C:\Windows\System32\cmd.exe" which is the Windows command prompt and "C:\Program Files (x86)\Mozilla Firefox\Firefox.exe" which is a 32-bit web browser. The quotation marks are not needed unless the program path contains spaces like the Firefox example..
dumpbin /headers "program path"
  • Process Explorer can display process propertiesTools like Microsoft Process Explorer are often used to replace the Task Manager. They provide a lot more information and features. Process Explorer can display the process properties or you can add the Image Type column to the process view as in the screenshot to the right..
  • I used to recommend running the PowerShell script from Auditing 32-Bit and 64-Bit Applications with PowerShell. Unless you already use PowerShell this will be a lot more hassle. It lists all installed applications and their bitness where they are correctly registered in the registry. The script has been updated to have one version that runs in both 32-bit or 64-bit Windows but it now requires PowerShell 2.0. That's no problem if you are running Windows 7 or 8 but will have to be downloaded if your Windows version is XP or Vista. If you are a first time user of PowerShell then the following instructions will help you to get it going..

You can check the version by running PowerShell and typing the following command into the console. This example indicates version 4 because it is provided in Windows 8.1.:

PS C:\Users\Me> $PSVersionTable.PSVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
4      0      -1     -1

PowerShell scripts are restricted from running by default run the powershell console as administrator and temporarily allow the script to run by entering the command "set-executionpolicy unrestricted"  - you will have to confirm that you want to be able to run scripts. Then you will need to remember to turn it off with the command "set-executionpolicy restricted":

PS C:\WINDOWS\system32> set-executionpolicy unrestricted
Execution Policy Change
The execution policy helps protect you from scripts that you do not trust.
Changing the execution policy might expose you to the security risks described in 
the about_Execution_Policies help topic at http://go.microsoft.com/fwlink/?LinkID=135170.
Do you want to change the execution policy?
[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): Y


To run the script unzip "Get-InstalledApps.PS1.TXT" and remove the ".TXT" so Windows will recognize the application as PowerShell. Then create a shortcut to it and in the shortcut's Target field insert "powershell.exe -noexit" before the path to the file. You can also redirect the console text output to a text file by appending " > installedapps.txt". It's easier to browse the file than viewing it as it streams to the display.

What are the differences between Windows 32-bit and 64-bit?

I've chosen to highlight the physical and logical differences between each version of desktop Windows as shown in Table 5. This table illustrates the progressive improvement of Windows 64-bit and indicates that Windows has a long way to go before it exhausts the capabilities of 64-bit processors.

Many of the limits in the 64-bit versions of Windows are design choices rather than limitations of the 64-bit CPUs. The number of physical processors is the most obvious as Windows Server editions support many more.

Hardware is also limited by design. For example, while 64-bit AMD and Intel CPUs use 64-bit  memory pointers, the supporting chipsets only use a 52-bit physical address space (4 Petabytes) and a 48-bit virtual memory space (256 Terabytes). This is presently more than sufficient because Windows 7 64-bit only allows 192 GB of physical memory and 16 Terabytes (44-bits) of virtual memory.

Table 5: Physical and Logical limits for Windows Versions
Numbers in parentheses indicate extended settings that are not the default and require compatible hardware
Version: XP Vista 7
Version Bits: 32 64 32 64 32 64
System:            
Physical Processors 2 2 2 2 2 2
Logical Processors 32 64 32 64 32 256
System Cache 1 GB 1,024 GB 1 (2) GB 1,024 GB 1 (2) GB 1,024 GB
Physical Memory 4 GB 128 GB 4 GB 128 GB 4 GB 192 GB
Virtual Memory 4 GB 16,384 GB 4 GB 16,384 GB 4 GB 16,384 GB
Kernel 1 (2) GB 8 GB 2 GB 8 GB 2 GB 8 GB
User Process:            
Physical Memory 2 (3) GB 2 (4) GB 2 (3) GB 8 GB 2 (4) GB 8 GB
Virtual Memory 2 (3) GB 2 (8,192) GB 2 (3) GB 2 (8,192) GB 2 (4) GB 2 (8,192) GB

Note 1. I have used Gigabytes (GB) for consistency even though it would be convenient to convert  1,024 GB to 1 TB.

Note 2. I've excluded the first 64-bit version of Windows XP (2002) because it has a different architecture. It used Intel Itanium (IA-64) CPUs which had an x86 processor built-in for compatibility. It was replaced by AMD's 64-bit architecture (x86-64) which extended the x86 instruction set and worked so well that it has been licensed by Intel and other chip makers. The name is commonly shortened to x64 as it is the most common 64-bit CPU type today.

 

Related Links

Help with terminology

 

Share this
4.453685
Average: 4.5 (529 votes)
Your rating: None

Comments

by Remah on 13. July 2014 - 10:52  (117298)

This article has been updated with more examples of how to find out if software is 32-bit or 64-bit. Screenshots have been added for Task Manager and Process Explorer.

Remah - Article Editor

by exus69 on 10. April 2013 - 7:00  (106951)

Excellent article :) I think there's a small mistake in the following para. Please correct me if I am wrong. The original is as follows:

"One important point that is made in that article is that it is not possible to install a 32-bit device driver on a 64-bit operating system. This is because device drivers run in parallel to the operating system. The emulation is done at the operating system level so it is available to the higher layer, the application, but it is not available to the device driver which runs on the same level."

The corrected one, which I think should be is as follows:

"One important point that is made in that article is that it is not possible to install a 32-bit device driver on a 64-bit operating system. This is because device drivers run in parallel to the operating system. The emulation is done at the application program level so it is available to the higher layer, the application, but it is not available to the device driver which runs on the same level."

by Remah on 11. April 2013 - 5:48  (106981)

"The emulation is done at the operating system level" not at "the application program level". This is because the emulator has to intercept operating system calls. If the emulator were an application program then it would not normally have sufficient privilege to interfere with the operating system or to supervise other application programs.

Gizmo's Freeware is Recruiting!

Gizmos Needs YouShare your knowledge of free software with millions of Gizmo's readers by joining our editing team.  Details here.