I am packaging an application which works fine in Admin User, but gives fatal error message saying Registry entry creation failed in power user mode. The original application doesn't behave this way. (I recreated MSI, stilll I am facing the same problem)
So i need to give permission to power user to edit the particular regisrty.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


If you know the registry key, then you need to set the required permissions on that key (and most probably its subkeys as well).

Windows Installer provides the LockPermissions table which can be used, though it is some what limited. My preferred method is the 'secedit' utility that is included within Windows.
Answered 03/07/2006 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
Generally speaking, I wouldn't use the the LockPermissions table as this overwrites the existing ACL. It's generally a lot safer to append to the ACL. I agree with brenthunter2005 on using Secedit --it's native to Windows (always a plus) works reliably (a must for SW repackaging) and can be scripted/customized using a variety of methods. At my company, we use 2 vbscripts (one for regkeys, one for files/folders) which call secedit as a custom action.
Answered 05/09/2006 by: norexx
Orange Belt

Please log in to comment
just for the sake of completeness, I'd like to point to subinacl from the ResKit, this is a very powerful tool for ACL handling.
Answered 05/12/2006 by: KPrinz
Fourth Degree Green Belt

Please log in to comment