Post Go back to editing

MSI Installer fails silent installs as SYSTEM

Category: Software
Product Number: LTSpice
Software Version: 17.1.6


We're trying to deploy the LTSpice software (the MSI edition) with the All Users configuration.

Launching the installer via GUI on the device and selecting All Users works.

Deploying it in bulk (silently, etc.) via the SYSTEM account fails with the following error. The icons briefly appear on the desktop, before rolling back on failure.

Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI4967.tmp, Entrypoint: OnExpandArchConfig
MSI (s) (F4!2C) [15:51:32:795]: Product: LTspice -- The system cannot find the path specified.


The system cannot find the path specified.

CustomAction AI_ExpandArchConfig returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

  • Hi,

    The LTspice installation makes use of two directories in Windows: one for the application and the second one for the libraries.  Both directories are under the "user id" "%APPDATA%" ( as an example typically "C:\Users\USERNAME\AppData").

    As you can see from the reported error, your process is trying to make use of a directory that does not exist. If the script is meant to provide for a given "user", it will have to be aware in the location of those directories for the individual user who will run LTspice. Be aware that LTspice and its installation are making use of "%APPDATA%" as defined by Microsoft and the previous paragraph.. 

  • I can also confirm with the user that this install will not work as the SYSTEM account.

    We are currently working on modifying our install of LTspice to the MSI version that your company is now publishing over the older exe version.  In going through the process, we have noticed the following.

    If we wish to install the application silently for all users on a computer we are able to use the following command:
    msiexec /i "LTspice64.msi" ALLUSERS=1 /qn /norestart
    When on a computer this would be a viable solution as even running as admin runs as a known "user" on the system.
    However, our goal is to distribute through the Microsoft SCCM software distribution service.  The way that apps install via this service is using the Windows NT AUTHORITY\SYSTEM account to complete the installation (versus a traditional user account).  The problem is that the application immediately fails the installation process with a 1603 error.  From what I can tell, either the installer would need to be tweaked or additional command line options are needed to specify directory locations (if I read the posts correctly).  We have done numerous installs with msi files using this service so we know that msi installers do install properly using it so we are looking for any help in getting your msi to work within this framework.
  • As answered before. The current "msi" is built for individual users to install. It is not implemented for what you are requesting.  I understand you would like to be able to install via SCCM, a feature to be considered but currently not supported.

Reply Children
No Data