This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- how can I force writing regsitry entries into 64-bit part?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 15, 2014
09:38 AM
how can I force writing regsitry entries into 64-bit part?
Hi,
I have a 32 bit installer package that installs 32-bit software. That software forces usage of the 64-bit key HKEY_LOCAL_MACHINE to read and write registry entries. My installer should prepare some registry entries that I configure during the user interface sequence. But the 32-bits installer should also write those entries in the 64-bit HKLM-part of the registry.
How can I force the MSI WriteRegistryValues action to use the 64-bit registry part?
I am able to write to the 64-bit registry myself, but all properties defined in the Registry Data views won't store themselves there.
At the moment, I have tried to create custom actions just before the action WriteRegistryValues to force:
Disable(WOW64FSREDIRECTION);
REGDB_OPTIONS = REGDB_OPTIONS | REGDB_OPTION_WOW64_64KEY;
But no luck yet.
Thank you
Marc
I have a 32 bit installer package that installs 32-bit software. That software forces usage of the 64-bit key HKEY_LOCAL_MACHINE to read and write registry entries. My installer should prepare some registry entries that I configure during the user interface sequence. But the 32-bits installer should also write those entries in the 64-bit HKLM-part of the registry.
How can I force the MSI WriteRegistryValues action to use the 64-bit registry part?
I am able to write to the 64-bit registry myself, but all properties defined in the Registry Data views won't store themselves there.
At the moment, I have tried to create custom actions just before the action WriteRegistryValues to force:
Disable(WOW64FSREDIRECTION);
REGDB_OPTIONS = REGDB_OPTIONS | REGDB_OPTION_WOW64_64KEY;
But no luck yet.
Thank you
Marc
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 16, 2014
04:49 AM
I have now created a custom action where I write each registry settings myself, but forcing it to the 64-bit portion. Not a great solution, but that works.
Does anyone know a better solution for this?
Thank you!
Does anyone know a better solution for this?
Thank you!
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)