Click here to Skip to main content
Click here to Skip to main content

Why does WoW64 use register and file system redirection?

, 22 Mar 2012 CPOL
Rate this:
Please Sign up or sign in to vote.
So, why does WoW64 employ the mechanism of redirecting the register and file system instead of simply assigning the obsolete register keys and "%windir%\system32" to 32-bit applications and allowing 64-bit applications to define new keys and use, for instance, "%windir%\system64" for 64-bit system l

So, why does WoW64 employ the mechanism of redirecting the register and file system instead of simply assigning the obsolete register keys and "%windir%\system32" to 32-bit applications and allowing 64-bit applications to define new keys and use, for instance, "%windir%\system64" for 64-bit system libraries? It would be rather logical especially if to remember that something similar was done when moving from Windows 3.x to Windows 95/NT.

A bit of history at first. The first Itanium was released in 2001. At the same time the first version of Windows XP 64-bit Edition for Itanium systems appeared. The first 64-bit processors by AMD appeared two years later - in 2003. And two more years later - in 2005 - Windows XP Professional x64 Edition was released. So, Itanium had been a target 64-bit platform long before AMD64 processors appeared.

Unlike x64 (AMD64), the difference between 32-bit and 64-bit code on Itanium (IA-64) is huge. Execution of x86 instructions is either emulated by the chip itself (it is a so called x86 hardware support) or the program emulator IA-32 EL. In the both cases, the mechanism of executing 32-bit applications is very similar to a virtual machine and therefore implies low performance of 32-bit applications. So, Intel makes it abundantly clear that support of 32-bit applications exists only to simplify the process of moving to 64-bit software. It did not mean to be long because there are just a couple of main applications running on a server unlike customer desktops where there are hundreds of programs of unknown origin.

Well, let us put Itanium aside for a while and look at the second factor - the complexity of porting applications to a 64-bit platform. Microsoft tried to make this port as smooth as possible. Actually, it were just enough to recompile an existing 32-bit application with a 64-bit compiler and that is all. But in practice it is not so easy of course - basically because programmers do not follow all the recommendations 100%. There will always be somebody who would like to "cut off a corner", and such optimization turns out badly then.

Now we may answer the question put in the title. We need to virtualize the register and file system because the names of the register keys and disk catalogues used by an application being recompiled remain the same after recompilation as these are just text constants in the program code. Well, it is not so bad with catalogues on the disk though, because you may (and must) get the names of the most system catalogues with the help of the functions GetSystemDirectory, GetWindowsDirectory, SHGetFolderPath and the like. But in case of "System32" it was too bad, because the fixed "System32" was everywhere.

All in all, it was clear that mere recompilation was not enough while search and correct replacement of many string constants in all the applications intended to be ported promised if not to cost much money but at least significantly slow down the process of moving to a new platform. The main problem was not to change the code but to convince software developers to do it. Solving this problem with the least troubles (i.e. using redirection in WoW64) seemed very nice.

As AMD64 appeared - or perhaps it was explained by rather poor sales of Itanium (in comparison with the forecast) - the move to a platform free from 32-bit applications dragged. Most applications are still 32-bit and there is no bottom to it.

All this resulted in what we can see now. Windows XP and Vista x64 has inherited the architecture WoW64 from Windows XP 64-bit Edition for Itanium systems, the move to pure 64-bit systems is dragging while people begin to notice some architectural contradictions (despite which, we should say, the system works rather well).


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Karpov Andrey
Architect Program Verification Systems, Co Ltd
Russian Federation Russian Federation

Andrey Karpov is technical manager of the OOO "Program Verification Systems" (Co Ltd) company developing the PVS-Studio tool which is a package of static code analyzers integrating into the Visual Studio development environment.

PVS-Studio is a static analyzer that detects errors in source code of C/C++ applications. There are 3 sets of rules included into PVS-Studio:

  1. Diagnosis of 64-bit errors (Viva64)
  2. Diagnosis of parallel errors (VivaMP)
  3. General-purpose diagnosis

Awards: MVP, Intel Black Belt

Andrey Karpov is also the author of many articles on the topic of 64-bit and parallel software development. To learn more about the PVS-Studio tool and sources concerning 64-bit and parallel software development, please visit the site.

Best Articles:

My page on LinkedIn site:

E-mail: karpov@viva64(dot)com

Follow on   Twitter

Comments and Discussions

-- There are no messages in this forum --
| Advertise | Privacy | Mobile
Web01 | 2.8.141015.1 | Last Updated 23 Mar 2012
Article Copyright 2012 by Karpov Andrey
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid