Remove the Trial Version Message

Jan 16, 2026
3 minutes to read

After you purchased a license, register your products as described in this help topic.

.NET ProductsConvert a Trial Version to a Licensed VersionDevExtreme ComponentsObtain and Validate Your License Key

If your .NET project continues to display a trial message, use the troubleshooting guide below.

Common Steps

The following steps help you clear up any IDE or NuGet cache that may include outdated licensing information.

Close your IDE.
Update your license key.
- If you use our Unified Component Installer : run the setup wizard in Modify mode, and login with your DevExpress.com credentials. The wizard updates your license key automatically.
- If you use other installation methods : download your up-to-date .NET license key from the DevExpress Download Manager and paste it to the corresponding text file or environment variable. See the following help topic for additional information: License Key for DevExpress .NET Products.
Delete bin and obj folders and clear NuGet cache (see Clearing local folders).
Reboot your machine (avoid possible project binary locks and re-initialization issues in your IDE and other apps).
Open your IDE and rebuild your projects.

For versions prior to v16.1.12 and v16.2.7, the issue can occur if your machine has the FIPS algorithm policy enforced:

Show the solution

If you develop with an older DevExpress build and the use of FIPS Algorithm Policy at the OS level is required, you can disable FIPS Algorithm Policy only for Visual Studio. Include the following code in your Visual Studio’s devenv.exe.config file located in the Visual Studio’s .*\Common7\IDE subfolder. This action does not affect the information security on your computer, but allows the project to use the standard licensing mechanism utilized in our libraries:

xml

<configuration>  
  <runtime>  
    <enforceFIPSPolicy enabled="0" />  
  </runtime>  
</configuration>

Alternatively, you can proceed at the application level and modify the enforceFIPSPolicy token similarly in the application’s configuration file. Take a look at the <enforceFIPSPolicy> Element article for more information.

You can also install a later version in which this problem was solved: 16.1.12+ and 16.2.7+.

ASP.NET Web Forms and MVC

For ASP.NET Web Forms and MVC applications, you can also clear “Temporary ASP.NET Files” directories. Use the DevExpress Temporary ASP.NET Files Clearer to clear the following “Temporary ASP.NET Files” directories (you can also clear these directories manually):

C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\
C:\Users[your_user_name]\AppData\Local\Temp\Temporary ASP.NET Files\

Follow these guides for details:

WinForms

You can find information on most common issues that may occur after you migrate to a newer version of DevExpress products here: DevExpress WinForms Troubleshooting - Upgrade Projects.