Registry changes lost after restoring a Hyper-V VM to a production checkpoint in Windows Server 2016

Applies to: Windows Server 2016


Assume that you make registry changes in a virtual machine (VM) that is running on a Windows Server 2016-based computer. Then, you immediately create a production checkpoint. When you restore the VM to the production checkpoint and start the VM, you may find that the latest registry change is not restored.


This issue occurs because the VSS registry writer in the virtual machine is disabled when you are creating a checkpoint. This behavior occurs to prevent a potential performance issue. Therefore, the latest registry change may not be flushed to the disk.


This behavior occurs by design to optimize the performance of checkpoint creation.