{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint/", "slug": "dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint", "url": "https://update.dsesecurity.com/updates/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint/" }, "title": "Preserve the current VM state before applying an older checkpoint", "summary": "What choice is made when applying an earlier Hyper-V checkpoint?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-08T18:13:17+00:00", "modified_at": "2026-09-08T18:29:34+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 2, "word_count": 230, "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.", "primary_source": { "name": "Using checkpoints", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/checkpoints", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

Microsoft Learn: Using checkpoints. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft 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.\nApplicability\nIdentify 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.\nDSE recommendation\nHave 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.\nVerification\nVerify 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.\nOfficial references\nMicrosoft Learn: Using checkpoints. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft 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).\n\n## Applicability\n\nIdentify 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.\n\n## DSE recommendation\n\nHave 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.\n\n## Verification\n\nVerify 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.\n\n## Official references\n\n[Microsoft Learn: Using checkpoints](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/checkpoints). Source reviewed September 8, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint/", "url": "https://update.dsesecurity.com/updates/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Preserve the current VM state before applying an older checkpoint", "item": "https://update.dsesecurity.com/updates/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint/", "url": "https://update.dsesecurity.com/updates/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint/", "headline": "Preserve the current VM state before applying an older checkpoint", "description": "What choice is made when applying an earlier Hyper-V checkpoint?", "abstract": "What choice is made when applying an earlier Hyper-V checkpoint?", "articleBody": "Source facts\nMicrosoft 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.\nApplicability\nIdentify 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.\nDSE recommendation\nHave 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.\nVerification\nVerify 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.\nOfficial references\nMicrosoft Learn: Using checkpoints. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:13:17+00:00", "dateModified": "2026-09-08T18:29:34+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260908-234-preserve-the-current-vm-state-before-applying-an-older-checkpoint/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Preserve the current VM state before applying an older checkpoint" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 230, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Using checkpoints", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/checkpoints" } } ] } }