Software Deployment

ORIGINAL: dmack

I have an MSI that is writes an entry into HKEY_USERS, however I can't find this key within the Feature Details Registry section in Wise. Where can I find it in Wise so that I can modify it?



Probably the obvious question, but have you made sure you have selected 'All Features (Modify/Delete Only)' in the 'Current Feature' dropdown box in the Feature Details view ?

Failing that, have you checked to see if the registry key is visible in the Registry Table using the Tables tab in Setup Editor.

Lastly, it is always a possibility that the registry key concerned is being written by a custom action rather than driven by the Registry table.

Spartacus

Thanks Spartacus. Found it in the Tables tab in the Setup Editor.

Question: Do you why I can't modify the HKEY_USERS registry manually even running as Admin with full rights?

Possible answers are because it doesn't exist at the time your writing to it or because its in use or because you don't have rights at the same level. HKEY_Users is what is loaded for use inside/outside of the loaded users profiles and is usually the parts of a user's profile that is being used actively. Accounts that may be loaded, but not writeable to by the user that is running the install are System, Administrator, etc. Especialy obvious in Win7, the System account properties (files/registry) cannot (usually) be directly accessed or changed by other users. ( I may not be explaining this well so I suggest you investigate further)

Instead, write to HKCU so it will be loaded at the time the user logs in. There are many ways to do this, but I tend to prefer to use Active Setups for our environment.

This is basically permission problem with it. Please try running the regedit as admin and trying writing the registry still if you are facing the problem then do the following,

1. Run Registry Editor (RegEdit).
   
2. Navigate to the registry key which user wants to modify its security settings.
   
3. Right click on selected registry key, and select Permissions.

Grant full permissions then It must work.

Thanks,
-MST

Please explain how a deployment system runs RegEdit, clicks down the tree, right-clicks a key, etc., etc.

@OP: re-jig the MSI to NOT write to that key. If you need to get stuff into HKCU (which is what HKU\[UserSID] becomes when users log in), use either self-healing (search the archive here for details) or Active Setup (ditto). Then send your invoice to the vendor for fixing his brain-dead package.