[v2] Machine install using SYSTEM account error. Topic is solved

[NCCAP]

Hi,

I am currently having an issue deploying v2 to our enterprise environment using Microsoft Endpoint Configuration Manager (Formally known as SCCM).

Installing silently as a normal admin user to the location "C:\Program Files\AutoHotKey" works as expected with the command:
AutoHotkey_2.0.2_setup.exe /Silent /Installto "C:\Program Files\AutoHotKey"

Unfortunately when doing the same using the SYSTEM account the install fails to complete successfully, with the message below:

System_Install_Error.jpg (54.48 KiB) Viewed 935 times

As MECM (SCCM) uses the SYSTEM account to do machine wide installs, we are currently unable to deploy this to our users.

Testing can be done by using PSEXEC to gain access to a CMD window running as SYSTEM, using this command: ("C:\psexec.exe" PSEXEC -i -s -d CMD)

Previous v1 installs worked fine! Does anyone have a solution?

Thank you

[lexikos]

It appears that xml.load("res://" ExePath "/#24/#1") cannot work under the SYSTEM account. It will be fixed by using the Resource API to load the manifest instead.

Previous v1 installs worked fine!

This is only because you never enabled the UI Access option, which is always enabled for v2. It can't be enabled at the command line, but is enabled automatically if a UIA.exe file is already present (such as from a previous installation via the GUI).

[lexikos]

Fixed by v2.0.3.

[NCCAP]

Confirmed to be fixed, Thank you.