Skip to main content

How to Force a Command to Run in 32-bit or 64-bit CMD in Batch Script

On a 64-bit version of Windows, the operating system cleverly maintains two separate versions of the command processor (cmd.exe) and many core system utilities. This compatibility layer, known as WoW64 (Windows on Windows 64-bit), allows you to run older 32-bit command-line applications seamlessly. However, in some advanced scripting scenarios, you need to explicitly control which version of cmd.exe your command runs in.

This guide will teach you the fundamental concept of the System32 and SysWOW64 folders. You will learn the correct paths to call the 32-bit and 64-bit versions of cmd.exe and see a practical example of why this is critical for interacting with the 32-bit parts of the Windows Registry.

The Core Concept: System32 vs. SysWOW64​

This is the most important and most confusing part of the 32/64-bit distinction on Windows. The folder names are the opposite of what you would expect.

On a 64-bit version of Windows:

  • C:\Windows\System32: This folder contains the 64-bit executables.
  • C:\Windows\SysWOW64: This folder contains the 32-bit executables.

When you run a 32-bit application on 64-bit Windows, a "File System Redirector" automatically and transparently redirects any calls from the 32-bit app to System32 over to the SysWOW64 folder instead. This is why a 32-bit program can run without knowing it's on a 64-bit OS.

Our goal in scripting is to bypass this redirection by explicitly calling the cmd.exe from the folder we need.

The Path to the 64-bit cmd.exe​

On a 64-bit OS, the standard cmd.exe you get when you open a command prompt is the 64-bit version. Its explicit path is:

%windir%\System32\cmd.exe

The Path to the 32-bit cmd.exe​

To run a command in a 32-bit context, you must explicitly call the cmd.exe that lives in the SysWOW64 folder.

%windir%\SysWOW64\cmd.exe

You can use these full paths with the /C switch (which tells cmd.exe to run a command and then terminate) to force a command into the desired context.

Basic Example: Demonstrating the Difference​

This script uses the PROCESSOR_ARCHITECTURE environment variable to prove which version of cmd.exe is running the command.

@ECHO OFF
ECHO --- Checking Command Processor Architecture ---
ECHO.

ECHO --- Running in the Default (64-bit) Context ---
ECHO The current processor architecture is: %PROCESSOR_ARCHITECTURE%
ECHO.

ECHO --- Forcing a command to run in the 32-bit Context ---
%windir%\SysWOW64\cmd.exe /C "ECHO The processor architecture in this context is: %PROCESSOR_ARCHITECTURE%"

Output on a 64-bit OS:

--- Checking Command Processor Architecture ---

--- Running in the Default (64-bit) Context ---
The current processor architecture is: AMD64

--- Forcing a command to run in the 32-bit Context ---
The processor architecture in this context is: x86

This clearly shows that by calling the cmd.exe in SysWOW64, we successfully launched a 32-bit process.

How the File System Redirector Works​

The redirection is what makes the folder names so confusing.

  • A 64-bit process sees the file system normally: System32 is for 64-bit, SysWOW64 is for 32-bit.
  • A 32-bit process sees a "lie." When it tries to look at C:\Windows\System32, the redirector automatically shows it the contents of C:\Windows\SysWOW64 instead.

By calling %windir%\SysWOW64\cmd.exe, our batch script (which is a 64-bit process) is directly launching the 32-bit executable, bypassing any redirection for that launch command.

Common Pitfalls and How to Solve Them​

Problem: This Only Applies to 64-bit Windows​

The SysWOW64 folder and the 32-bit cmd.exe do not exist on a 32-bit version of Windows. If you try to run %windir%\SysWOW64\cmd.exe on a 32-bit OS, it will fail with a "path not found" error.

Solution: Your script must first check if it's running on a 64-bit OS before attempting to call the 32-bit command processor.

IF NOT DEFINED ProgramFiles(x86) (
    ECHO This is a 32-bit OS. Cannot force 32-bit context.
    GOTO :EOF
)

ECHO This is a 64-bit OS. It is safe to call the SysWOW64 cmd.exe.
%windir%\SysWOW64\cmd.exe /C "my_command"

Practical Example: Accessing the 32-bit ODBC Registry​

This is the most common reason to force the context. On a 64-bit OS, the registry is also split. There is a special "Wow6432Node" for 32-bit applications. If you need to read or write a registry key for a 32-bit application, you must use the 32-bit version of reg.exe.

The easiest way to do this is to run the REG command from the 32-bit cmd.exe.

This script reads the 32-bit ODBC data sources from the registry, which are invisible to the standard 64-bit REG command.

@ECHO OFF
SETLOCAL
SET "RegKey_32bit=HKLM\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources"

ECHO --- Reading the 32-bit ODBC DSNs ---
ECHO This is only possible from a 32-bit context.
ECHO.

IF NOT DEFINED ProgramFiles(x86) (
    ECHO This is a 32-bit OS. The key is at the standard location.
    REG QUERY "HKLM\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources"
    GOTO :End
)

REM --- On a 64-bit OS, we must use the 32-bit cmd.exe ---
%windir%\SysWOW64\cmd.exe /C "REG QUERY ""%RegKey_32bit%"""

:End
ENDLOCAL

This script intelligently adapts. On a 32-bit OS, it queries the normal registry path. On a 64-bit OS, it uses the 32-bit command processor to correctly query the redirected registry path.

Conclusion​

While most scripts can run without worrying about the processor architecture, knowing how to force a command into a specific 32-bit or 64-bit context is an essential skill for advanced system administration.

Key takeaways:

  • On a 64-bit OS, System32 contains 64-bit files, and SysWOW64 contains 32-bit files.
  • To run a command in a 32-bit context, you must explicitly call %windir%\SysWOW64\cmd.exe /C "your_command".
  • This is most often required when you need to interact with the 32-bit file system or registry from a 64-bit script (e.g., accessing HKLM\SOFTWARE\Wow6432Node).
  • Always check if you are on a 64-bit OS (IF DEFINED ProgramFiles(x86)) before attempting to call the 32-bit cmd.exe.

Table of Contents