This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 23%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDD%3C/text%3E%3C/svg%3E)
Hi all,
Years ago, I virtualized an old Windows 7 machine using Hyper-V and have been running it on a Windows 10 box. Everything is working well except that host machine is getting old too and in anticipation of its inevitable demise, I had to move the VM to a newer machine, a Windows 11 laptop.
So from Hyper-V manager on the old host, I exported the VM to a flash drive, and then, on the new host, tried to import it. This message appeared:
I chose "Delete Saved State" and proceeded with the import, and it worked. Well, kind of. On the new host machine, the VM does appear to work but not as expected and certainly not the same way it did on the old host machine. Every time the host machine is rebooted, the VM refuses to start with the error
The virtual machine <name> is not compatible with physical computer <computer name>.
To get it working I have to delete the saved state but then the VM returns to the original state and all changes since the last reboot are gone. Also, the VM itself gets rebooted instead of staying in the current state.
Both host machines are Intel except the original host is Core 7 and the new one Core 5.
Also, the VM on the original host has two network adapters. One is the standard one and the other was added by me. I can't remember why I added this 2nd adapter. I added an adapter with the same name on the new host machine, but that does not seem to help.
Any help will be greatly appreciated.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 21%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
Hi DC Dweller,
I take its gen 1 in Hyper-V.
Remove all network adapters and manually replace it with the host adapter.
This might help as well, shut down the VM for this setting to be live.
"Every time the host machine is rebooted, the VM refuses to start with the error", which error is this and have you got the VM to restart when Windows starts
Thank you for replying. The error is shown in the original post, "The virtual machine <name> is not compatible with physical computer <computer name>."
The problem is definitely related to the saved state. If, instead of saving the state, I just turn the VM off, then it restarts fine. But if I save it, it refuses to start unless or until I delete the saved state. So the workaround I have found is to NOT save, and I configured the VM to turn off instead of save when the host machine is shut down.
Do you happen to know why being in the Saved status has such a catastrophic effect?
Two things, did you try that setting above for CPU and when you exported the VM did you shut it down first or did you use save?
Also which options are you using here and what were they set on in your old host?
I did not shut down the original VM before exporting it. Should I have? Do you think this is the reason for this behavior?
The options are the same on both hosts.
If you don't shut and removed saved states it cant use the saved states as the two CPU have different features , have you still got the original VM on your old system?
First have you tried shutting down the VM on the new host, change the settings for CPU and apply new network adapter, then start it up and see what happens.
