Under Review
Last Updated: 17 Mar 2026 15:33 by ADMIN
Hakon
Created on: 21 Jan 2026 09:51
Category: Installer and VS Extensions
Type: Bug Report
0
The upgrade wizard fails with an XML error when trying to upgrade a project

We have a WebForms application with Telerik AJAX components which we have successfully upgraded using the wizard for years. Starting with product version 2025.4.1210 and persisting in the latest version, 2025.4.1321, the upgrade wizard fails with the following error message.

The Telerik extension to VS is up to date, and it doesn't seem to help to run this in VS 2022.

An error occurred while running the wizard.

Error executing custom action Telerik.Web.UI.VSX.Actions.MultiProjectUpdateReferencesAction: System.InvalidOperationException: There is an error in XML document (3, 2). ---> System.Xml.XmlException: Name cannot begin with the '<' character, hexadecimal value 0x3C. Line 3, position 2.
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.ParseQName(Boolean isQName, Int32 startOffset, Int32& colonPos)
   at System.Xml.XmlTextReaderImpl.ParseElement()
   at System.Xml.XmlTextReaderImpl.ParseElementContent()
   at System.Xml.XmlReader.ReadStartElement()
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderSolutionDistributionDefinition.Read2_SolutionDistributionDefinition(Boolean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderSolutionDistributionDefinition.Read3_Distribution()
   --- End of inner exception stack trace ---
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Xml.Serialization.XmlSerializer.Deserialize(TextReader textReader)
   at Telerik.VSX.Helpers.Serializer`1.Deserialize(String filePath)
   at Telerik.VSX.SolutionManagement.SolutionDistributionOperator.<>c__DisplayClass11_0.<DeserializeSolutionDistributionDefinition>b__0()
   at Telerik.VSX.SolutionManagement.SolutionDistributionOperator.HandleUnauthorizedAccessException(Action action)
   at Telerik.VSX.SolutionManagement.SolutionDistributionOperator.DeserializeSolutionDistributionDefinition(String distributionFilePath)
   at Telerik.VSX.SolutionManagement.SolutionDistributionOperator.<>c__DisplayClass10_0.<CreateSolutionDistribution>b__0()
   at Telerik.VSX.SolutionManagement.SolutionDistributionOperator.HandleUnauthorizedAccessException(Action action)
   at Telerik.VSX.SolutionManagement.SolutionDistributionOperator.CreateSolutionDistribution(String distributionFilePath, DistributionInfo distributionInfo)
   at Telerik.VSX.SolutionManagement.SolutionDistributionsContext.LoadSolutionDistributionDefinitions(DistributionInfo distributionInfo)
   at Telerik.VSX.Actions.MultiProjectUpdateReferencesActionBase`1.CreateSolutionDistributionsContext(WizardContext context)
   at Telerik.VSX.Actions.MultiProjectUpdateReferencesActionBase`1.Execute(WizardContext wizardContext, IPropertyDataDictionary arguments)
   at Telerik.VSX.WizardEngine.ActionManager.ExecActions()

9 comments
ADMIN
Maria
Posted on: 17 Mar 2026 15:33

Hello Hakon,

Thank you for the update. I’m glad to hear you were able to identify the issue and complete the upgrade successfully. Since it contained leftover merge artifacts, it might be worth considering adding this file to your .gitignore. That can help avoid similar issues in the future, especially that this folder is generated when you build the project.

Let me know if you have any other questions.

Regards,
Maria
Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Telerik family, check out our getting started resources
Hakon
Posted on: 17 Mar 2026 10:20

Well, this was somewhat embarrassing, but it helped to learn about the lib\distribution.xml file.

I had a look at it and it contained remnant of what must have been an unsuccessful git merge at some point. I deleted the offending lines of gibberish, and consequently performed a successful upgrade using the Upgrade wizard.

Thank you for your assistance!

Case closed.

ADMIN
Maria
Posted on: 17 Mar 2026 09:10

Hеllo Hakon,

Thank you for providing the file. I checked it, and the XML file is not corrupted, and its encoding is correct.

While debugging the source code, I noticed that another distribution XML file is being used, which is located in the lib folder of the project. Could you please send us that file as well so we can check whether there might be an issue in it and investigate further? In addition, please try deleting the folder, rebuilding the project, and then running the Upgrade Wizard again. Let us know what the result is after trying these steps.

Looking forward to your reply.

Regards,
Maria
Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Telerik family, check out our getting started resources
Hakon
Posted on: 10 Mar 2026 21:50

Sorry for the delay. Have tried to re-install the extension, but there is no change in behaviour.

I have attached the Distribution.xml (zipped) from the extension folder.

Attached Files:
ADMIN
Maria
Posted on: 25 Feb 2026 14:45

Hello Akon,

I apologize for the delay in my response. The XML file that we need is located in the extension directory. Please follow the steps below to find it: 

1. Navigate to C:\\Users\\User\\AppData\\Local\\Microsoft\\VisualStudio. Refer to the image below for example:

In this directory, you will see generated folders corresponding to different Visual Studio versions. Version 16 - Visual Studio 2019, version 17 - Visual Studio 2022, and Version 18 - Visual Studio 2026. 

2. Open the folder for the Visual Studio version you are currently using. Inside, locate and open the Extensions folder. This folder contains all installed extensions. Note that the folders for the installed extensions are generated and on your machine will be different from the example image below. 

Find the folder corresponding to the AJAX extension, the main assembly for the product will be placed there - Telerik.Web.UI.dll. Inside, you should find the Configuration folder, and inside there will be the DistributionInfo.xml file that is required. Please attached the file so we can observe what is the problem. 

I hope this information helps. If you have any difficulties locating it, please let me know, and I will be happy to assist further.

Regards,
Maria
Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Telerik family, check out our getting started resources
Hakon
Posted on: 25 Feb 2026 06:35

Hi Maria, it's been a while since you came back to the office. Still looking forward to any additional details that may prove useful. I've tried upgrading the wizard extension after the latest release of the AJAX components, but I get the same error.

ADMIN
Maria
Posted on: 16 Feb 2026 17:16

Hеllo Hakon, 

I apologize for the delayed response. I was out of office. I will write to you tomorrow with additional details.

Thank you for your patience.

Regards,
Maria
Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Telerik family, check out our getting started resources
Hakon
Posted on: 10 Feb 2026 06:48

Maria, thank you for your answer!

I must admit that I don't know where the extension directory resides, nor the name of the "internal XML" file. I would suspect this file is internal to the upgrade package with the new version of the Telerik components, so a hint of what file name to search for, would be most welcome.

ADMIN
Maria
Posted on: 26 Jan 2026 14:19

Hello Hacon, 

Thank you for the information.

The error that you are encountering during the upgrade process occurs when our upgrade wizard attempts to deserialize an internal XML containing the distribution information used by the Visual Studio extension. To try to resolve this, please follow the steps below:

1. Check if the XML file exists in the extension directory.
2. Verify that the file is a valid XML, and that it is saved with UTF-8 encoding.
3. If the file exists and is valid, try uninstalling and reinstalling the extension. 

If the error still occurs after reinstalling the extension, the XML file may be corrupted or incompatible. You can attach the file to review its contents.

If the issue persists even after following the above steps, please don’t hesitate to contact us again to assist further.

Regards,
Maria
Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Telerik family, check out our getting started resources