Session test: logged out
Skip to content

How can we help?

Skip to content
  • There are no suggestions because the search field is empty.

Azure Virtual Desktop (AVD) Deployments of Foxit PDF Editor

Explains how to deploy Foxit PDF Editor in Azure Virtual Desktop (AVD) environments.

Answer

Support for Foxit PDF Editor v11 and v12 has been discontinued as of August 13, 2025. Upgrade to v14 to continue receiving support.

 

The Admin Console supports entitlement management for Foxit PDF Editor Windows installed in an Azure Virtual Desktop (AVD) environment.

Audience:

IT Admins looking to customize and deploy Foxit PDF Editor to Azure Virtual Desktop

In this article:

System requirements
  • Deploy on one of the following to any version of Foxit PDF Editor Windows version 12.1 and up:
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016, Windows 10
    • Windows Server 2012 R2 standard
    • Windows Server 2008 R2
Install Foxit PDF Editor Windows

The following method should be used to install the client (the version is not lower than PDF Editor for Windows 12.1) on AVD.

Open the cmd command line and execute the command

  • If it is the msi version, add the parameter USERMLICENSE=1 USEVENIDENTITY=1 after the path of the installation package.
C:\>FoxitPDFEditor20241_L10N_Setup.msi USERMLICENSE=1 USEVENIDENTITY=1

 

  • If it is the exe version, add the parameter /UseRMLicense /UseVEnIdentity after the path of the installation package.
C:\>FoxitPDFEditor20241_L10N_Setup.exe /UseRMLicense /UseVEnIdentity

 

If the deployment is successful, the registry key UseRMLicense and UseVEnIdentity will be set to 1.
For 32-bit Editor: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Foxit Software\Foxit PDF Editor   Keys:   UseRMLicense = 1   UseVEnIdentity = 1

For 64-bit Editor: HKEY_LOCAL_MACHINE\SOFTWARE\Foxit Software\Foxit PDF Editor Keys: UseRMLicense = 1 UseVEnIdentity = 1
Tuning for virtual environments

Tuning helps mitigate performance issues, simplifies the end user experience, and allows you to disable features and behaviors that should not be accessible to end users in an IT-managed environment.

Licensing

Only licensed users should have access to the virtual Foxit PDF Editor instance. For more information, refer to the Software license terms.

AVD deployments support the following licensing options:

  • Named user licensing

Named user licensing deployments

With named user licensing, end users simply “activate” Foxit PDF Editor by logging in to the software. License-related data is saved in the user's "AppData/Roaming/Foxit Software/" folder and registry hive "HKEY_CURRENT_USER\SOFTWARE\Foxit Software\Foxit PDF Editor 12.0\Advanced" which is synced to the VM on login.

1. Set up profile redirection. User profile data in roaming folder as well as the HKCU hive must sync to the VM instance on which the user logs in.

Admins should ensure that such data is saved on user logout or disconnect. Some systems provide VM tools; for example, Citrix (Citrix Profile Management) and VMware Horizon (View Personal Management). At a minimum, sync the following:

Inclusion list for

Exclusion list

User configuration redirection for v12.x %UserProfile%AppData\Roaming\Foxit Software
  • %UserProfile%\AppData\Roaming\Foxit Software\Foxit PDF Editor\FxCEF32
  • %UserProfile%\AppData\Roaming\Foxit Software\Addon
User configuration redirection for v13.x %UserProfile%AppData\Roaming\Foxit Software
  • %UserProfile%\AppData\Roaming\Foxit Software\Classic\Foxit PDF Editor\FxWebView
  • %UserProfile%\AppData\Roaming\Foxit Software\Classic\Addon
User configuration redirection for v2023.3 and above %UserProfile%AppData\Roaming\Foxit Software
  • %UserProfile%\AppData\Roaming\Foxit Software\Continuous\Foxit PDF Editor\FxWebView
  • %UserProfile%\AppData\Roaming\Foxit Software\Continuous\Addon
Registry synchronization HKEY_CURRENT_USER\Software\Foxit Software  

2. Customize the package using the Foxit Customization Wizard

3. Deploy it as usual.

Connect to Azure Virtual Desktop | Microsoft Learn