IanDD25 asked a question.
InstallShield Express fails to write registry values to Current User
We have a build that writes about 6 string values to our app's section of Current User section of the registry.
This has worked fine for many years but we have one customer for whom the writing to the registry fails.
The build installs correctly, only the registry part fails.
Is this issue related to some increased security in their Windows environment? If so, how can I resolve this within InstallShield?
If your installer is working correctly in all other instances - and the issue only occurs on this customers machine, then I think it would be logical to assume that the issue is unique and specific to their environment.
You would need to perform some testing, perhaps with Microsoft's process monitor to understand what is blocking the installer from writing those registry keys.
In addition, how are you writing those registry keys? Are they simply part of a component in your installer, or are they being written by a custom action or some other method?
Maybe the customers security is blocking the custom action, but not registry entries written by windows installer.
I would speak directly to your customer and have them contact their IT department to understand if they have any security policies which could be blocking this.
If they do, then it may be difficult to circumvent that security as this would constitute a vulnerability (which security companies are very keen to avoid).
Hi and thanks for your feedback. The registry is written to via the "Registry" section under "Configure the Target System", so no custom actions are used.
I have asked the customer for more information on their policies and I have also asked them to try a manual creation of a string in the registry to see if that is blocked too. If I hear anything back from the customer I will update this post, otherwise I guess it's something to do with their specific security policy.