Summary
Locations used within a 64bit Windows OS to determine a 32 or 64bit application.
Synopsis
Microsoft designed 64-bit versions of Windows to allow existing 32-bit applications to work seamlessly on 64-bit versions of Windows. They also designed 64-bit versions of Windows in such a way to allow a recompiled version of the same code to work seamlessly as a 64-bit application.
In some cases, such as installation, what is normally a beneficial separation becomes a challenge. Typically installers are 32-bit applications themselves (in order to run on 32-bit machines), and accessing 64-bit locations to install a 64-bit application is more complex than a standard file copy or registry write.
Discussion
To provide support for allowing existing 32-bit applications to work on 64-bit versions of Windows, most 64-bit versions of Windows use 32-bit Windows-on-Windows (WOW64) emulation. This WOW64 emulation support isolates the 32-bit and 64-bit files from each other by storing their files in separate locations.
A 64-bit target system typically has two Program Files folders:
- Program Files, which is for 64-bit applications
- Program Files (x86), which is for 32-bit applications
A 64-bit target system typically has two Common Files folders (one in either Program Files folder):
- Program Files\Common Files, which is for 64-bit applications
- Program Files (x86)\Common Files, which is for 32-bit applications
A 64-bit target system also typically has two system folders:
- System32, which is for 64-bit libraries and executable files
- SysWOW64, which is for 32-bit libraries and executable files
Thus, if an end user runs a 32-bit installer on a 64-bit version of Windows that uses WOW64 emulation, files that you may want to be installed to 64-bit file locations may be redirected to 32-bit file locations (such as Program Files x86). However, on 32-bit systems, such files are installed to Program Files.
The isolation of 32-bit and 64-bit data from each other on 64-bit systems also occurs in the registry. A 64-bit target system typically has two HKEY_LOCAL_MACHINE\Software keys:
- HKLM\Software, which is for 64-bit applications
- HKLM\Software\Wow6432Node, which is for 32-bit applications
Thus, if an end user runs a 32-bit installer on a 64-bit version of Windows that uses WOW64 emulation, registry data that you may want to be installed to 64-bit HKLM\Software locations may be redirected to HKLM\Software\Wow6432Node. On 32-bit systems, such registry data are installed to HKLM\Software.
Related Articles
Installing 32bit lmadmin to "Program Files (x86)" folder on 64bit Windows prevents starting it as a service 3Number of Views 32-bit and 64-bit Installation Support 8Number of Views Install Condition to determine a 32bit or 64bit Machine 6Number of Views Syntax for Specifying a Different Trusted Storage Location for Windows and Linux-Based Platform Other Than Using the Defau… 14Number of Views Locations of Flexera agent logs on Linux and Windows 6Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago