New
#1
Annoyance with ViBoot Losing VHD's, Visible but not Usable in Hyper-V
It's common for ViBoot to lose a virtual machine.
I'm aware of the problem of using checkpoints with ViBoot; sometimes removing checkpoints will allow ViBoot to see the virtual machine again. This is not always the case. I have a virtual machine created using ViBoot that is only visible in Hyper-V, but the machine will not run using Hyper-V -- the machine starts but never boots. Even with checkpoints turned off, something is corrupting the image. The only solution is to delete the machine using hyper-v and starting over.
The problem is more of an annoyance, since I always have a current Macrium backup available to reload. Why is this happening?
- - - Updated - - -
I neglected to state that the base image contains several incremental updates. I will try viboot using only a base image (no incrementals) and see if this behaves better.