SCCM Error 0x643(1603) When Deploying Software

Scenario

You are deploying an SCCM application. The application installation fails resulting in an error code 0x643(1603)

Troubleshooting

The first thing I wanted to do was to verify what command SCCM was trying to run. To do this, I went to the AppEnforce log from the client on which I as trying to install the software. It showed the following:

Context: Machine
    Command line: msiexec /i "PBIDesktop_x64.msi" /q
    Allow user interaction: No
    UI mode: 0
    User token: not null
    Session Id: 2
    Content path: C:\Windows\ccmcache\d

And the result was as follows:

<![LOG[    Process 3912 terminated with exitcode: 1603]LOG]!>
<![LOG[    Unmatched exit code (1603) is considered an execution failure.]LOG]!>

So the .msi failed when trying to install. Fortunately, you can turn on msi logging to get more information on why the .msi installation failed.  To do this, see this article: https://support.microsoft.com/en-us/help/223300/how-to-enable-windows-installer-logging

Turn On MSI Logging

Open Regedit and navigate to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows

Once there, create a key called Installer. Then create a REG_SZ called Logging in that key and a REG_DWORD called Debug. The Logging value should be voicewarmupx and the Debug value should be 7.

After you have made these changes, attempt the install of the .msi as you did before. After it fails, you will have an MSI log in the following folder C:\Windows\Temp

You will see several MSIxxxx files. Select the one from the time and date when you attempted the failed install.

Cause

In my case, the log was very helpful. It showed the following:

EULA has not been accepted while executing the installation in reduced UI mode. Please add the flag ACCEPT_EULA=1 to the command line.

Resolution

I added this to the command line in the SCCM application, and tested and it resolved the issue.

NOTE: Be sure to remove the "Installer" key in the registry after you complete your troubleshooting.