Hello,
I was experimenting with the Hyper-V "Planned Failover" functionality, from a primary VM to its replica on another machine. One of the tests I did was doing a Planned failover, canceling the planned failover, and then removing replication altogether. I'm not 100% sure if this is the cause of what I'm seeing, but it seems the most likely.
What I'm seeing is these mysterious F and G drives, which I AM 100% sure are not actual physical disks:
The size of the G: drive is EXACTLY the size of the virtual machine hard disk that I was testing in the Planned Failover testing I mentioned prior.
The virtual machine in question is safely running on another machine, and I have deleted the virtual machine replica from this machine (Using the Delete Virtual Machine functionality in the main Hyper-V management screen), but the virtual hard disk still is hanging around - I can't delete it. It's in the default Hyper-V replicas folder, and this is what I get when I try to delete it (it's a virtual dynamically expanding disk that has 35 GB of content, but has a set max size of 127 GB):
looking in the Server File and Storage Services section, which I'm not terribly familiar with, I see this:
Same picture, but cropped for better resolution in browser
How do I safely delete the F and G volumes, and delete the currently undeletable .VHDX file? And does anybody know what causes this nonsense to happen?