Sneaky effect from using 32-bit file manager

[j7n]

I use a 32-bit Total Commander because I don't like updating any software that comes with many changes. I know about some pitfalls of it, like System32 redirection. But something new came to bite me. I launched a BAT file, which spawned a 32-bit CMD, and programs within it operated on the Wow6432Node registry. I also launched CMD from the command bar with the same outcome. As the CMD stays open, it is not obvious that it is in fact 32-bit or from where it was launched.

I think this issue also occurs with RegEdit and REG files. But most of the time edits happen in the common areas. so it doesn't matter. Like everything to do with the SYSTEM hive or the HKCU\Software key, which surprisingly isn't mirrored.

This WOW stuff in Windows is really confusing.

[Dalai]

There's an easy way around it for batch files. Here's a code example of how I tackle this problem:

Code: Select all

@echo off
set REG_EXE=%SystemRoot%\system32\reg.exe
set REGEDIT_EXE=%SystemRoot%\system32\regedit.exe
if exist %SystemRoot%\SysNative\*.exe (
    set REG_EXE=%SystemRoot%\SysNative\reg.exe
    set REGEDIT_EXE=%SystemRoot%\SysNative\regedit.exe
)

This can be done with any executable/file. reg.exe is a bit special in that it has a switch /reg:32 and /reg:64 which specifies on which registry branch it is supposed to operate.

BTW, there's no problem accessing the SYSTEM branch from a 32-bit executable. The relevant problematic branches are HKLM\Software and HKCU\Software (and a couple more).

[j7n]

Yes, System is shared like I said. What is the reason for HKLM\Software needing a separate copy, but HKCU\Software being fine as is? It's a bit weird design that Windows settings are buried deep under Software.

[Dalai]

What is the reason for HKLM\Software needing a separate copy, but HKCU\Software being fine as is?

The same reason why there's file redirection in regards to System32, catroot, catroot2 and a couple of others: to keep 32-bit programs and their settings separated from 64-bit programs and their settings. OK, in case of files, there's another reason: 32-bit programs can't load 64-bit DLLs and vice versa.

It's a bit weird design that Windows settings are buried deep under Software.

Where else would they be? They're software settings after all. Explorer settings are in the Explorer key. Settings regarding Calculator or Notepad can be found in their corresponding keys. And so on and so forth. But I guess there are some historical reasons as well. The registry itself started with Win95 which is getting 30 years old next year.

PS: I was wrong about HKCU\Software being problematic. Only HKLM\Software has a Wow6432Node subkey that is frequently used.