# Plan processor compatibility before moving a VM across CPU generations

> Which VM processor setting must be reviewed before migration between different hosts?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:13:14+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

Which VM processor setting must be reviewed before migration between different hosts?

## Potentially affected

Administrators configuring Hyper-V VM processor compatibility.

## DSE recommendation

Document the hosts the VM must be able to use and the application features that may depend on exposed CPU capabilities.

## Article

## Source facts

Microsoft describes processor compatibility mode as limiting the processor features exposed to a VM so it can move between hosts with differing capabilities. The VM must be powered off before enabling or disabling the setting. Dynamic processor compatibility cannot be configured in Hyper-V Manager; the documented alternatives are PowerShell or Windows Admin Center. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/configure-processor-compatibility-mode).

## Applicability

Inventory the intended source, destination, and recovery hosts and their supported capabilities. Check whether the cluster and operating-system versions support the dynamic option described in the source. Keep the compatibility decision separate from allocating more virtual processors to a workload.

## DSE recommendation

Document the hosts the VM must be able to use and the application features that may depend on exposed CPU capabilities. Ask the workload owner to approve the planned powered-off change window. Select the management tool that supports the intended mode and preserve the initial setting. Define a representative migration and application test before altering a production VM.

## Verification

Confirm the effective compatibility mode after the approved change, then start the VM and validate the application. Exercise the intended host-to-host move and record both placement and workload results. Compare the result with every host in the accepted placement set. Resolve an unsupported destination or changed application behavior before extending the setting to other VMs.

## Official references

[Microsoft Learn: Configure processor compatibility in Hyper-V virtual machines](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/configure-processor-compatibility-mode). Source reviewed September 8, 2026.

## Primary reference

- Name: Configure processor compatibility in Hyper-V virtual machines
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/configure-processor-compatibility-mode
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Plan processor compatibility before moving a VM across CPU generations,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations/
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.