Error Importing Hyper-V VM (The Virtual Machine Is Using Processor-Specific-Features)

MISAdmin 381 Reputation points
2021-08-19T16:50:02.723+00:00

I am trying to move a Windows 10 VM from an older Windows 10 PC to a more recent one. I am not doing a Live migration. I exported the VM on the older box and copied the resultant folder to the newer PC. When I start the import, I get an error that says...

"The virtual machine [NAME] is using processor-specific-features not supported on physical computer [NAME]. To allow for migration of this virtual machine to physical computers with different processors, modify the virtual machine settings to limit the processor feature used by the virtual machine."

I have three saved states and this error is repeated for the other two states as well. It gives me an option to delete the saved states or cancel. I enabled the CPU compatibility option for the VM and then re-exported and imported but it doesn't help. Anyone know how to fix this?

System Center Virtual Machine Manager
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,706 questions

16 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. AlexZhu-MSFT 5,871 Reputation points Microsoft Vendor
    2021-08-24T07:20:46.817+00:00

    Hi,

    Could you try to run the following PowerShell cmdlets (with admin previllege) to see if it helps? 

    $vm_name = "virtual machine win10"
get-vm -name $vm_name | stop-vm
Set-VMProcessor $vm_name -CompatibilityForMigrationEnabled $true
$start-vm -name $vm_name

    Alex
    If the response is helpful, please click "Accept Answer" and upvote it.

  2. MISAdmin 381 Reputation points
    2021-08-24T13:24:53.603+00:00

    Hi. I don't think Compatibility Mode is the cause. Microsoft states that "Processor compatibility mode is not needed for virtual machines moves that involve a stop and restart of the virtual machines." See here...

    https://video2.skills-academy.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn859550(v=ws.11)

    0 comments
  3. AlexZhu-MSFT 5,871 Reputation points Microsoft Vendor
    2021-08-25T08:21:18.127+00:00

    Hi,

    Backing to the error message, to get it a little further, we may check the processor features betwween the (problematic) virtual machines and the new host. Some third-party tools can do this.
    "The virtual machine [NAME] is using processor-specific-features not supported on physical computer [NAME]"

    As for the Processor compatibility mode, it seems the article is right, however, someone solved the problem for the same error message. If possible, we may run it for testing purpose. Before runing this, we may use get-vmprocessor to get the current value so that we can revert it back.

    cpu features for virtual machine of old hyper-v host
    126292-hwinfo-vm.png

    cpu features for new hyper-v host
    (all the green items in the vm should exist in the new host and be green)
    126276-hwinfo-host.png

    get-vmprocessor
    126293-get-vmprocessor.png

    Alex
    If the response is helpful, please click "Accept Answer" and upvote it.

    0 comments
  4. MISAdmin 381 Reputation points
    2021-08-25T11:09:40.167+00:00

    Hi. What is that gui tool you are running? Perhaps I can try that.

    0 comments
  5. AlexZhu-MSFT 5,871 Reputation points Microsoft Vendor
    2021-08-26T01:04:15.683+00:00

    Hi,

    It's hwinfo, a free hardware detection tool (not from Microsoft). From the window title of the screenshots, we can see it.

    And this is the download link
    Note: this is not from Microsoft, just for your reference.

    Alex
    If the response is helpful, please click "Accept Answer" and upvote it.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.