| Issue ID | Description | Impact | | :--- | :--- | :--- | | 1822453 | Converter failed to clone Windows source with EFI system partition if secure boot was enabled. | High | | 1764891 | Hot cloning a Linux VM with XFS filesystem on a raw device caused kernel panic at destination. | Critical | | 1700554 | Converter Worker process would leak memory during long-running conversions of servers with >8 NICs. | Medium | | 1689237 | Timeout errors when using VSS on Windows Server 2012 R2 with SQL Server installed. | High | | 1654402 | The "Reconfigure source VM after cloning" option did not remove the source's network configuration. | Low | | 1628810 | Converter CLI failed to authenticate against vCenter 6.5 with external PSC (Platform Services Controller). | High |
The release, launched on December 14, 2017 , introduced critical updates to support modern data center environments, specifically targeting compatibility with vSphere 6.5 Update 1 and newer guest operating systems. This version serves as a key utility for automating the conversion of physical machines (P2V) and virtual machines (V2V) into VMware virtual machines. What’s New in Release 6.2 vmware vcenter converter standalone 6.2 release notes
to see if you should be using a more recent version like 6.6 or 9.0 instead. or troubleshooting a specific conversion error VMware vCenter Converter Standalone 6.2 Release | Issue ID | Description | Impact |
Before deploying Converter 6.2, understanding constraints is vital. | Medium | | 1689237 | Timeout errors
Expanded to include Windows Server 2016 and Ubuntu 16.04 LTS.