Hello.
I have a WiX MSI that installs a bootloader. On EFI systems, it does so in the
EFI system partition. On BIOS systems, it chainloads the new boot option to
the Windows Boot Manager (and so running bcdedit shows the new option).
When I run my MSI on a BIOS system, everything works as expected. If I run cmd
as administrator and then install the MSI via msiexec, things work. If I
instead run cmd normally, or just double-click on the MSI, I'll get a UAC
prompt, and then things work as expected.
For EFI, the story is different. On an EFI-installed system, if I run cmd as
administrator and then install the MSI via msiexec, things work. But if I go
the UAC prompt route, my MSI installation fails.
This is confusing. I thought there is no difference between running a command
explicitly as administrator, and running a command by accepting the UAC prompt,
but this clearly shows there is in fact a difference.
Any ideas why I'm running into this behaviour? Any ideas how I can fix this,
or at least debug it further?
P.S. I use the Get/SetEnvironmentVariable API calls from my code to tweak the
EFI partition. This requires the SeSystemEnvironmentPrivilege, which I do set,
so that's not the issue, AFAIK.
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
