# Preserve the current VM state before applying an older checkpoint

> What choice is made when applying an earlier Hyper-V checkpoint?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:13:17+00:00
- Modified: 2026-09-08T18:29:34+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

What choice is made when applying an earlier Hyper-V checkpoint?

## Potentially affected

Administrators applying Hyper-V virtual-machine checkpoints during an approved recovery or test.

## DSE recommendation

Have the owner decide whether the present state must be preserved before the older checkpoint is applied.

## Article

## Source facts

Microsoft describes checkpoints as saved VM states that can be used to return to an earlier point after a configuration change. Hyper-V Manager offers a choice to create a checkpoint of the current VM before applying the selected older checkpoint. The alternative Apply choice applies only the selected checkpoint, and the source warns that this action cannot be undone. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/checkpoints).

## Applicability

Identify the exact VM, the checkpoint time, and the data-state change the application owner intends. Review the configured checkpoint type and workload requirements before proceeding. Keep returning to an earlier state separate from confirming that the earlier application data is acceptable.

## DSE recommendation

Have the owner decide whether the present state must be preserved before the older checkpoint is applied. Record that decision alongside the selected checkpoint name and the reason it represents the desired point. Use identifiable checkpoint names and a representative pilot when designing the procedure. Agree on how newly created or modified application data will be assessed after the return.

## Verification

Verify the selected state through the VM configuration and a workload-specific data check. Confirm that the current-state checkpoint exists when that option was required. Record the actual applied checkpoint and any unexpected data difference. Do not close the recovery solely because the VM starts; obtain the application owner’s acceptance of the restored state.

## Official references

[Microsoft Learn: Using checkpoints](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/checkpoints). Source reviewed September 8, 2026.

## Primary reference

- Name: Using checkpoints
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/checkpoints
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Preserve the current VM state before applying an older checkpoint,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.