# What's new in QLM v20 and upgrade procedure QLM v20 was released on April 12, 2026. -> [Latest Version Release Notes](https://soraco.co/products/qlm/ReleaseNotes.html) Quick License Manager (QLM) v20 is a **foundational release** focused on modernizing the core architecture of the product to ensure long‑term stability, performance, and future innovation. While QLM v20 does not introduce a large set of new end‑user features, it represents a **major technological leap**. All QLM server components have been fully migrated from **.NET Framework 4.x to .NET 10**. This was a significant engineering effort that positions QLM on a modern, fully supported platform and enables us to evolve the product using the latest Microsoft technologies for years to come. In addition, the **QLM Portal has been completely rewritten** using modern frameworks (**Blazor and DevExpress**). This rewrite delivers improved usability, a cleaner user experience, and better overall performance, while laying the groundwork for future enhancements. As with every major release, **backward compatibility is fully maintained**. Existing customers can upgrade with confidence, and QLM v20 server components can be installed **side‑by‑side with QLM v1x server components**, allowing for a smooth and controlled transition. QLM v20 is an investment in the future of the platform—focused on modernization today so we can deliver faster innovation tomorrow. ### Important Changes in v20 #### License Server * The QLM License Server and all related server components have been upgraded from .NET Framework 4.6 to .NET 10. This is a significant architectural change that affects the License Server URLs used for communication. * **New QLM License Server URL** * The main URL to the QLM License server has changed from: * `http://localhost/Qlm/QlmLicenseServer/qlmservice.asmx` to * `http://localhost/Qlm/QlmLicenseServerNetCore/api/v1/QlmApi` * Instructions for redirecting the old License Server URL to the new URL are provided below and should be implemented to ensure backward compatibility. If you host your own License Server, review the upgrade instructions carefully before upgrading. * All integrations must be updated to use the new License Server URL. * The QLM Portal has been completely rewritten using DevExpress/Blazor and .NET 10, delivering improved performance, maintainability, and user experience. * The QLM Agent Windows Service now uses .NET 10. After installing QLM v20, you will need to reconfigure the credentials of the user account running the QLM Agent Windows Service. * **PayPal integration**\ If you are using PayPal, you **must update the IPN URL** to point to the new License Server endpoint (details provided below). * **E‑commerce integrations**\ All e‑commerce integrations must be updated to use the **new License Server URL**. * **Database security requirement (hosted License Server only)**\ Before upgrading, the QLM database login **must** have the `db_securityadmin` role.\ You can grant this role using the following command (replace `qlm_user` as needed): ```sql SQLEXEC sp_addrolemember N'db_securityadmin', N'qlm_user' ``` * **Azure integration**\ The procedure to integrate QLM with Azure has changed. Please refer to the latest documentation before upgrading. * **Authentication framework**\ QLM authentication now uses the **Microsoft Identity framework**, replacing **ASP.NET Membership**. * **Disaster Recovery Site** * Effective immediately, when hosting your License Server with Soraco, the DR site will only host the License Server component. The QLM Self Help, QLM Portal and QLM Customer Portal will not be available on the DR site. * The qlmredirect.xml must be updated with new entries for the QLM v20 License Server. See detailed instructions below. #### Client Side * Most client side QLM components now use .NET 10. * The QLM License Wizard XML settings file must be updated to reflect the new URL. ### .NET Support * The QlmLicenseLib.dll is now available for .NET4, .NET6, NET7, .NET8, .NET9 and .NET 10. * The QlmControls.dll is now available for .NET4, .NET6-Windows, .NET7-Windows, .NET8-Windows, .NET9-Windows, and .NET10-Windows. ### New Requirements * The QLM Management Console now requires .NET 10 (requires Windows 10 or higher). * The QLM Management Console and the QLM Portal now reference DevExpress 25.2.5. * New License Server requirements: * You must install the [.NET 10 Hosting Bundle ](https://dotnet.microsoft.com/en-us/download/dotnet/10.0)10.0.5 or greater * You must install [Microsoft OLE DB Driver for SQL Server v19](https://learn.microsoft.com/en-us/sql/connect/oledb/download-oledb-driver-for-sql-server?view=sql-server-ver17) * You must install [Visual C++ Redistributables for x86 and x64 (for Visual Studio 2017)](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170) ### Documentation The QLM Documentation has moved to: ### Upgrade Procedure To upgrade to QLM v20, you must first install the QLM Management Console on your client system by running qlmsetup20.exe. To determine if you are eligible for a v20 upgrade, you may contact us or click the About tab. If we are hosting your QLM License Server, contact us to upgrade the License Server. If you are hosting your own License Server, you can upgrade the License Server as described in the next sections. **License Server Changes** The QLM v20 License Server can be installed side-by-side with the QLM v19 or earlier License Server. **Automated Upgrade** If you originally installed QLM using **QlmLicenseServerSetup.exe**, running the latest version of **QlmLicenseServerSetup.exe** will automatically install QLM v20 License Server side‑by‑side with your existing QLM v1x installation. This allows you to upgrade safely without disrupting your current environment. **New URLs After Installation** After the QLM v20 License Server is installed, the following URLs will be available\ (replace `localhost` with your server name or domain): * QLM License Server ```html http://localhost/Qlm/QlmLicenseServerNetCore/api/v1/QlmApi ``` * QLM Self Help ```html http://localhost/Qlm/QlmCustomerSiteNetCore ``` * QLM Portal ```html http://localhost/Qlm/QlmPortalNetCore/QlmPortal ``` * QLM Customer Portal: ```html http://localhost/QlmCustomerPortalNetCore/qlm-portal-app ``` **Backup Before Upgrading (Strongly Recommended)** Before running the upgrade, **always back up both your QLM site and database**: * **Site backup**\ Make a copy of all existing **QLM License Server folders**. * **Database backup**\ Perform a standard **SQL Server backup** of the QLM database. These backups allow you to restore your environment quickly if necessary. *** **Required Post‑Installation Step: Database Schema Upgrade** Once the QLM v20 server components are installed, you **must upgrade the database schema**: 1. Launch the **QLM Management Console** 2. Go to the **Manage Keys** tab 3. Click **Sites** and select your site 4. Click **Upgrade DB Schema** #### Manual Upgrade **QLM License Server Upgrade** 1. Launch the QLM Management Console 2. Go to the Manage Keys tab, click Sites, select your site, then click Copy and set the name of the v20 License Server 3. In the Primary Site field, set the URL to (replace localhost with the name of your server/domain): 4. Go to the Deployment tab and set the information associated with your License Server (see screenshot below) 5. Click "Update Config Files" 6. Copy all the files located in %Public%\Public Documents\Quick License Manager\DeployToServer\ to your server, under the c:\inetpub\wwwroot\Qlm 7. On your server, in IIS, create the Application Pools below. When creating the Application Pool, select the option: No Managed Code. 1. QlmLicenseServerNetCore (only required if you do no want to redirect from your QLM v1x License Server to the QLM v20 License Server) 2. QlmCustomerSiteNetCore 3. QlmPortalNetCore 4. QlmCustomerPortalNetCore 8. In IIS, expand the Default Web Site node and locate the QLM virtual directory 9. Right mouse click QlmLicenseServerNetCore and select Convert to Application. When prompted to Add the Application, you have 2 options: 1. If you want to redirect your QLM v1x customers to QLM v20, set the same Application Pool as the one currently used for QLM v1x. 2. If you do not want to redirect, set the Application Pool to QlmLicenseServerNetCore. 10. Right mouse click QlmCustomerSiteNetCore and select Convert to Application. When prompted to Add the Application, set the Application Pool to QlmCustomerSiteNetCore 11. Right mouse click QlmPortalNetCore and select Convert to Application. When prompted to Add the Application, set the Application Pool to QlmPortalNetCore 12. Right mouse click QlmCustomerPortalNetCore and select Convert to Application. When prompted to Add the Application, set the Application Pool to QlmCustomerPortalNetCore 13. Right mouse click QlmCustomerPortalNetCore /qlm-portal-api and select Convert to Application. When prompted to Add the Application, set the Application Pool to QlmCustomerPortalNetCore 14. Right mouse click QlmCustomerPortalNetCore /qlm-portal-app and select Convert to Application. When prompted to Add the Application, set the Application Pool to QlmCustomerPortalNetCore 15. Once the License Server is updated, start the QLM Management Console, go to Sites and click on Upgrade Database Schema.
#### Redirection from old URL to new URL If you are upgrading from QLM v19 or earlier to QLM v20, you can configure the old license server to redirect to the v20 License Server by adding some entries to the QlmLicenseServer\web.config file. In order to perform the redirect, you must first install the URL Rewrite module which is available [here](https://www.iis.net/downloads/microsoft/url-rewrite). You must then update the legacy QlmLicenseServer\web.config as follows (note that the system.webserver section exists already so you should just add the relevant URL Rewrite section): ```xml ``` **Important**: when redirecting from an old License server to a v20 license server, the old license server and the v20 license server must use the same Application Pool.
#### PayPal Integration The URL to the QLM PayPal integration has changed from: [http://localhost/Qlm/QlmLicenseServer/qlmpaypalipn.aspx
](http://localhost/Qlm/QlmLicenseServer/qlmpaypalipn.aspx) To: [http://localhost/Qlm/QlmLicenseServerNetCore/api/PayPalIpn/notify](http://localhost/Qlm/QlmLicenseServerNetCore/api/v1/PayPalIpn/notify) #### Disaster Reovery Redirection The qlmredirect.xml that is used by the QLM Disaster Recovery framework needs to be updated to add new entries for the QLM v20 License Server as per the example below: ```xml https://qlm4.net/qlmdemo/qlmlicenseserver/qlmservice.asmx https://qlmdr4.net/qlmdemo/qlmlicenseserver/qlmservice.asmx https://qlm4.net/qlmdemo/QlmLicenseServerNetCore/api/v1/QlmApi https://qlmdr4.net/qlmdemo/QlmLicenseServerNetCore/api/v1/QlmApi ``` #### Source Code To upgrade your source code to QLM v20: * If you are upgrading from QLMv9 or earlier and if you are using the QLM License Wizard, be it the .NET Control or the standalone executable, you will need to customize the look & feel of the control and regenerate the settings XML file. Note that as of QLM v9, only one settings file is required. The UI Settings XML file is no longer required since all settings are stored in a single file. * If you have implemented floating licenses, it is recommended that you review the new QLM Enterprise [sample ](https://docs.soraco.co/docs/step-by-step-guides/how-to-support-floating-and-node-locked-licences-in-the-same-app)and follow the same approach as the new sample.