How to Fix SCCM ConfigMgr CU 1 Installation rename operations pending Error

How to Fix SCCM ConfigMgr CU 1 Installation rename operations pending Error. I’ve encountered following errors while installing CU1 “configmgr2012adminui-rtm-kb2717295-i386.msp”.

This is applicable for all the systems with “CM 2012 Admin Console”. Whenever you get a warning in the prerequisite checker like below it’s better to restart the server and then install the CU fix.

How to Fix SCCM ConfigMgr CU 1 Installation rename operations pending Error

An earlier software installation still has outstanding file rename operations pending. Before continuing with setup, you should restart the computer to allow operations to complete.

Error One

(Not sure, how come there is a spelling mistake in ConfigMgr Log file)

Fatal error 0x87d01101 encountered for program Cumulative update 1 – console update install. This program will not retry.

The first error 0x87d01101 was encountered during the installation of the CU1 CM 2012 Admin console update through the “Software Deployment” method. The deployment got failed probably because the console was open on the site server. I’ve closed the console and rerun the deployment. This issue got resolved.

Error Two

MSI (s) (FC:F0) [13:59:04:648]: SOURCEMGMT: Failed to resolve source

MSI (s) (FC:F0) [13:59:04:648]: Product: Microsoft System Center 2012 Configuration Manager Console — Error 1706. An installation package for the product Microsoft System Center 2012 Configuration Manager Console cannot be found. Try the installation again using a valid copy of the installation package ‘Adminconsole.msi’.

Error 1706. An installation package for the product Microsoft System Center 2012 Configuration Manager Console cannot be found. Try the installation again using a valid copy of the installation package ‘Adminconsole.msi’.

The Second error was encountered when I tried to install the same update manually on a different site server. I’ve used the command line which is given in the package program. It got failed with the most common MSI error 1603. Now? Had a look at the log file in more detail and once again “Return value 3” helped me to reach the actual error “SOURCEMGMT: Failed to resolve source”.

Command Line

msiexec.exe /p configmgr2012adminui-rtm-kb2717295-i386.msp /L*v %TEMP%\configmgr2012adminui-rtm-kb2717295-i386.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous

Now the things are much clear. The installer is not able to find the ‘Adminconsole.msi’ file in the temp folder of the user who installed the site server and or admin console. Is there any logic? I’m not that BIG. Maybe, big people must have some knowledge about the logic behind this.

My goal is to solve this issue. What do I do? Removed the silent switch (/q) from the above command line and tried again. The installation stopped with the following error.

Setup is searching for installed applications….

Click OK to try again, or enter an alternate path to a folder containing the installation package “Adminconsole.msi” in the box below

Now it’s pretty easy to guide the wizard to a location where we’ve “AdminConsole.MSI” and click OK. Now what? The update got installed successfully with the latest “AdminUI.Common.dll” file version “5.0.7711.200”.

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…