How to Import .Reg File Via Scripting to 64 Bit Registry Hive (4248106)

The problem is the “HKEY_LOCAL_MACHINE\SOFTWARE \Wow6432Node” registry key represents a separate view of “HKEY_LOCAL_MACHINE\SOFTWARE” for 32-bit applications. This runs on all 64-bit version of Windows.

By calling “%WINDIR%\regedit.exe /s MyRegistry.reg” directly from the Kbox script would import registry value to “HKEY_LOCAL_MACHINE\Software\Wow6432Node”, this is not what we are trying to achieve.  Our goal is to import registry to “HKEY_LOCAL_MACHINE\SOFTWARE” which is a native registry location for 64-bit applications.

In order to reach our goal we will use Regedt32.exe a Windows registry configuration editor and SYSNATIVE Windows system re-director.

Quest Kace agent is a 32-bit application and therefore uses 32-bit Windows libraries and executables from %WINDIR%\SysWoW64 directory. This location contains 32-bit DLLs and executables including a regedit.exe which is commonly used in scripting to import or export registry values.

Steps to resolve

• Have your .reg file ready and tested manually on your test 64-bit Windows system.
• Test .reg file manually by double clicking on the file and accept all messages to import registry values, then verify expected results. When you do a manual .reg file importing via double-click, it uses 64-bit OS libraries.  Therefore all registries are imported to “HKEY_LOCAL_MACHINE\Software\” hive.

1. Let’s create a Kbox script by going to Scripting – Scripts – Choose Action and selecting “Add New Item”
2. Select “Run As Local System”
3. Check box next to “Allow Run While Logged Off”
4. Under “Dependencies:” upload your xxxxxx.reg file
5. In “On Success” step select “Launch a program…”

“Directory:” %WINDIR%\SYSNATIVE

“File:” regedt32.exe

“Wait For Startup” box CHECKED

“Parameters:” /s $(KACE_DEPENDENCY_DIR)\MyRegFile.reg

(Note: Replace “MyRegFile.reg” with the actual your file name)

1. Enter a name for the script, limit distributions if needed and save it.
2. Test this script on couple of systems to verify expected results.

          ***NOTE: Provided script is for 64-bit Operating System architecture ONLY. It will not succeed if it is targeted for 32-bit OSs.***