Mike Howard
asked on
Hyper-V cannot create a new VM claiming a checkpoint is missing, even when no checkpoint has ever been made.
I had created a VM, then a checkpoint, but somehow it was deleted. It was only a little test VM I had set up, no big deal to lose, so I deleted the VM from Hyper-V Manager.
Now, whenever I try to create a VM--*any* VM--it fails with a popup error:
It doesn't matter what the VM name is, it always claims that the checkpoint %vmname%.vhdx is missing.
Example:
I try to create a VM in directory d:\vm\vms\ called VM-01. I tell it to place the disk in d:\vm\vms\VM-01\vhd\. I hit Finish. It acts like it is creating everything, then I get the popup above. The directories are created (e.g. d:\vm\vms\VM-01\Virtual MachinesError log reports:
'VM-01' is missing a checkpoint. The disk paths missing used to be located at: D:\vm\vms\VM-01\vhd\VM-01.
This will happen regardless of what I name the VM.
Security on the directory:
SYSTEM: FULL CONTROL
%MyDomainUserAcct%: FULL CONTROL
%LocalMachine%\Administrat
I've removed/reinstalled Hyper-V, done a system restore to before the problem started etc. Services are running and I am an admin on the machine. I still choose to run Hyper-V Manager as admin and get the same results.
To make matters more confusing: If I choose the Quick Create option it works just fine. If I create a custom machine and place it in the same directory (%userprofile%\Documents\V
Also, I am not able to add NT Virtual Machine\Virtual Machines to the security of the custom VM directory I've created on D:. Error is that the group or principal doesn't exist.
Any ideas are appreciated.
Now, whenever I try to create a VM--*any* VM--it fails with a popup error:
It doesn't matter what the VM name is, it always claims that the checkpoint %vmname%.vhdx is missing.
Example:
I try to create a VM in directory d:\vm\vms\ called VM-01. I tell it to place the disk in d:\vm\vms\VM-01\vhd\. I hit Finish. It acts like it is creating everything, then I get the popup above. The directories are created (e.g. d:\vm\vms\VM-01\Virtual MachinesError log reports:
'VM-01' is missing a checkpoint. The disk paths missing used to be located at: D:\vm\vms\VM-01\vhd\VM-01.
This will happen regardless of what I name the VM.
Security on the directory:
SYSTEM: FULL CONTROL
%MyDomainUserAcct%: FULL CONTROL
%LocalMachine%\Administrat
I've removed/reinstalled Hyper-V, done a system restore to before the problem started etc. Services are running and I am an admin on the machine. I still choose to run Hyper-V Manager as admin and get the same results.
To make matters more confusing: If I choose the Quick Create option it works just fine. If I create a custom machine and place it in the same directory (%userprofile%\Documents\V
Also, I am not able to add NT Virtual Machine\Virtual Machines to the security of the custom VM directory I've created on D:. Error is that the group or principal doesn't exist.
Any ideas are appreciated.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok, I was able to create a VM with no disk in the custom location. Then I was separately able to create a .vhdx in the custom location. I could then attach it to the VM and Jack's a doughnut! it works.
I hate unsolved mysteries like this, but I can handle the workaround. Thanks for the suggestion!
I hate unsolved mysteries like this, but I can handle the workaround. Thanks for the suggestion!
Glad to help. :)
ASKER