If you’re trying to upgrade your ConfigMgr console to a newer version and encounter an XML format error in the configuration file, this guide provides the solution.
I recently upgraded the Configuration Manager to version 2503 on one of the production servers. While the upgrade process went smoothly, the console upgrade failed. After restarting the server and attempting the upgrade again, the console abruptly closed.
The below screenshot is the actual issue that I encountered during my console upgrade. The error reads: XML format error in connected console configuration file. Relaunching the console manually reported the same error.
I have done many console upgrades and never encountered this issue before. It is interesting to note that this issue is not documented anywhere. Maybe it’s just me who gets these weird errors?🤔 Trust me, the error message offers very little information, making it difficult to troubleshoot effectively.
Next, I looked at all the logs related to console, but none of them had any information that could help me. Don’t panic if you’re encountering the same error, I have covered the solution for it.
Fix Console Upgrade XML Format Error in Config File
An XML format error in the configuration file may arise due to corrupt console upgrade files or a malfunctioning console extension. To resolve this issue, uninstall the SCCM console and manually install the latest version.
To remove the existing ConfigMgr console, go to Control Panel > Programs > Programs and Features. Select Microsoft Configuration Manager console and choose Uninstall.
Once the console is removed, you must restart the server once. This will remove the traces of existing console folders, logs, and files.
Now, log in to the server and install the latest SCCM console on the server. You can grab the console installation files from any of the below locations.
- On Configuration Manager Site server: <ConfigMgr site server installation path>\Tools\ConsoleSetup\
- SCCM installation media: <Configuration Manager installation media>\SMSSETUP\BIN\I386
Run the ConsoleSetup.exe to install the latest version of console on the server.
When the console is installed, launch it, and you will notice that you’re running the latest console version and the XML format error no longer appears.
You may see a console notification asking you to install the WebView2 extension. Install it because it is essential for displaying features such as custom tabs in the Software Center.
That’s all for this guide. I believe that was a simple fix, and now you can start managing your setup using Configuration Manager.
Great article Prajwal,
But if you must know, you just need to delete the Microsoft.ConfigurationManagement.ApplicationManagement.config file in the %LocalAppData%\Microsoft\ConfigMgr10 folder and the message goes away. No worries, this file will be created again next time you launch the MCM console again.
Thank you,