Proceed with the following phases for pre-upgrade verification, plugin activity validation, risk assessment, and post-upgrade remediation to safely complete the vCenter Server upgrade:
-
Pre-Upgrade Verification:
- Identify the plugins listed in the Stage 2 warning
- Log in to the source vCenter Client, navigate to Administration > Solutions > Client Plug-ins
- Note the Vendor and Version of each reported plugin

- Verify compatibility with the target version via vSphere Client Plug-In
Note: If 3rd-party plugin compatibility details are not available or if the plugin is not listed in the compatibility guide, contact the specific third-party vendor for support.
-
Check if the Plug-in is In-Use:
- Before taking any action, verify if the flagged extension is actively managing components within the environment. To confirm if a plugin is in-use, perform the following checks:
- Task Console Verification
- Navigate to Monitor > Tasks in the vSphere Client. Review recent tasks to determine if the flagged plugin ID is actively initiating operations (e.g., snapshot creations or storage syncs). Note: Below screenshot shows that the vLCM plugin is actively being used.

- Storage Provider Verification (For Storage Plugins):
- Navigate to vCenter Server > Configure > Storage Providers. If a provider matching the plugin vendor is listed with a status of "Online" and "Active," the plugin is actively managing storage arrays.

- MOB Heartbeat Verification:
- Access the Managed Object Browser (MOB) at https://<vCenter_FQDN_or_IP>/mob.
-
Navigate to Content > ExtensionManager.
-
Select the specific extension key flagged in the warning.
- Review the lastHeartbeatTime property. A recent timestamp indicates the third-party appliance is actively communicating with vCenter Server.
- Risk of proceeding: Based on the findings in Phase 2, evaluate if the plugin is required for ongoing operations and consider the associated risks
- If the plugin is NOT in-use (Legacy/Ghost registration): The warning can be safely bypassed. There is no risk to the environment.
-
If the plugin is in-use and required: Bypassing this warning and continuing the vCenter Server upgrade may result in the plugin failing to function in the target vCenter Server version.
Note: Proceeding with the upgrade while relying on an incompatible plugin can disrupt critical third-party integrations, leading to a loss of storage management visibility (vVols/VASA), failure of automated third-party backup jobs, or loss of network integration controls until the vendor provides a compatible update.
- Proceed with the upgrade: Once the risks have been evaluated and accounted for, this warning can be safely bypassed. Click Next on the installer screen to continue the upgrade process.
- Post-Upgrade validation and remediation
- Log in to the Target vCenter Server after the upgrade completes
- Navigate to Administration > Solutions > Client Plug-ins and check the plugin status
- If enabled: No action required
- Failed/Incompatible: The plugin must be updated or re-registered. To register plugin refer Reregister Plug-In Solution in vCenter Server After Upgrade or Migration