I have a 32-bit application and a 32-bit installer, written in Wise Installation Studio. I know...I shouldn't be using Wise and I should switch to something else. But for now, I'm stuck with it.
Our application is graphics-intensive and to improve performance, we want it to disable desktop composition (Windows Aero) while running. We accomplished this on 32-bit systems by adding a registry entry at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
with a value of DISABLEDWM
.
This sets the "Disable desktop composition" checkbox in the compatibility tab of the properties for our EXE to be checked by default.
This works perfectly on 32-bit systems, but when running the installer on a 64-bit system, Windows redirects the creation of registry entries to HKLM\SOFTWARE\Wow6432Node
, and the flag is not set correctly. If I manually create an entry in the 64-bit registry view, then it works.
So how can I force this registry key to be created in the 64-bit registry view from our 32-bit installer? Or is there a better way to set this property aside from creating a registry entry?
I'm not sure what possibilities Wise gives you regarding scripting, but the way to access the 64-bit registry from a regular program is to use KEY_WOW64_64KEY when manipulating the registry.
If it's a possibility to at the least run an external EXE file from the setup, it should solve your problem.
I am not sure if this solution was possible at the time this question was asked, but you can create a custom action that executes a REG ADD
command and include the /reg:64
switch, like this:
REG ADD "HKLM\Software\Example" /v "Name" /t REG_SZ /d "Data" /reg:64
The /reg:64
switch will force it to the 64-bit registry. I am not entirely sure what this will do on a 32-bit system, but I expect it will probably be ignored.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With