[wix-users] When does Burn use C:\ProgramData\Package Cache\ vs C:\Users\...\AppData\Local\Package Cache?

[Hoover, Jacob]

Per Machine vs Per User installs have a different location.

Logs will indicate the error, and what it was attempting to do at the time the error occurred.

http://errco.de/win32/winerror-h/error_elevation_required/0x800702e4/

From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of Shintaro Takechi via wix-users
Sent: Thursday, April 8, 2021 3:30 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Shintaro Takechi <devst119 at gmail.com>
Subject: [wix-users] When does Burn use C:\ProgramData\Package Cache\ vs C:\Users\...\AppData\Local\Package Cache?

Hi,

I now encounter weird errors.

I have a bundle project (calling bundle A) that is perfectly working, and
now I am working on a bundles that is created again from the bundle A.
(calling this new bundle B)
Even though the prerequisite exe has not changed, nor the <ExePackage ...>
code, error started to show up in the middle of installing the prerequisite
for bundle B.

Error code itself are 0x800702e4, but I do not think the cause is not
elevation issue.
I compared the binaries (using winmerge) and confirmed the exe are same.

Main difference I found in the bundle .log is the path the file is
available.

In the bundle A, the path of this problematic prerequisite was located
in C:\ProgramData\Package Cache

However, in the bundle B the path of this prerequisite is placed
at C:\Users\My.User.Name\AppData\Local\Package Cache

I recall the majority of the time ProgramData was used before.
How could this happen?
When does WiX determine to use different package locations?
Is there a flag in the bundle code I can modify to guarantee the use of
ProgramData?

Best regards,

Shintaro Takechi

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/<http://www.firegiant.com>
NOTE: This email was received from an external source. Please use caution when opening links or attachments in the message.