Error '0x20' ('The process cannot access the file because it is being used by another process.') after quick migration VM in Failover Cluster

Question

Hello!

After quick migration banch of VMs (Hyper-V Replica) some VMs generate error The error code was '0x20' ('The process cannot access the file because it is being used by another process.') on new node. VM show on new node in Failover Cluster Manager, but actully it's configuration stay on old node in Hyper-V Manager. After make quick migration to old node and make again migration to new node for that one VM - VM migrate works fine.

All updates for Windows Servers 2019 is installed. We are use VM configurations version 5 (Windows Server 2012R2) for due to compatibility issues. But this version of configurations is declared as supported.

Answer 1

The VMs in your situation appear to be operating on the source node. Try the following fix:

• On the source node, stop the VMs.
• Move the virtual machines (VMs) to the new node.
• On the destination node, start the virtual machines.

You can try the following if the VMs continue to have migration issues:

• Verify the folder and file permissions for the VM. Make that the user account for Hyper-V Manager has the proper permissions to access the files.
• On the source or destination nodes, turn off any antivirus or anti-malware software that may be running. Sometimes, this program can prevent Hyper-V migrations.
• On both the source and destination nodes, update the Hyper-V drivers.

Also, you can check this thread for reference - https://serverfault.com/questions/585368/how-can-i-release-a-locked-hyper-v-vhd-that-is-used-by-another-process

Please Note: Since the web sites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.