Using the MECM Console Extensions to install receives the following error:
AdminUI.ExtensionInstaller.exe Error: 0 : Unable to install extension: XXXX because it is an invalid extension. Exception:Microsoft.ConfigurationManagement.AdminConsole.ExtensionInstaller.InvalidCustomExtensionException: Unable to validate XXXX:4.8.2109.3303 because Manifest doesn’t exists in the cab.
Do you have any antivirus programs installed on this machine that could be interfering with the install by chance? We weren’t able to recreate this issue in our 2107 lab environment.
Please attempt to use our standalone community edition installer requested here: Free Tool Download - Recast Software and let us know if you run into the same issue.
Just installed Right Click Tools-4.8.2109.3303.msi fine.
However, that was not the point of this original post. There seems to be a missing manifest in the CAB file for MECM Console Extensions. Has anyone from Recast Software reviewed if the CAB file contains a manifest file?
This issue that you’re experiencing is local to your environment. We’re able to successfully complete the console extension installation in our test lab using the same MECM, Console, and RCT versions.
hi b0n3z,
Just to let you know you aren’t alone. (unless someone finds a fix, don’t need a response). We have 4 of these in our environment too (out of about 15 users) where the rct console extension fails to install and we have to use the MSI instead, I haven’t been able to find a fix either. The latest one is on my freshly reimaged machine. (disabling Mcafee didn’t help) MECM 2107(with patch). It was installed fine on my machine before I reimaged it too.
Uninstall, reinstall webview2 (and another extension) without a problem, just won’t install RCT. Even tried copying the files from a working machine to the empty folder in “C:\Program Files (x86)\MECM Console\Extensions\99429045-5ed9-42f0-992b-d73f628e6131\4.8.2109.3303” - same error.
AdminUI.ExtensionInstaller.exe Information: 0 : Found 1 extensions need install/update.
DateTime=2021-12-16T04:03:38.6131934Z
AdminUI.ExtensionInstaller.exe Information: 0 : Applying Extension 99429045-5ed9-42f0-992b-d73f628e6131 Version:4.8.2109.3303
DateTime=2021-12-16T04:03:38.6131934Z
AdminUI.ExtensionInstaller.exe Error: 0 : Unable to install extension:99429045-5ed9-42f0-992b-d73f628e6131 because it is an invalid extension. Exception:Microsoft.ConfigurationManagement.AdminConsole.ExtensionInstaller.InvalidCustomExtensionException: Unable to validate 99429045-5ed9-42f0-992b-d73f628e6131:4.8.2109.3303 because Manifest doesn’t exists in the cab.
at Microsoft.ConfigurationManagement.AdminConsole.ExtensionInstaller.CustomExtensionInstallerBase.ValidateFiles(List1 customExtensionFiles) at Microsoft.ConfigurationManagement.AdminConsole.ExtensionInstaller.CustomExtensionInstallerBase.Install() at Microsoft.ConfigurationManagement.AdminConsole.ExtensionInstaller.CustomExtensionHandler.InstallExtensions(List1 extensionsMetadata)
side note, probably unrelated, but finding this in most of the default menus xml’s was interesting (time for an update )
Hope all is well! Is it possible you have a slightly outdated version of the extension by chance? If so, can you please try downloading the latest version from GitHub, re-approving, enabling it again, and reattempting the installation?
I talked to the ConfigMgr product group about this and they are tracking it as a bug on their side. If you can clear the AdminUI.ExtensionInstaller.log, repro the failure, and post the resulting I’ll send it on. They’d also like a screenshot of the %Program Files (x86)%\Microsoft Configuration Manager\AdminConsole\Extensions\99429045-5ed9-42f0-992b-d73f628e6131 folder where they install our extension.
To get to the point of installing the console extension the manifest and the content it describes has already been extracted, verified, and loaded into the ConfigMgr database. Having a manifest problem creep in at install time doesn’t make a lot of sense and is definitely not something we (Recast) can prevent.
Update: The ConfigMgr product team was aware of this already and it should be fixed in the 2111 release.
The problem arose in ConfigMgr upgrades previous to 2111; they were corrupting the console extension data stored in the DB. I’m told that upgrading to 2111 should fix this issue but if you’re not there yet you just need to delete the extension from the Console Extension node and then redownload it from Community Hub.
)