VDI client and plugin version compatibility and management

Zoom maintains seamless compatibility between VDI Host clients and VDI Plugins through an internal versioning system. This system enables VDI Workplace clients to support older plugin versions while ensuring smooth updates, even when plugin versions appear newer than the client.

Table of Contents

Plugin Version Management

The policy option AutoUpdatePluginVersion can be used to specify the auto-upgrade plugin version. The auto-update plugin will prioritize the specified version. If the specified version is invalid, the host version will be used to find the closest matching plugin.

When specifying the plugin version, the value must fall within the acceptable range for the host client's version. Invalid values will be ignored, and a value matching the host value will be used instead. The table below provides version information for Windows and macOS plugin versions supported by Zoom VDI Plugin Management.

Definitions of compatibility between the VDI clients and plugins

Compatible VDI plugins have undergone comprehensive regression testing, with all major features verified to work properly with the corresponding VDI client. These plugins are fully supported for regular use.

Plugins with limited support have only undergone basic feature regression testing. While core meeting functions (basic audio, video, virtual background, sharing, and annotation) work, these combinations are not recommended for long-term use as some features may not function correctly. These configurations should only be used.

VDI clients and plugins compatibility matrix

note icon
VDI plugin and client combinations not specifically listed in the compatibility matrix below have not been tested and are not guaranteed to work correctly.
 
VDI client versionsRecommended VDI plugin versionCompatible VDI pluginsVDI plugins with limited support
6.6.106.6.10

6.6.10
6.5.10 -  6.5.13
6.4.10 -  6.4.15 

6.3.10 - 6.3.15
6.2.10 - 6.2.15
6.1.10 - 6.1.18
6.5.10 -  6.5.136.5.13

6.5.10 -  6.5.13
6.4.10 -  6.4.15
6.3.10 -  6.3.15

6.2.10 - 6.2.15
6.1.10 - 6.1.18
6.0.10 - 6.0.16
6.4.10 -  6.4.156.4.15

6.4.10 -  6.4.15
6.3.10 -  6.3.15
6.2.10 -  6.2.15

6.1.10 - 6.1.18
6.0.10 - 6.0.16
5.17.5 - 5.17.15
6.3.10 -  6.3.156.3.15

6.3.10 -  6.3.15
6.2.10 -  6.2.15
6.1.10 -  6.1.18

6.0.10 - 6.0.16
5.17.5 - 5.17.15
5.16.0 - 5.16.16
6.2.10 -  6.2.156.2.15

6.2.10 -  6.2.15
6.1.10 -  6.1.18
6.0.10 -  6.0.16

5.17.5 - 5.17.15
5.16.0 - 5.16.16
5.15.10 - 5.15.17

6.1.10 -  6.1.186.1.18

6.1.10 -  6.1.18
6.0.10 -  6.0.16
5.17.5 -  5.17.15

5.16.0 - 5.16.16
5.15.10 - 5.15.17

6.0.10 -  6.0.166.0.16

6.0.10 -  6.0.16
5.17.5 -  5.17.15
5.16.0 -  5.16.16

5.15.10 - 5.15.17

5.17.10 - 5.17.155.17.15

5.17.5 -  5.17.15
5.16.0 -  5.16.16
5.15.10 -  5.15.17

N/A
5.17.5 - 5.17.65.17.6

5.17.5
5.16.0 -  5.16.16
5.15.10 -  5.15.17

N/A
5.16.10 - 5.16.16 5.16.16 

5.16.0 -  5.16.16
5.15.10 -  5.15.17

N/A

 

note icon
As Extension Patch (EP) releases remain on the same release branch and generally include only additional bug fixes, fixes to compatibility issues with virtual environments, and security enhancements found in that branch, VDI Plugin Management will automatically update to the highest EP version for that same branch. This means the version specified by the AutoUpdatePluginVersion registry policy will be exceeded if an available EP is available for that branch, but updates will not exceed releases of that branch. For example, if admins choose 6.2.10, version 6.2.15 will be installed, as it is the latest version on that branch.