Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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

View products that this article applies to.


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.

↑ Back to the top


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.

↑ Back to the top


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

↑ Back to the top

Keywords: registry key changes not saved in hyper-v vm, kb, kbsurveynew

↑ Back to the top

Article Info
Article ID : 4099228
Revision : 10
Created on : 4/4/2018
Published on : 4/4/2018
Exists online : False
Views : 279