I have found a number of posts regarding the subject of Current User and MSI repairing the registry keys however none of the solutions (active setup, stub) I believe should be used in a well authored MSI package.

My situation is as follows.

I am repackaging RealPlayer 10.5 which installs and works well however when a user with a locked down account logs in although the application will initiate a self repair from the realplay.exe which is an advertised shortcut, none of the HKCU values are populated. When installing with an account which admin privilages there are no problems however I have got the following message in the event viewer which appears when either a admin or a restricted account runs the app:

Detection of product '{0DE977BB-70C9-4D0E-83D5-CF2F61047645}', feature 'Complete', component '{BD2BD4CB-0226-4BFC-A66C-5C32F7626D8D}' failed. The resource 'HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Media\MimeTypes\text/vnd.rn-realtext' does not exist

The product GUID {0DE977BB-70C9-4D0E-83D5-CF2F61047645} refers to RealPlayer, the component in the "Complete" feature is {BD2BD4CB-0226-4BFC-A66C-5C32F7626D8D} and it refers to the "Current User" component. The registry value that it errors on is the key path.

I know that the key path does not exist for that user hence the self repair but I do not quite understand why the registry entries are not being repaired. The advertised shortcut that initiates the repair is in the same component which I believe is what is needed for it to start the self repair and check all the other key paths in the same feature.

I have also tried adding the registry key to the Lock permissions table to elevate its permissions however this did not work either.

Can anyone help here please?


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 i understand you corrently then the msi is doing what normal, it's trying to install the user part, the way i deploy application we put the user in a group if they are in the group they have elevate rights meaning user can install registry key under HKCU, which is how most deploy technology work. so if you give the user a shortcut went you user click on it then the msi will try to repair the user part. so you need to give the user access.
Answered 10/05/2006 by: linstead
Blue Belt

Please log in to comment