We use RunOnceEx to run post unattend processes. Some of the processes run regedit /s with a reg file. These have always worked fine in a 32bit OS. However, when I started running these in a 64bit OS, the settings do not stick. We have simply lived with the issue since 2003 64bit, but now I would like to find an answer. Interestingly, if I pause RunOnceEx with a cmd /k, then manually apply the reg file and open RegEdit, the changes do appear. However, when I reboot, the changes are reverted. Any ideas? Anyone else seen this in 64bit OS's?

64bit has 2 registries, probably could be it...

Note The registry in 64-bit versions of Windows XP, Windows Server 2003, and Windows Vista is divided into 32-bit and 64-bit keys. Many of the 32-bit keys have the same names as their 64-bit counterparts, and vice versa. The default 64-bit version of Registry Editor that is included with 64-bit versions of Windows XP, Windows Server 2003, and Windows Vista displays the 32-bit keys under the following node:

HKEY_LOCAL_MACHINE\Software\WOW6432Node

http://support.microsoft.com/kb/305097/

64bit has 2 registries, probably could be it...

Note The registry in 64-bit versions of Windows XP, Windows Server 2003, and Windows Vista is divided into 32-bit and 64-bit keys. Many of the 32-bit keys have the same names as their 64-bit counterparts, and vice versa. The default 64-bit version of Registry Editor that is included with 64-bit versions of Windows XP, Windows Server 2003, and Windows Vista displays the 32-bit keys under the following node:

HKEY_LOCAL_MACHINE\Software\WOW6432Node

http://support.microsoft.com/kb/305097/

Good thought, but no. I am aware of both. I also know that if you use the regedit in system32 you get the 64bit version (with access to the WOW6432Node branch) and if you use the regedit under syswow64, you get only the 32bit branch only. This alas is not the issue. I can see the settings in regedit after applying the file manually from a command prompt, but after reboot, those same settings (whether in the main or wow6432node branch) are gone. Thanks for the info, though.

We use RunOnceEx to run post unattend processes. Some of the processes run regedit /s with a reg file. These have always worked fine in a 32bit OS. However, when I started running these in a 64bit OS, the settings do not stick.

really don't see that. I run and add many applications and apply settings with RunOnceEx including regedit /s since early XP. I'm running 64 bit now for 6 months and no change but I've adjusted to look at both sides of the registry with my Jump2reg program

Strange what your saying it apply and then disappear.

We use RunOnceEx to run post unattend processes. Some of the processes run regedit /s with a reg file. These have always worked fine in a 32bit OS. However, when I started running these in a 64bit OS, the settings do not stick. We have simply lived with the issue since 2003 64bit, but now I would like to find an answer. Interestingly, if I pause RunOnceEx with a cmd /k, then manually apply the reg file and open RegEdit, the changes do appear. However, when I reboot, the changes are reverted. Any ideas? Anyone else seen this in 64bit OS's?

I slipstream all my custom reg entries into the wim using a cmd file like this one attached, then, save the changes. Of course your paths and file names will differ, but, it always works perfectly; so far anyways

RegHive.7z