Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>In every case, I <em>really</em> don't expect the two issues really your problem. And I have some experience. Your are not looking for the right things, I guess, you are already to deep. Abandon your "MsiTrueAdminUser" search is my recommendation. Besides, I share the idea with Christopher.</p> <p>Posting the basic problem behaviour would be probably more successful. Are you aware of UAC and it's implications to MSI? There I would start. For MSI it is not important, if you are the built-in "Administrator" user or not as long as you have started the MSI with elevated rights.</p> <p>There are two common problems. They would make over 90% of all "elevation" problems, I guess. First prob is, that it makes a difference, if you start the msi already with elevated rights or you wait until the msi dialog is asking for it. If possible, try to assure the first scenario, e.g. with a setup.exe boot strapper.</p> <p>Second prob is the understanding, when msi is working with which rights. To simplify it a bit in one sentence, it uses the rights with which it was started, but between the actions InstallInitialize and InstallFinalize (this is where the real changes are done!) it uses them from the local system account, no matter with what rights it was started. (Assumed that it is an elevated and not a per-user install)</p> <p>Remember, the local system account has a slightly different right set than administrators, so probably you are looking for the wrong detail.</p> <p>The two issues get really complicated, if you have to deal with custom actions. Then there is a distinct MSI knowledge necessary to find out with which rights your actions are started. And most times there is the problem.</p> <p>Generally, it is not very good style to use elevated rights in a setup at another place than in the mentioned section (InstallInitialze/InstallFinalize). If you are the setup author, I would first recommend to read about best practices.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload