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 Upgrade stuck in installing state from 2111

  • Thread starter Thread starter tpaofai
  • Start date Start date
  • Replies Replies 1
  • Views Views 3K

tpaofai

New Member
Messages
2
Reaction score
0
Points
0
Hi,
I try to upgrade from 2111 to 2211 but it is stuck to installing state.
The installation state is :
  • Check Site Server readiness (in progress)
  • Stop CONFIGURATION_MANAGER_UPDATE service (completed)
  • Update CONFIGURATION_MANAGER_UPDATE service (In progress)
  • Extract Update package (Completed)
  • Check site readiness (In progress)
I check the hman.log, only these errors : "Failed 'C', 874, 0x8009310b", "Failed to read certificate context from file 'readme.txt', 0x8009310b", "Failed to process TPM certs cab, 0x8009310b" appear but on other forums mentionned that this can be ignore and will be fixed on later build.
Last error in hman is "Failed to validate version for file C:\Program Files\Microsoft Configuration Manager\CMUStaging\BAD30974-7608-45F6-B2CE-78FB3900E19A\SMSSetup\bin\x64\setupcore.dll (C:\Program Files\Microsoft Configuration Manager\bin\x64\setupcore.dll)". Not sure if it's related to my issue.

But the most interesting one is from cmupdate.log. The only error that I have is "ERROR: Failed to execute SqlCMUpdateInitScripts." and I think that my issue is there.
Did you already faced that one ?
I don't find anything with that.

Thank you
 
Hi,
I managed to fix myself this issue. Very strange the setupcore.dll was more recent than the original one from cd.latest folder.
So I replaced this file C:\Program Files\Microsoft Configuration Manager\bin\x64\setupcore.dll from the same one located in C:\Program Files\Microsoft Configuration Manager\cd.latest\bin\x64\setupcore.dll and this fixed my issue.
So it wasn't a SQL issue.
Thank you
 
Back
Top