RussellResthaven
12 years ago
I need to have a very simple installer do a perMachine install where the
program is installed to the program files folder, shortcuts created on the
desktop and start menu, and basic registry settings created to record the
install for the uninstall.
I am running Windows 7, x64 and am working in Visual Studio 2010 with Wix
3.7. My project and the installer target x64 platforms only.
The problem:
This works perfectly fine on an admin account, however most people are not
admins on their machines. What I need is for a non-admin user to be
presented with the admin prompt when installing to allow them to enter
admin credentials, or at least a user with admin privileges.
Currently, no matter what I do, the prompt *never* comes up and the
installation *always* fails.
I have tried all of the following:
-MSI Setup Project:
Package:
Keywords="Installer"Platform="x64"Description="MyProduct"Comments="MyProduct"Manufacturer="MyProduct"InstallScope="perMachine"InstallerVersion="400"InstallPrivileges="elevated"Compressed="yes"Languages="1033"SummaryCodepage="1252"
Changing between perMachine and perUser makes no difference, ditto that for
elevated vs. limited.
Next, every combination of none, one, some, or all of these makes no
difference:
<Property Id="ALLUSERS" Value="2" /><Property
Id="MSIUSEREALADMINDETECTION" Value="1" /><Property
Id="MSIFASTINSTALL" Value="1" />
At this point, I tried playing with a bootstrapper, following those
instructions and that too provides nothing helpful.
<Chain><MsiPackage DisplayInternalUI="yes"
SourceFile="$(var.SolutionDir)..\..\..\Bin\$(var.Platform)\$(var.Configuration)\MyProductSetup.msi"
/></Chain>
First, the bootstrapper gives a generic UI that is not what is specified in
my MSI. I've tried adding the DisplayInternalUI="yes" value and it doesn't
display the MSI UI.
Further, the same exact problem happens where it fails due to lack of
privileges.
I also read that it might have the intended behavior if the filenames have
the word "setup" in them. I tried that too, to no avail.
So that sent me off in the direction of trying to change the manifest.
Using the command suggested by various folks on different boards and
mailing lists has the unfortunate effect of stripping the entire MSI out of
the boostrapper exe. Whereas before I run mt.exe, it's about 10MB. After I
run it, it's stripped down to about 300k and is ruined.
Next I tried a program called ResourceHacker to manually edit the manifest
in place to be:
<requestedExecutionLevel level="requireAdministrator" uiAccess="true" />
While this did not cripple the file, like all other attempts it did nothing.
At this point I'm completely out of ideas, hence this email. I am starting
to think there might be something wrong with my machine. I am testing with
a basic user account that I made specifically for testing this scenario.
Again, when running as a user with admin privileges, everything works fine
either when running the MSI directly or through the bootstrapper.exe. When
running with the basic account, both fail.
I'm two weeks into it and am totally out of ideas and time. Any help would
be greatly appreciated.
Thanks.
program is installed to the program files folder, shortcuts created on the
desktop and start menu, and basic registry settings created to record the
install for the uninstall.
I am running Windows 7, x64 and am working in Visual Studio 2010 with Wix
3.7. My project and the installer target x64 platforms only.
The problem:
This works perfectly fine on an admin account, however most people are not
admins on their machines. What I need is for a non-admin user to be
presented with the admin prompt when installing to allow them to enter
admin credentials, or at least a user with admin privileges.
Currently, no matter what I do, the prompt *never* comes up and the
installation *always* fails.
I have tried all of the following:
-MSI Setup Project:
Package:
Keywords="Installer"Platform="x64"Description="MyProduct"Comments="MyProduct"Manufacturer="MyProduct"InstallScope="perMachine"InstallerVersion="400"InstallPrivileges="elevated"Compressed="yes"Languages="1033"SummaryCodepage="1252"
Changing between perMachine and perUser makes no difference, ditto that for
elevated vs. limited.
Next, every combination of none, one, some, or all of these makes no
difference:
<Property Id="ALLUSERS" Value="2" /><Property
Id="MSIUSEREALADMINDETECTION" Value="1" /><Property
Id="MSIFASTINSTALL" Value="1" />
At this point, I tried playing with a bootstrapper, following those
instructions and that too provides nothing helpful.
<Chain><MsiPackage DisplayInternalUI="yes"
SourceFile="$(var.SolutionDir)..\..\..\Bin\$(var.Platform)\$(var.Configuration)\MyProductSetup.msi"
/></Chain>
First, the bootstrapper gives a generic UI that is not what is specified in
my MSI. I've tried adding the DisplayInternalUI="yes" value and it doesn't
display the MSI UI.
Further, the same exact problem happens where it fails due to lack of
privileges.
I also read that it might have the intended behavior if the filenames have
the word "setup" in them. I tried that too, to no avail.
So that sent me off in the direction of trying to change the manifest.
Using the command suggested by various folks on different boards and
mailing lists has the unfortunate effect of stripping the entire MSI out of
the boostrapper exe. Whereas before I run mt.exe, it's about 10MB. After I
run it, it's stripped down to about 300k and is ruined.
Next I tried a program called ResourceHacker to manually edit the manifest
in place to be:
<requestedExecutionLevel level="requireAdministrator" uiAccess="true" />
While this did not cripple the file, like all other attempts it did nothing.
At this point I'm completely out of ideas, hence this email. I am starting
to think there might be something wrong with my machine. I am testing with
a basic user account that I made specifically for testing this scenario.
Again, when running as a user with admin privileges, everything works fine
either when running the MSI directly or through the bootstrapper.exe. When
running with the basic account, both fail.
I'm two weeks into it and am totally out of ideas and time. Any help would
be greatly appreciated.
Thanks.