When I reviewed the ConfigMgrAdminUISetup.log on the server, I noticed the error 1618, which halted the console upgrade. At that point, I restarted the server and tried to upgrade the console, but nothing changed. When I attempted to upgrade the SCCM console in my production setup, I did not see any upgrade progress windows. Another good example of a console install or upgrade error is SCCM Console Upgrade Error 503 Remote Server Unavailable. Most ConfigMgr installations upgrade their consoles without any problems, but occasionally, you might get console upgrade error 1618. Because of this reason, the console must be updated. Microsoft’s hotfixes and updates add new features to the SCCM console. The older files are updated with a new set of files during the console upgrade, which is a crucial step.

You must always upgrade the console to the latest version.

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

Java installation error code 1618