Many users encounter challenges when performing backups of virtual machines (VMs) after migrating to a new Hyper-V host server. Specifically, issues with application-aware processing can arise, leading to backup failures and error messages. One common problem reported involves Error Code ‘32678’, often encountered after migrating Windows Server 2008 R2 VMs to a Windows Server 2016 Hyper-V host. This issue persists even after applying updates like KB3063109, which is intended to address some Hyper-V integration service problems.
The error often manifests when running this WMI query on the Hyper-V host server during the backup process. Users find that VMs migrated to the new host, particularly those restored as new VMs instead of exported/imported, are susceptible to this error. While exporting and importing VMs might circumvent the problem, this isn’t always practical for large or clustered environments.
A potential solution discussed in forums points to the need for KB3037623. This update is suggested to resolve issues related to Hyper-V backup integration components. However, users frequently report that KB3037623 is not offered through standard Windows Update on affected servers, despite systems being fully updated. This makes obtaining the necessary patch challenging. The vmbus.sys file version, even at 6.3.9600.18080, which is present on working exported/imported VMs, doesn’t seem to guarantee a resolution for migrated VMs experiencing this error.
Finding a reliable download source for KB3037623 for Windows Server 2008 R2 becomes crucial for resolving this backup problem. The official Microsoft support link often proves unhelpful in providing a direct download for this specific update. Therefore, system administrators facing Error Code ‘32678’ and application-aware backup failures on migrated Hyper-V VMs need to investigate alternative methods to acquire and install KB3037623 to potentially rectify the WMI query related issues on their Hyper-V host servers.
