Fix SCCM Console Install Failed with Error 1618

In this post, I will show you how to fix SCCM console install failed with error 1618. During the ConfigMgr console upgrade, the new version of the console failed to install with an error 1618. “Install failed because another program is installing (1618),” as per the ConfigMgrAdminUISetup.log file.

The last step you have to do when you install a new SCCM current branch update is to update the console. You must always upgrade the console to the latest version. The older files are updated with a new set of files during the console upgrade, which is a crucial step. Microsoft’s hotfixes and updates add new features to the SCCM console. Because of this reason, the console must be updated.

Most ConfigMgr installations upgrade their consoles without any problems, but occasionally, you might get console upgrade error 1618. Another good example of a console install or upgrade error is SCCM Console Upgrade Error 503 Remote Server Unavailable.

PatchMyPC HorizontalAD
Patch My PC Sponsored AD

When I attempted to upgrade the SCCM console in my production setup, I did not see any upgrade progress windows. At that point, I restarted the server and tried to upgrade the console, but nothing changed. When I reviewed the ConfigMgrAdminUISetup.log on the server, I noticed the error 1618, which halted the console upgrade. I have upgraded the ConfigMgr server’s console many times, but I have never seen the error 1618. Let’s understand what exactly this error code 1618 is that appears during console upgrades and the steps to resolve it.

Useful Read: Fix SCCM Extend AD Schema Error Code 1355

Fix SCCM Console Install Failed with Error 1618

Let’s take a look at how to fix SCCM console installation failure with error 1618. The error 1618 shows up because another program is also being installed on the same device during the console upgrade. Closing all the other .msi installation process resolves error code 1618. In this case, the installation of the ConfigMgr console is stopped, and error 1618 is logged to the ConfigMgrAdminUISetup.log file.

To begin, in the event of console installation errors, open the ConfigMgrAdminUISetup.log file. You may open the console log files with the Configuration Manager Trace log tool. Examine the log file for errors that will assist you in determining the reason for installation. As shown in the screenshot below, the SCCM console installation failed for me because another program was also being installed at the same time (Error 1618). The conflict program or application that is halting the console upgrade with error 1618 is revealed in the log file and the admins have to find this out by themselves.

SCCM Console Install Failed with Error 1618
SCCM Console Install Failed with Error 1618

Below lines are from ConfigMgrAdminUISetup.log and take a look at the last line – Installation failed because another program is installing (1618). In addition to that I also saw the below two lines.

  • Cannot find MSPs
  • Cannot find ReportViewerLP_*s
==========[ uisetup started in process 8780 ]==========(0x0000)
UI Setup invoked with args - "C:\Program Files (x86)\ConfigMgr10\AdminconsoleSetup\469A3000-14DA-425E-B288-4B0E16DB87C4\ConsoleSetup.exe" /qb
Created temp - C:\Program Files (x86)\ConfigMgr10
Created temp - C:\Program Files (x86)\ConfigMgr10\AdminconsoleSetup\
Created temp - C:\Program Files (x86)\ConfigMgr10\AdminconsoleSetup\{E7F3840F-C637-4AB4-8E0E-30DB1CBE2235}\
Copying Adminconsole.msi to C:\Program Files (x86)\ConfigMgr10\AdminconsoleSetup\{E7F3840F-C637-4AB4-8E0E-30DB1CBE2235}\\Adminconsole.msi
Copying Completed
Default UI lang code 1033
Language code found 1033
Language Locale found 1033
Setting LangPackDir to C:\Program Files (x86)\ConfigMgr10\AdminconsoleSetup\469A3000-14DA-425E-B288-4B0E16DB87C4\LanguagePack
Scaning for MSPs under C:\Program Files (x86)\ConfigMgr10\AdminconsoleSetup\469A3000-14DA-425E-B288-4B0E16DB87C4\LanguagePack
Scanning for ReportViewerLP_*s under C:\Program Files (x86)\ConfigMgr10\AdminconsoleSetup\469A3000-14DA-425E-B288-4B0E16DB87C4\LanguagePack
Cannot find MSPs
Cannot find ReportViewerLP_*s
New console product version is 5.1906.1096.1000
Installed console product version is 5.1902.1085.1000
MSI PROPERTIES are INSTALL=ALL ALLUSERS=1 TARGETDIR="C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\" DEFAULTSITESERVERNAME=CORPSCCM.PRAJWAL.ORG ADDLOCAL="AdminConsole,SCUIFramework"
Running installation package
Package: C:\Program Files (x86)\ConfigMgr10\AdminconsoleSetup\{E7F3840F-C637-4AB4-8E0E-30DB1CBE2235}\\Adminconsole.msi
Log: C:\ConfigMgrAdminUISetupVerbose.log
Properties: INSTALL=ALL ALLUSERS=1 TARGETDIR="C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\" DEFAULTSITESERVERNAME=CORPSCCM.PRAJWAL.ORG ADDLOCAL="AdminConsole,SCUIFramework"
Installation failed because another program is installing (1618)

About Error Code 1618

As I mentioned earlier, the error code 1618 is a MSI installation error code and this error is caused by multiple .msi installations running at the same time on the device. To sort this error, you must stop all related MSI install processes running in the background or restart the server.

In my case, rather than stopping the MSI Install processes, I restarted the server once. After the server restart I attempted to upgrade the SCCM console and that actually resolved the error 1618. The console upgrade worked perfectly fine.

The following lines from ConfigMgrAdminUISetupVerbose.log file confirms that console upgrade is successful.

  • Windows Installer installed the product. Product Name: System Center Configuration Manager Console. Product Version: 5.1906.1096.1000. Installation success or error status: 0.
SCCM Console Install Failed with Error 1618
Fix SCCM Console Install Failed with Error 1618