Difference between System32 and SysWOW64 folders in Windows 11/10

Download PC Repair Tool to quickly discover & set up Windows errors automatically

If you have been using Windows Os for some fourth dimension, I am certain you must have seen this System32 folder. Nonetheless, If you are on a 64-bit PC, you must have noticed that there are ii folders in your C:\Windows directory. The first is System32 and the 2d is SysWOW64. In this post, nosotros are going to larn about them, and the difference between System32 and SysWOW64 folders in Windows 11/ten.

What is System32 folder?

The System32 binder all the organisation files. These are unremarkably DLL or library files. They are the nearly common programs used past applications to access Windows features. Apart from this, programs which install on your computer can as well store files inside it.

When you install a plan, two things happen on a broader level. The main program (EXE) is installed on Programs binder while its DLL (which packs in its functions etc.) are stored in System32 folders. This is mutual practice.

What is SysWOW64 folder?

Take you noticed a C:\Program Files (x86) binder on your 64-bit PC? Here x86 means 32-fleck. So to install 32-bit programs on a 64-bit automobile, C:\Program Files (x86) is used. WhileC:\Program Files folder contains 64-flake programs and their files.

Now you may be cartoon an illustration that the SysWOW64 folder must be containing only 64-bit DLLs. That was the actual intention, only it did not work out. If you manually check, there are a lot of 64-bit DLL in System 32 binder and 32-scrap DLL in SysWOW64 binder.

So why is a 32-bit marked folder having a 64-fleck folder, and why is a 64-bit marked folder housing all the 32-flake DLLs?

Read: What is splwow64.exe process?

Departure between System32 and SysWOW64 folders

Both are system folders, and they contain organisation-wide DLL or files. However, they just don't adhere to their proper name, thanks to hard-coded programming.

On a 64-bit computer, 64-bit programs store-

Primary files similar EXE in C:\Program Files.
System-broad files like DLL etc. in C:\Windows\System32 folder contains 64-scrap libraries.

Even so, the 32-bit programs store-

Primary files in C:\Program Files (x86)
Organization-broad binder is C:\Windows\SysWOW64.

When a 32-bit program wants to install their 32-flake DLL files into C:\Windows\System32, it volition be redirected to C:\Windows\SysWOW64. This essentially makes the System32 hold only 64-fleck libraries. Microsoft could not remove it considering it would have broken a lot of programs.

What happened is that nigh of the developers who rolled out their 32-bit applications on a 64-scrap system were still using C:\Windows\System32. This was hard-coded into their plan. Since Microsoft did not want to break programs, they devised this redirection.

This makes sure that everything is happening in the background without developers needing to do much work. Whenever something is requested past a 32-scrap program from System32 folder, it is silently redirected to SysWOW64 folder which holds all the 32-flake DLL. There is no redirection needed for the 64-bit programme as they have the default folders in place.

In short: Windows x64 has a System32 binder that contains 64-flake DLLs. A 2nd SysWOW64 folder contains the 32-chip DLLs. Native 64-bit processes find their DLLs where they await them to viz in the System32 folder. For 32-chip processes, the Os redirects requests and shows them the SysWOW64 folder.

The same was washed for Windows Registry as well – 32-bit and 64-flake programs are separated.

Related: System32 folder opens automatically at startup.

The WOW in SysWOW64

Instead of naming information technology as System64, Microsoft named this folder every bit SysWOW64. WOW stands for Windows (32-bit) on Windows (64-flake). 32-bit applications were able to run on 64-bit applications, and that'south how it got its proper name.

Microsoft did not run across it coming for sure else System32 folder would not have never got its name. Information technology could take been rather simpler. However, it was an excellent decision not to rename the folder and instead use a redirection. It made sure both consumers and developers did not lose their app when they moved to 64-bit.

While 32-bit systems are slowly phasing out, and replaced with 64-fleck computers, it's going to take some time. Probably in the hereafter Microsoft might practice something about information technology. Hopefully, in that location is no hard coding in 64-fleck coding.

Read next: Sysnative folder in Windows 64-flake explained.

Anand Khanse is the Admin of TheWindowsClub.com, a x-yr Microsoft MVP (2006-16) & a Windows Insider MVP. Delight read the unabridged post & the comments showtime, create a Arrangement Restore Point earlier making any changes to your organization & be conscientious about any 3rd-party offers while installing freeware.