{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-199-keep-vm-configuration-upgrades-separate-from-hyper-v-host-upgrades/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-199-keep-vm-configuration-upgrades-separate-from-hyper-v-host-upgrades/", "slug": "dse-20260908-199-keep-vm-configuration-upgrades-separate-from-hyper-v-host-upgrades", "url": "https://update.dsesecurity.com/updates/dse-20260908-199-keep-vm-configuration-upgrades-separate-from-hyper-v-host-upgrades/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-199-keep-vm-configuration-upgrades-separate-from-hyper-v-host-upgrades.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-199-keep-vm-configuration-upgrades-separate-from-hyper-v-host-upgrades/" }, "title": "Keep VM configuration upgrades separate from Hyper-V host upgrades", "summary": "When should a Hyper-V VM configuration version be advanced?", "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:52+00:00", "modified_at": "2026-09-08T18:26:32+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 2, "word_count": 236, "potentially_affected": "Administrators upgrading Hyper-V hosts and virtual-machine configuration versions.", "dse_recommendation": "For each VM, write down the feature that requires an upgrade and the older-host return path that may still be needed.", "primary_source": { "name": "Upgrade virtual machine version in Hyper-V on Windows or Windows Server", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Upgrade-virtual-machine-version-in-Hyper-V-on-Windows-or-Windows-Server", "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 explains that moving or importing a VM onto a newer Hyper-V host does not automatically upgrade its configuration version. Keeping the older version preserves the documented ability to move the VM back to an older host, while some newer features require an explicit upgrade. The source provides Get-VMHostSupportedVersion to inspect supported versions. An upgraded VM configuration version cannot be downgraded. Its upgrade procedure starts by shutting down the virtual machine. Microsoft Learn.

\n

Applicability

\n

Inventory the current VM configuration version and every host that might need to run it, including recovery destinations. Check those hosts against the source support table. Make the configuration-version decision separately from completing the host operating-system upgrade.

\n

DSE recommendation

\n

For each VM, write down the feature that requires an upgrade and the older-host return path that may still be needed. Have the virtualization and workload owners agree when that fallback requirement ends. Schedule the required shutdown and preserve a recoverable pre-change record. Do not advance every VM automatically just because a newer host offers the option.

\n

Verification

\n

After the approved upgrade, verify the reported configuration version and the specific feature that motivated it. Validate startup and the representative application transaction. Compare all intended placement destinations with the accepted compatibility plan, and document any destination that is no longer part of that plan.

\n

Official references

\n

Microsoft Learn: Upgrade virtual machine version in Hyper-V on Windows or Windows Server. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft explains that moving or importing a VM onto a newer Hyper-V host does not automatically upgrade its configuration version. Keeping the older version preserves the documented ability to move the VM back to an older host, while some newer features require an explicit upgrade. The source provides Get-VMHostSupportedVersion to inspect supported versions. An upgraded VM configuration version cannot be downgraded. Its upgrade procedure starts by shutting down the virtual machine. Microsoft Learn.\nApplicability\nInventory the current VM configuration version and every host that might need to run it, including recovery destinations. Check those hosts against the source support table. Make the configuration-version decision separately from completing the host operating-system upgrade.\nDSE recommendation\nFor each VM, write down the feature that requires an upgrade and the older-host return path that may still be needed. Have the virtualization and workload owners agree when that fallback requirement ends. Schedule the required shutdown and preserve a recoverable pre-change record. Do not advance every VM automatically just because a newer host offers the option.\nVerification\nAfter the approved upgrade, verify the reported configuration version and the specific feature that motivated it. Validate startup and the representative application transaction. Compare all intended placement destinations with the accepted compatibility plan, and document any destination that is no longer part of that plan.\nOfficial references\nMicrosoft Learn: Upgrade virtual machine version in Hyper-V on Windows or Windows Server. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft explains that moving or importing a VM onto a newer Hyper-V host does not automatically upgrade its configuration version. Keeping the older version preserves the documented ability to move the VM back to an older host, while some newer features require an explicit upgrade. The source provides Get-VMHostSupportedVersion to inspect supported versions. An upgraded VM configuration version cannot be downgraded. Its upgrade procedure starts by shutting down the virtual machine. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Upgrade-virtual-machine-version-in-Hyper-V-on-Windows-or-Windows-Server).\n\n## Applicability\n\nInventory the current VM configuration version and every host that might need to run it, including recovery destinations. Check those hosts against the source support table. Make the configuration-version decision separately from completing the host operating-system upgrade.\n\n## DSE recommendation\n\nFor each VM, write down the feature that requires an upgrade and the older-host return path that may still be needed. Have the virtualization and workload owners agree when that fallback requirement ends. Schedule the required shutdown and preserve a recoverable pre-change record. Do not advance every VM automatically just because a newer host offers the option.\n\n## Verification\n\nAfter the approved upgrade, verify the reported configuration version and the specific feature that motivated it. Validate startup and the representative application transaction. Compare all intended placement destinations with the accepted compatibility plan, and document any destination that is no longer part of that plan.\n\n## Official references\n\n[Microsoft Learn: Upgrade virtual machine version in Hyper-V on Windows or Windows Server](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Upgrade-virtual-machine-version-in-Hyper-V-on-Windows-or-Windows-Server). 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-199-keep-vm-configuration-upgrades-separate-from-hyper-v-host-upgrades/", "url": "https://update.dsesecurity.com/updates/dse-20260908-199-keep-vm-configuration-upgrades-separate-from-hyper-v-host-upgrades/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-199-keep-vm-configuration-upgrades-separate-from-hyper-v-host-upgrades/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Keep VM configuration upgrades separate from Hyper-V host upgrades", "item": "https://update.dsesecurity.com/updates/dse-20260908-199-keep-vm-configuration-upgrades-separate-from-hyper-v-host-upgrades/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-199-keep-vm-configuration-upgrades-separate-from-hyper-v-host-upgrades/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-199-keep-vm-configuration-upgrades-separate-from-hyper-v-host-upgrades/", "url": "https://update.dsesecurity.com/updates/dse-20260908-199-keep-vm-configuration-upgrades-separate-from-hyper-v-host-upgrades/", "headline": "Keep VM configuration upgrades separate from Hyper-V host upgrades", "description": "When should a Hyper-V VM configuration version be advanced?", "abstract": "When should a Hyper-V VM configuration version be advanced?", "articleBody": "Source facts\nMicrosoft explains that moving or importing a VM onto a newer Hyper-V host does not automatically upgrade its configuration version. Keeping the older version preserves the documented ability to move the VM back to an older host, while some newer features require an explicit upgrade. The source provides Get-VMHostSupportedVersion to inspect supported versions. An upgraded VM configuration version cannot be downgraded. Its upgrade procedure starts by shutting down the virtual machine. Microsoft Learn.\nApplicability\nInventory the current VM configuration version and every host that might need to run it, including recovery destinations. Check those hosts against the source support table. Make the configuration-version decision separately from completing the host operating-system upgrade.\nDSE recommendation\nFor each VM, write down the feature that requires an upgrade and the older-host return path that may still be needed. Have the virtualization and workload owners agree when that fallback requirement ends. Schedule the required shutdown and preserve a recoverable pre-change record. Do not advance every VM automatically just because a newer host offers the option.\nVerification\nAfter the approved upgrade, verify the reported configuration version and the specific feature that motivated it. Validate startup and the representative application transaction. Compare all intended placement destinations with the accepted compatibility plan, and document any destination that is no longer part of that plan.\nOfficial references\nMicrosoft Learn: Upgrade virtual machine version in Hyper-V on Windows or Windows Server. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:13:52+00:00", "dateModified": "2026-09-08T18:26:32+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-199-keep-vm-configuration-upgrades-separate-from-hyper-v-host-upgrades/" }, "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-199-keep-vm-configuration-upgrades-separate-from-hyper-v-host-upgrades/#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": "Keep VM configuration upgrades separate from Hyper-V host upgrades" }, "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": 236, "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": "Upgrade virtual machine version in Hyper-V on Windows or Windows Server", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Upgrade-virtual-machine-version-in-Hyper-V-on-Windows-or-Windows-Server" } } ] } }