This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 5%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENM%3C/text%3E%3C/svg%3E)
After installing the CB 2006 update, the console displays a banner as shown in the attached image. When I attempt to "install the new console version" it fails with the attached error log. It appears to be a very similar issue to the one addressed in this article:
However, the recommended resolution doesn't work. It just seems as though I don't have the correct version of the source files expected by the installer. I have already installed all available hotfixes.
I ended up opening a case with Microsoft. Somehow during the upgrade from 2002 to 2006, and even during the hotfix upgrades, the latest versions of the following files were never added to the listed console installation sources. Microsoft support provided new ones that passed the hash check and everything is now working as expected:
ConfigMgr.AC_Extension.amd64.cab
ConfigMgr.AC_Extension.i386.cab
C:\Program Files\Microsoft Configuration Manager\bin\i386
C:\Program Files\Microsoft Configuration Manager\tools\ConsoleSetup
The recommended actions in the articles that @AllenLiu-MSFT and I found assume that the correct source files are somewhere on the site server. This wasn't the case for me. However, thank you for your kind assistance.
Thank you very much for the update and we're glad the problem is solved now. If you have any questions in future, we warmly welcome you to post in this forum again.
Have a nice day!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 18%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
@AllenLiu-MSFT is there a way for me to get these files as well without opening my own support case? I have an identical issue and followed the other workflows in this thread to the exact same (lack of) results as @NotSoMagic Mike and would like to try replacing the existing .cab file with ones that pass the hash check.
EDIT: for 2006 with the latest hotfix, here is the the payload from which the .cab files can be extracted in SMSSETUP\bin\i386 - https://download.microsoft.com/download/9/1/1/911364aa-dc85-447c-8e40-ec6eea6204af/KB4578605/FA345346-6C1E-408E-9B05-C92A2B2333AE.cab
@NotSoMagic Mike
Thank you for posting in Microsoft Q&A forum.
Did you run the console with admin privileges? Make sure you have administrative rights to click the "Install the new console version".
You may refer to:
https://www.walshamsolutions.com/sccm-1906-required-component-missing-error-after-console-upgrade
And I have encountered a similar problem, you may rename the AdminConsole to AdminConsole.old and then install the console manually:
https://www.windows-noob.com/forums/topic/16606-how-to-fix-there-is-not-enough-available-disk-space-on-when-upgrading-the-configmgr-adminconsole/
Note: The third-party link is just for your reference.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Neither running as administrator, nor renaming the AdminConsole folder resolved my issue.
For the second link, do you according to the ConfigMgrAdminUISetupVerbose.log to find the path corresponding to TARGETDIR and CURRENTDIRECTORY?
Or do you have some wrong message in ConfigMgrAdminUISetupVerbose.log?
Hello, After installing the CB 2303, the console displays an error during the update.
Log: D:\Program Files\Microsoft Configuration Manager\AdminConsole\AdminUILog.log
As per @AllenLiu-MSFT 's guidance, the solution was to rename AdminConsole to AdminConsole.old and then install the console manually.
Thanks.