[Solved] vCenter Converter Standalone 6.2 Installation Failed or Service cannot Start

VMware vCenter Converter Standalone 6.2 installation failed with error “Could not start service” or related service (vCenter Converter Agent, vCenter Converter Server or vCenter Converter Worker service) cannot start on Windows Server 2008 R2 or later. Additionally, Event ID 7009 can be get in Windows event viewer with content A timeout was reached (30000 milliseconds) while waiting for the VMware vCenter Converter Standalone Worker service to connect. This issue caused by Service Control Manager generates an event if a service does not respond within the defined timeout period (the default timeout period is 30000 milliseconds). Follow below steps to change the service timeout period.

Resolution

Step 1: Click Start > Run, type regedit and click OK to open Registry Editor.

Step 2: Go to below registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

Step 3: Locate the ServicesPipeTimeout entry, right-click it and select Modify. Note: If ServicesPipeTimeout entry does not exist, you must create it by selecting Edit > New > DWORD Value then typing ServicesPipeTimeout and clicking Enter.

Step 4: Click Decimal, enter the new timeout value in milliseconds to a larger one and click OK.

Step 5: Restart computer.

Step 6: Manual start related service (vCenter Converter Agent, vCenter Converter Server or vCenter Converter Worker service) in Windows Service Manager. If the service is still failed to start with Windows event 7009, increase ServicesPipeTimeout value.

Source

VMware Knowledge Base: vCenter Converter 6.2 failed to install on Windows Server 2008 R2 or later (64993)