Hello there,
Whether these VMs were modified on the Hyper-V console before the issue occurs? If they are modified on the Hyper-V console, the result may not be passed to the Cluster console which causes the issue.
- When you begin to delete the VM, do you use the cluster GUI to remove the VM, then remove the VM in Hyper-V?
If the VM files haven't been deleted completely, you may check if restoring the VM and then removing the VM from cluster GUI could work.
- Try to restart the Cluster MMC or restart the Server and see if that helps.
- If the above method couldn't work, you may also try Process Monitor, we may capture the detailed process when we delete the VM.
Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry, and process/thread activity. You can get the tool from here https://docs.microsoft.com/en-us/sysinternals/downloads/procmon
Similar discussion here https://social.technet.microsoft.com/Forums/en-US/faaf2bbf-b623-45c8-b82c-1b9115e6afb8/the-file-cannot-be-opened-because-it-is-in-the-process-of-being-deleted?forum=winserverClustering
Hope this resolves your Query !!
--If the reply is helpful, please Upvote and Accept it as an answer–