AppDataFolder when installer is running as SYSTEM account

[smljoju]

We set both EXE extract location and installer log file (via MSI command line property) under [AppDataFolder][|Manufacturer], all is good but if installer is running under SYSTEM account, it will have an issue because extract location ends up writing to C:\AppData\Roaming folder, so then installer will show an error that it is unable to access the log file because %appdata% folder of the SYSTEM account doesn't exist (or the sub folder [|Manufacturer] doesn't exist)

Question is why does the extract location of the installer behave this way when running the SYSTEM account? and if the extract location behaves that way, why would the log file be written to a completely different location? I would expect that either both should succeed or both should fail since these are both initially done by the exe bootstrapper

[Catalin]

Hello,

Thank you for the details on this.

I have tested this and managed to reproduce the issue on our end.

I will create a ticket and this will be fixed in a future version of Advanced Installer.

As a workaround, you can use a different location for your log file, e.g. the [TempFolder]:

Screenshot_40.png (22.27 KiB) Viewed 993 times

Hope this helps!

Best regards,
Catalin

[smljoju]

ok got it, thanks for the reply

please do keep us posted for future versions when this issue gets fixed, thank you!

[Catalin]

You are always welcome!

And sure, I will update this thread as soon as a version with a fix will be released.

Best regards,
Catalin

[Catalin]

Hello,

A little followup on this, as this seems to be a coincidence that it actually works during a normal installation.

For more information, please read the following thread:

Log File Saving in custom location

Basically, the folder must exist on the disk before the log file is created, because the Windows Instlaler can not create the folder for us.

Best regards,
Catalin