HLKM64; it's documented but does it work?

[Michiel]

As documented here, it is possible to bypass registry redirection when running a 32bit application on a 64bit Windows installation, using HKLM64 or HKCR64. I quote:
 

For registry interaction, use HKCR64 or HKLM64 to bypass the redirection mechanism see Registry Functions documentation.

 
In this thread, >this feature's existence is denied.

Also, if this feature exists and works, does it work on both production and beta? And can I also specificy HKEY_LOCAL_MACHINE64 and HKEY_CLASSES_ROOT64 instead of HKLM64 and HKCR64?

[JohnOne]

If you use that, it puts the onus on the OS to figure where to direct the call.

[Michiel]

If you use that, it puts the onus on the OS to figure where to direct the call.

 

I don't understand.. What do you mean? I know what an onus is, but what is "that" referring to here?

[JohnOne]

what is "that" referring to here?

"HKLM64"

On a 32 bit OS it will direct to HKLM, on a 64 bit OS wil direct to HKLM64 or appropriate path if HKLM64 is not available.

[Michiel]

Hmmm, I just tested it on Windows 7 Home Premium x64, and what HKLM64 does is evade the registry redirector as documented: instead of storing registry writes to virtual locations under Wow6432Node, Windows now lets my 32bit application write to and read from the normal non-redirected locations...

Am I missing something here?

[caramen]

you need to correct multiple path in registry to help windows to call the correct DLL's that are not called in HKLM x86 this feature exist i can give you the complet set of key you have to check i need to get back my documentation if i found it i ll edit that post

[Michiel]