This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 57.00000000000001%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
For unknown reasons,
two virtual machines in a saved state appear in Hyper-V and cannot be deleted. How to delete it?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 39%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
Just incase someone is looking for an answer now that it's 2023 It took me forever to figure out what to do. I had no other VM'S but one that was in saved-critical state that I could not delete and I also couldn't create new vm's either. So, I went to the drive where I save Hyper-V VM'S and I deleted the folder called Hyper-V and then created a new folder with the same name. By doing that I was able to create new VM'S and save them in the new folder. I made sure even though when I created the new vm it atomically was going to save it to that location, I clicked on browse and I clicked on the new folder I created to save it there. Because of creating that new folder I was now able to click on that stuck VM to turn it blue and then to the right was able to finally click delete that VM. Hope this helps.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 91%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKP%3C/text%3E%3C/svg%3E)
Thanks a lot, DI. That also helped me. Simple and effective!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 99%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGS%3C/text%3E%3C/svg%3E)
Just delete content from this directory and restart Hyper-v management service - C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines Cache
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 42%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Thanks; this was helpful. I had to first stop the Hyper-V Virtual Machine Management service, and then I was able to delete the vmcx file in the Virtual Machines Cache folder.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 19%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPG%3C/text%3E%3C/svg%3E)
Worked for me, i need to stop the service first to clear it.
I just had this problem. Turns out the "cannot connect to virtual machine configuration storage" error probably just means it can't find the virtual machine file(s). In my case the external SSD that I have all my VMs stored on had its drive letter changed somehow, and I didn't notice.
Once I changed the drive letter back to what it was before, the Virtual Machines all were fixed in the list instantly.
To see where the disk was before, with one of the problematic VMs selected in the Hyper-V window, on the right side under the "Actions" pane I hit 'Edit Disk', then in the 'Locate Disk' section it showed where it was expecting it to be, which made me realize the letter was wrong.
Yes you could delete the cache folder like others have mentioned but be warned that will simply remove all the entries for your virtual machines, so you'd probably have to re-add them manually by selecting their disks and stuff - so make sure you can locate those files yourself in the first place.
I cant read the printscreen, but make sure the VM is shutdown and that all snapsnots are gone.
I could try shutting down the VM and see if those saved states get rid of it. I just restarted the computer before and didn't try to shut down the VM. (At present, the computer is controlled remotely, and the router in the virtual machine is a router, so I have to think about how to operate it)
Hello
Thank you for your question and reaching out. I can understand you are having issues related to Delete VMs which are in Saved State.
Please follow below steps to resolve the issue.
Change the SAVE auto-off mode from saved state to shutdown or to power off - that should clear that state file.
Then Open up the Hyper-V Manager.
Right-click on the virtual machine that is having the issue to open up the drop-down menu.
From there, click on the Delete Saved State option.
Once the saved state has been deleted, try starting the VM again.
If you face an error like “Operation cannot be performed while the object is in use“, restart the physical host and you should be good to go.
--If the reply is helpful, please Upvote and Accept as answer--