Windows 10: HYPER-V Non persistent Disks ???

Hi folks
particularly @Kari

With HYPER V is it possible to create a training environment so that people can do exercises / tutorials on a VM but at the end of the session the Virtual HDD's are restored to the initial state.

With VMWARE it's easy enough but I'm not sure how HYPER V works. This way is better than just restoring VM's every time. Note this is different from SNAPSHOTS.

Cheers
jimbo

:)

 

Recreate Windows 10 Recovery partition

When Windows 10 is installed as a hyper-v virtual machine it creates a 350Mb System Reserved partition at the beginning of the disk and a 450Mb Recovery partition at the end of the disk.

Problem is this 450Mb Recovery partition at the end of the disk then prevents hyper-v edit disk from being able to shrink the dynamic disk!

Solution seems to be either move the 'Recover Partition' or delete and recreate it, question is how?

 

Hyper V

I have read all the answers about disabling Hyper V in Windows 8.1. It does not work. I repeat, unchecking Hyper V in the change Windows Settings does not work. I ran Ubuntu and Fedora in the Virtual Machine. Now I have VM Ware. It
is not compatible with Hyper V. How do I disable the virtual machines and the virtual disk created by Hyper V? I am using
Windows 10.

 

Dead easy - just create a checkpoint at start of session, and wind back to that at end of session.

Also, you can export the VM for sharing so it can be reinstated quickly as an added precaution.

 

Exactly.

Create the VM. Before booting it first time open its Settings and disable automatic checkpoints (#1), check that checkpoints are enabled (#2) and that checkpoint type is set as Standard Checkpoints (#3).





Boot VM, set it up as it should be at start before user starts training (install required software, set resolution and other settings and so on). Shut down VM. Create checkpoint:





Start VM, change it as you wish or as training requires. Shut down when done, apply checkpoint to restore saved state:









That's it. Next time the VM is started, it restores the saved state as in selected checkpoint.

Notice that by default, if you have applied checkpoints but not started virtual machines after applying them, next time Windows will be restarted the virtual machines will start automatically. To avoid automatic start of virtual machines with applied checkpoints after Windows boot, set Automatic Start Action to Nothing. Default is Automatically start if it was running when the service stopped, which not only starts virtual machines which were running when service was stopped (Windows shut down / restarted), but also automatically starts those virtual machines which had a checkpoint applied before service was stopped.

 

Hi guys

Thanks

Nice clear explanations too -- thanks again

Cheers
jimbo