You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I built a bundle installer with a <PackageGroup> comprising three MSI packages and using WixStandardBootstrapperApplication (and specifying the Wix v5.0.2 SDK in the .wixproj).
When starting the resulting bundle exe as a non-privileged user, I'd expect that the Windows UAC elevation would drop in, but this does not happen.
Instead, the installation of the first MSI simply fails on writing a file (in this case a .png file, but I guess this is more or less random).
Note that I specify Compressed="no" for the <Bundle> element, and if it's "yes", the behavior is worse.
How can I configure/enforce UAC privilege elevation on startup?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
WiX Toolset
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I built a bundle installer with a
<PackageGroup>comprising three MSI packages and usingWixStandardBootstrapperApplication(and specifying the Wix v5.0.2 SDK in the .wixproj).When starting the resulting bundle exe as a non-privileged user, I'd expect that the Windows UAC elevation would drop in, but this does not happen.
Instead, the installation of the first MSI simply fails on writing a file (in this case a .png file, but I guess this is more or less random).
Note that I specify
Compressed="no"for the<Bundle>element, and if it's"yes", the behavior is worse.How can I configure/enforce UAC privilege elevation on startup?
Beta Was this translation helpful? Give feedback.
All reactions