Added new kb article handling-license-file-name-changes

distribution-and-licensing/license-key.md

@@ -196,4 +196,5 @@ Starting with the 2025 Q2 release of the product in May 2025, all conditions abo
 * [License Agreement]({%slug license-agreement%})
 * [Redistributing Telerik Document Processing]({%slug installation-deploying-telerik-document-processing%})
 * [Unable to find package Telerik.Licensing]({%slug dpl-package-update-failure-license%})
+* [Handling License Key File Name and Environment Variable Name Changes in the 2025 Q1 Release]({%slug handling-license-file-name-changes%})
 

knowledge-base/handling-license-file-name-changes.md

@@ -0,0 +1,41 @@
+---
+title: Handling License Key File Name and Environment Variable Name Changes in the 2025 Q1 Release
+description: Learn how to handle license key file and environment variable name changes introduced with the 2025 Q1 release. 
+type: troubleshooting
+page_title: Handling License Key File Name and Environment Variable Name Changes in the 2025 Q1 Release
+slug: handling-license-file-name-changes
+tags: license,key,file,name,2025,change
+res_type: kb 
+---
+
+## Environment
+
+| Version | Product | Author | 
+| ---- | ---- | ---- | 
+| Q1 2025| Telerik Document Processing |[Desislava Yordanova](https://www.telerik.com/blogs/author/desislava-yordanova)| 
+
+## Description
+
+After downloading the License Key file by using the VS2022 extensions menu:
+![Download License key](images/download-license-key.png)  
+
+when building a simple console app with the Telerik Document Processing libraries, you get the following error:
+
+![License error](images/license-error.png)  
+
+## Solution
+
+It may be caused by an old [KENDO_UI_LICENSE environment variable](https://docs.telerik.com/kendo-ui/knowledge-base/license-key-file-name-and-environment-variable). So, delete it and invoke `refreshenv` command. If the rebuild has the same error again:
+
+1\. Go to telerik.com and generate a new [License Key](https://www.telerik.com/account/your-licenses/license-keys). 
+
+2\. Compare the license key with the one downloaded from the extensions. If it indeed looks different than the one VS2022 got, replace the original telerik-license.txt file with the newly downloaded one.
+
+3\.Next, I restart VS2022 (to ensure it has a fresh copy env vars) and compile the project. It is expected to work:
+
+
+![License Fixed](images/license-fixed.png)   
+
+## See Also
+
+* [Unable to find package Telerik.Licensing]({%slug dpl-package-update-failure-license%})