Hyper V causing corrupted drive

I have a Server 2012 R2 machine with Hyper-V running on it. Have 2 virtual machines and had no issues with it. I recently ran a windows update on it and since then have been having issues.
If I shut down the PC and swap out the boot drive with a drive that has Windows 10 on it and reboot I get a message saying a drive is corrupt. Checking the partitions where the VM's and VM drives are they are usually corrupt and beyond use.

I tried a demo of Server 2016 and it does exactly the same thing. Previously this was working fine and I use it to do computer labs learning things like Exchange server and the likes.

I have even shut the VM's down and then powered down but the directory or files still end up corrupted.

Has anyone else seen this issue? Maybe MS are no longer shutting things down cleanly and expect to tidy things up when the machine reboots?

Hi there

I believe Windows 12 server allows a different file format than standard NTFS / FAT32 -- so check whether the disks allocated to your HYPER-V was formatted in a "W10 readable format".

Another possible solution --> re-boot server -- export the VM's to another HDD formatted with NTFS then re-boot W0 and import the VM's.

Cheers
jimbo

jimbo45 said:

Hi there

I believe Windows 12 server allows a different file format than standard NTFS / FAT32 -- so check whether the disks allocated to your HYPER-V was formatted in a "W10 readable format".

Another possible solution --> re-boot server -- export the VM's to another HDD formatted with NTFS then re-boot W0 and import the VM's.

Cheers
jimbo

The drive was formatted under Windows 10 as NTFS and is readable at the root directory. Just the VM directory shows as corrupted and can not access them. Same with the VHDx's. They are either gone or 0 size. So cant export them anyway. I did think it might be permissions thing but doesn't appear to be. I think it is something the Server 2012 is doing and then Windows 10 tries to fix it but kills all the files. The VM's have been set to save on machine shut down and the shutdown seems really fast compared to what it used to take.
Maybe it is a fast shutdown thing? I might check on that tomorrow and turn it off if it is on in the power settings.

Did some more investigation today. Started with empty folders and no VM's. Added a Server 2016 demo VM and took it through to it was able to be run and latest updated done on it. I then shut down the VM. Once that was done I shut down the Hyper V service to fully disconnect it. Checked and all folders were correct. VM and VHDx were in correct place.

Made a backup copy of each into a separate drive.

Shut down the PC and rebooted into Windows 10. Checked the VM folder and appears intact. Checked the VHDx folder and blank. Drive was gone or at least no visible. The drive usage appeared to indicate it was there but nothing. Ran a disk check over it and it said there were errors. Said it would fix them and after that I could not open the drive at all and had to reformat it.

I am thinking it is a permissions thing but I can see the copies I made fine. Copied the VHDx back to where it should be and when I get a bit more time will see it the VM still works.

Did a few more tests today and something strange is going on. Added another VM making it two and updated the files on it. The server wanted an update as well so I updated that. Shut both VM's down and then shut the Hyper V service down. Checking the drives folder they were okay and the VM folder appeared okay as well. However running a checkdisk on the VM drive resulted in errors again and it required fixing. The fix was okay and the files appear okay.

Looks like something is not shutting down properly and leaving files open which corrupt the disk and need fixing and it must by the Hypervisor but I can't see why or how to fix it. It was running fine originally and now after an update it is doing this.

Very frustrating. Only way around it is to copy everything to another folder so there is a back up if it gets corrupted while shutting down. Defeats the purpose really. Might try a completely separate drive and see what that does.

Did you discover a solution? I believe the same thing is happening to me. It has to do with connected standby. I havent been able to fix my drive without reinstalling windows.

Kromaticorb said:

Did you discover a solution? I believe the same thing is happening to me. It has to do with connected standby. I havent been able to fix my drive without reinstalling windows.

Welcome to TenForums. I'm afraid the OP is not able to respond as their account has been closed.

You would do better to start a new thread of your own, with details of the symptoms you are experiencing.