Using Application Launcher element to add values to registry keys does not create them on correct place (214202)

When using Application Launcher elements to add new registry keys to HKEY_LOCAL_MACHINE\SOFTWARE structure they are missing from registry even when logs show the action as successfully completed.

Two types of elements can be used:

1) Create a batch file with the "Regedit.exe /s <.reg file>" command and using that batch file as file name without arguments on the application launcher element.

Or

2) Use Regedit.exe as file name on the application launcher element with the "/s <.reg file>" as argument.

Both methods are added to logs as successfully completed, but values are not available on desired keys.

Desktop Authority client is a 32 bits application, when a 32 bit program is launched, it runs in the 32 bit area of the machine.  when a 32 bit application is requested to programmatically write to the registry, even if the 64 section is targeted, Windows will send it to the 32 bit section of the registry, then it adds the new registry keys to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node structure. When a 32-bit application queries a value under the HKEY_LOCAL_MACHINE\SOFTWARE\\subkey, the application reads from the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\\subkey.

To enter a Windows Registry Key to HKEY_LOCAL_MACHINE\SOFTWARE\\subkey, a Registry element can be created and used, this will add the key as a 64 bits application to the HKEY_LOCAL_MACHINE\SOFTWARE\\subkey

Article How to create a Registry profile element with existing .reg files (107935) explains how import a registry file to registry keys.