This question already has an answer here:
- Inno Setup does not seem to write to the registry on a 64-bit machine 1 answer
In my Inno installer I am writing some registry keys:
RegWriteStringValue(HKEY_LOCAL_MACHINE, 'SOFTWARE\Google\Chrome\NativeMessagingHosts\com.mycompany.myapp', '', ExpandConstant('{app}\{#MyAppChrome}'));
RegWriteStringValue(HKEY_LOCAL_MACHINE, 'SOFTWARE\Mozilla\NativeMessagingHosts\com.mycompany.myapp', '', ExpandConstant('{app}\{#MyAppChrome}'));
It automatically writes it to the keys under Wow6432Node, which is fine. But firefox expects it not be under Wow6432Node:
Windows
For global visibility, create a registry key with the following name:
HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\NativeMessagingHosts\ The key should have a single default value, which is the path to the manifest.
Note that this key should not be created under Wow6432Node, even if the app is 32-bit. The browser will always look for the key under the "native" view of the registry, not the 32-bit emulation. To ensure that the key is created in the "native" view, you can pass the KEY_WOW64_64KEY or KEY_WOW64_32KEY flags into RegCreateKeyEx. See Accessing an Alternate Registry View.
So, how can I prevent the redirection of firefox related registry key.