[Bug] PAL needs to be able to disable Wow6432Node redirection

Perhaps something like the following would work:

[RegistryKeys]
SomeKey1=HKCU\Software\SomeKey
SomeKey2=HKLM\Software\SomeKey2

[RegistryKeys:DisableWow6432Node]
SomeKey3=HKLM\Software\SomeKey3

The first case is how we do it now, the second is an example of how we could control things.

In a 64 Bit OS, SomeKey1 would not be redirected as HKCU typically isn't subject to redirection. SomeKey2 would be redirected.

SomeKey3 would have redirection disabled by the special section.

You would want to export all keys in 32 bit mode, as 64 bit mode would add Wow6432Node to the path in the file. You would import all keys in the first INI section using 32 bit mode, and use 64 bit mode to import the second entries.

What I mean by 32 bit mode is that if you have a reg file, and it goes to HKLM\SOFTWARE\AKey (no Wow6432Node in the file), if you import it with cmd.exe *32 (running under WOW64), it will be imported to HKLM\SOFTWARE\Wow6432Node\AKey. If you used the 64 bit CMD.exe, it would not be redirected.

NSIS is a 32bit executable..

if you want to read/write in x64 registry..
use Custom code..

takes only a few lines..

set in .OnInit

ie.

!include x64.nsh

${SegmentFile}
${Segment.OnInit}
${If} ${RunningX64}
   SetRegView 64
   ${DisableX64FSRedirection}
${EndIf}
!macroend

if you want to use the launcher..
then use ReadINIStr or ${ReadLauncherConfig}

if you really don't want to use Custom Code
then you can edit the source to have your own custom Launcher sections..
so end-users don't have to deal with Custom code.

if you don't want to edit anything at all..
then redesign PAL with NSIS 3.0 x64 ..
it's been released.

what was the workaround?

can you show us?

While PAL is currently using a modified version of NSIS 2 we will be switching it to NSIS 3 in the near future. As of the NSIS 3.02 release, NSIS now has support for HKCR32, HKCR64, HKCU32, HKCU64, HKLM32 and HKLM64 registry root keys and no longer supports SetRegView. We'll need to consider how we implement this going forward carefully and possibly adapt our handling of .reg files to match.