Replies: 2 comments
-
I have added 2 keys to test the behavior SystemComponent and VkpabbaSystemComponent (assigning the same value) |
Beta Was this translation helpful? Give feedback.
0 replies
-
You'll probably need to dig through a verbose log file for all the various installs/uninstalls to see what is getting re-run and messing up the registry key you're trying to set. Patches create lots of complexities. 😄 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Question
I have a base setup (RTM) followed by three sequential hotfixes: HF1, HF2, and HF3. After installing HF3, only RTM and HF3 are visible in "Programs and Features" (Control Panel), while HF1 and HF2 are hidden. I’m hiding HF1 and HF2 by setting their SystemComponent registry value to 1 using a custom action scheduled before InstallFinalize.
This works as expected during installation. However, the issue occurs when I uninstall HF3 — both HF1 and HF2 become visible again in the Control Panel. On investigation, I noticed that although the SystemComponent value was correctly set to 0 via custom action, it gets deleted later. As a result, the previously hidden entries for HF1 and HF2 reappear, which is not desired.
How can I ensure that HF1 and HF2 remain hidden even after HF3 is uninstalled? Is there a way to prevent the deletion of the SystemComponent registry value during uninstall?
Note: I am using WiX v5
<CustomAction Id="HideHotFixes"
Execute="" -> Tried with immediate, commit and deferred type of custom actions
DllEntry="HideandUnhideHotFixes"
Impersonate="no"
BinaryRef="MBACAs" />
Any help would be greatly appreciated. Thanks in advance!
Open Source Maintenance Fee
wixtoolset
project because I support the maintainers.Beta Was this translation helpful? Give feedback.
All reactions