Hi Alex. Is that tool run on the Hosts? The VM in question is an image. I don't want to run software on images. They always leave remnants that get propagated to every machine the image is used on.
Error Importing Hyper-V VM (The Virtual Machine Is Using Processor-Specific-Features)
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
Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V
17 answers
Sort by: Most helpful
-
-
MISAdmin 386 Reputation points
2021-08-30T13:10:28.563+00:00 Hi Alex. So the difference is the VM running on the old HOST has the HTT (CPU Multi-Threading Capability)... as reported by HWiNFO. The new HOST PC does not have this.
I disabled Hyper-threading in the BIOS but HWiNFO still shows HTT green on the old HOST.
-
MISAdmin 386 Reputation points
2021-09-02T12:05:15.783+00:00 Hi Alex. Do you have anymore info that may assist with this?
-
Maddy 1 Reputation point
2021-10-22T20:04:59.583+00:00 I have experienced this problem when Windows updates installed the below updates on my Hyper-V Host. Had to uninstall the KB updates to bring my VMs back to life.
-
MISAdmin 386 Reputation points
2021-10-25T14:59:29.227+00:00 I didn't have any issues with my original host PC and Windows updates. It was only importing a VM from that host to a new host that failed.