Windows 10: Can't show Checkpoint in Hyper-V manager

I have created Checkpoint, but I can't find it in Hyper-V Manager.

:)

 

Create and Use Hyper-V Checkpoints in Windows 10  


Hi Kari,

actually I do this similarly. Just, I like to keep the date/time in name as it is not otherwise shown in Hyper-V Manager.

So I always create my checkpoints with generated name and then just append some description in Hyper-V Manager.





Like here in Ubuntu, where I've kept track of nearly every step installing stuff on it... sorry just my paranoia *Wink as I'm a somewhat dummy in Linux.

Gerhard

 

Create and Use Hyper-V Checkpoints in Windows 10  

PowerShell really is a nice tool to be used with Hyper-V.

I see you had used default checkpoint names. I like to rename mine to better remember to what point any checkpoint takes me.

Earlier today I recorded video to be sent to Macrium support. I've had contact with them because an issue with Macrium Reflect CBT and Image Guardian features; they simply break OneDrive Files on Demand feature (OD FOD) in Insider builds 17035 and 17040. To demonstrate it I clean installed W10 on a VM, then reproduced the issue creating checkpoint after each step:




I like doing it so, making a relatively short video now by applying checkpoints one after another, capturing those few seconds from that step I want to show, then applying next checkpoint and so on.

Renaming checkpoints with descriptive names tells me exactly which checkpoint I need to / want to apply.

 

Where is the Hyper V Manager, How to I start it ?

I am trying to setup an XP virtual Machine on Windows 10 Pro.

I followed the steps in Neil Peterson article of 5/9/2016.

System Requirements - done - ok

Install Hyper-V - done - ok

Create a Virtual Switch - skip

Create a Virtual Machine

Create a Virtual Machine with Hyper-V Manager

These steps walk through how to manually create a virtual machine and deploy an operating system to this virtual machine.

• 
  In Hyper-V Manager, click Action > New >
  Virtual Machine to bring up the New
  

Uhhhhhhhhh - this step obviously implies one knows

1) Where the Hyper-V Manager is

2) How to start the Hyper-V Manager

Isn't that odd ?