Problem Description
VMware virtual machine backups fail during the snapshot phase with the following error code: VMWARE_GOVMOMI7 | 'VssSyncStart' operation failed: IDispatch error #8451 (0x80042303)
When attempting to isolate the issue by taking a manual quiesced snapshot directly from the vCenter UI, the action fails with the exact same error: Error: 'VssSyncStart' operation failed: IDispatch error #8451 (0x80042303)
Traceback
The following errors can be found within the EnterpriseWorkloadsFL.<ID>.log file:
level=error ts=2026-06-18T13:58:09.885371638Z filename=virtual_machine.go:311 method=createVMSnapshot message="VM snapshot creation failed." Error="An error occurred while quiescing the virtual machine. See the virtual machine's event log for details."
Cause
This issue occurs when a stale registry key for the VMware Snapshot Provider is orphaned inside the Windows Guest OS registry database.
The following key should only exist temporarily while a quiesced snapshot is actively being created or consolidated by the hypervisor: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{564d7761-7265-2056-5353-2050726f7669}
If a previous process leaves this key behind, subsequent Microsoft VSS operations conflict with the phantom provider entry, causing the VssSyncStart routine to fail.
Resolution
Follow the steps below inside the affected Windows guest operating system to remove the stale registry key:
Step 1: Verify the Stale Provider
Log in to the affected Windows Guest OS as an Administrator.
Open a Command Prompt window and execute the following command:
DOS
vssadmin list providers
Check the output to see if the VMware Snapshot Provider with the following ID is listed outside of an active backup window:
Provider ID: {564d7761-7265-2056-5353-2050726f7669}
Step 2: Remove the Stale Registry Entry
⚠️ WARNING: Incorrect use of the Windows Registry Editor can cause serious system-wide problems. Ensure you carefully follow the backup steps listed below before modifying any keys.
Press
Win + R, typeregedit, and press Enter to open the Registry Editor.Navigate to the following path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\ProvidersRight-click on the
Providersfolder and select Export. Save this file to a secure location as a backup.Expand the
Providersfolder, locate the specific sub-key named exactly:{564d7761-7265-2056-5353-2050726f7669}Right-click the
{564d7761-7265-2056-5353-2050726f7669}key and click Delete.Exit the Registry Editor.
Step 3: Apply and Verify Changes
Reboot the virtual machine to clear out any remaining cached VSS states.
Once the VM boots back up, open vSphere and manually trigger a Quiesced Snapshot on the VM to verify it completes without errors.
Run the Druva backup job again to ensure successful completion.