This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Restricted User account HKCU Entries when using "Run As Administrator"
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 27, 2007
04:08 PM
Restricted User account HKCU Entries when using "Run As Administrator"
Can anyone help me fix this?
We need to write some HKCU entries and some HKLM entries for our install. This works fine as an administrator.
If we log into a Resticted User account and use "Run As Administrator" to run the installation (or just run the installation from an administrator account), all of the HKCU entries are created for the administrator's account and are missing for the Restricted User's account. So the software can't run.
Is there any way to fix this?
We need to write some HKCU entries and some HKLM entries for our install. This works fine as an administrator.
If we log into a Resticted User account and use "Run As Administrator" to run the installation (or just run the installation from an administrator account), all of the HKCU entries are created for the administrator's account and are missing for the Restricted User's account. So the software can't run.
Is there any way to fix this?
(1) Reply
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 30, 2007
08:12 AM
This would be expected behavior as you're running in the context of the administrative user and not the limited user.
You might try using a HKCU registry key as the keypath of the component and authoring an advertised entry point to trigger auto repair to get those keys down.
You might try using a HKCU registry key as the keypath of the component and authoring an advertised entry point to trigger auto repair to get those keys down.
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)