Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING [Failed]:Updating Admin Console binaries. Check cmupdate.log for details

Flook

New Member
Messages
3
Reaction score
0
Points
1
Hi!
First of all I want to thank you, Prajwal, for your awesome guide! I'm using it to set up my SCCM for a little school as my graduate project.
I'm currently working on my graduate project and have chosen for Windows 10 Image deployment with SCCM 2012 R2. I've made multiple test sites before moving on to our customer (a little school).

Now I've tried to upgrade (via cloud service) my SCCM Console from version 1606 to 1610 by first doing the 1606 hotfix that was available. This succeeds. Whenever I try to run the 1610 upgrade I encounter an error. Heres the problem, the upgrade fails time to fime at following step: [Failed]:Updating Admin Console binaries. Check cmupdate.log for details. It's the second last step in the upgrade process. I've checked the cmupdate.log but can't really get the issue here.

Log file:
INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure CONFIGURATION_MANAGER_UPDATE 11/03/2017 11:22:36 4352 (0x1100) Turned on activation for service broker queue CONFIGURATION_MANAGER_UPDATE 11/03/2017 11:22:36 4352 (0x1100) Failed to apply update changes 0x80004005 CONFIGURATION_MANAGER_UPDATE 11/03/2017 11:22:36 4352 (0x1100) ERROR: Failed to process configuration manager update. CONFIGURATION_MANAGER_UPDATE 11/03/2017 11:22:36 4352 (0x1100) Waiting for changes to the "C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, servers will be polled in 1 second... CONFIGURATION_MANAGER_UPDATE 11/03/2017 11:22:36 4352 (0x1100) INFO: setup type: 1, top level: 1. CONFIGURATION_MANAGER_UPDATE 11/03/2017 11:22:37 4352 (0x1100)

I'm stuck at the moment as I've never encountered this error before in my test sites. I really love how SCCM works and the features of this product but man...do these errors (not just this one) can be a serious "p in the a" :(

If any one can find a solution i'd be thankfull!
 
I see the error Failed to apply update changes 0x80004005. Are there any other errors in cmupdate.log file ?.
 
Thanks for the fast reply. I watched my CMUpdate log while updating but can't see anything wrong. All goes well until (after) SQL objects. Have a look if you want in my CMupdate.log attached
 

Attachments

I'm curious if anyone had success fixing this error. I'm encountering the same error upgrading our hierarchy from 1606 to 1610 (CAS + 8 primary sites). The upgrade is only failing on one primary site, the only site we have hosted in AWS. I think the root error is a bit further up that log file:

"Failed to process AdminUI UI manifest xml. "

I've retried the install, rebooted the server, deleted the CMU_Staging folder contents to force the update data to be resynced, verified folder permissions, etc. Any ideas?
 
Was anyone ever able to fix this issue? I am getting the exact same issue. Looking at CMUpdate.log I see that it failed to process the AdminUI UI manifest.xml and further down in the log I see Failed to apply update changes 0x80004005. Looking at the SCCM Console under monitoring I see it failed updating the Admin Console Binaries. I have 1606 and have tried upgrading to 1610, I've tried 1702 and I've tried 1710 and I get the exact same thing on all of them. Any help with this would be appreciated
 

Forum statistics

Threads
7,025
Messages
27,489
Members
17,676
Latest member
chew

Trending content

Back
Top