Solved The virtual machine is not compatible with physical computer

ardelean94 · Apr 9, 2024

Hi,

I'm running a laptop with 2 extended - 4k monitors, windows version 23H2 (OS Build 22631.3296).
A few weeks ago I had to change my resolutions from 4K to 2K to accommodate a project that I'm using within a Virtual Machine.

However, after I did that, I start the VM and at the end I saved the state of the machine.
When I tried to start the saved state I got this error:

"VM_Name failed to restore
The virtual machine is not compatible with physical computer"

In summary, the only thing I changed was the resolution and now I do not know where to look for the issue or how to approach it.
Now, in order to start the VM every time I have to shut the machine down and start clean.

Thank you for the support,
Alex

cereberus · Apr 9, 2024

ardelean94 said:
Hi,

I'm running a laptop with 2 extended - 4k monitors, windows version 23H2 (OS Build 22631.3296).
A few weeks ago I had to change my resolutions from 4K to 2K to accommodate a project that I'm using within a Virtual Machine.

However, after I did that, I start the VM and at the end I saved the state of the machine.
When I tried to start the saved state I got this error:

"VM_Name failed to restore
The virtual machine is not compatible with physical computer"

In summary, the only thing I changed was the resolution and now I do not know where to look for the issue or how to approach it.
Now, in order to start the VM every time I have to shut the machine down and start clean.

Thank you for the support,
Alex

Which vm software?

ardelean94 · Apr 9, 2024

cereberus said:
Which vm software?

Hyper-V Manager - It's a Windows Server 2019 Standard, Version 1809, OS Build: 17763.5576
Hyper-V Manager Version: 10.0.22621.1

jimbo45 · Apr 10, 2024

ardelean94 said:
Hyper-V Manager - It's a Windows Server 2019 Standard, Version 1809, OS Build: 17763.5576
Hyper-V Manager Version: 10.0.22621.1

Try the latest Windows server LTSC 2022 -- you can get free trial for 180 days and extend for 5 times so plenty of time for testing on VM etc etc. I run it as a decent desktop OS and as a HOST it's great for hosting HYPER-V VM's.

I'd imagine your hardware should work on it.

Works a treat both as VM and HOST.

Cheers
jimbo

cereberus · Apr 10, 2024

jimbo45 said:
Try the latest Windows server LTSC 2022 -- you can get free trial for 180 days and extend for 5 times so plenty of time for testing on VM etc etc. I run it as a decent desktop OS and as a HOST it's great for hosting HYPER-V VM's.

I'd imagine your hardware should work on it.

Works a treat both as VM and HOST.

Cheers
jimbo

This is irrelevant to OP's question.

ardelean94 · Apr 11, 2024

jimbo45 said:
Try the latest Windows server LTSC 2022 -- you can get free trial for 180 days and extend for 5 times so plenty of time for testing on VM etc etc. I run it as a decent desktop OS and as a HOST it's great for hosting HYPER-V VM's.

I'd imagine your hardware should work on it.

Works a treat both as VM and HOST.

Cheers
jimbo

Thanks, but that is not possible due to the business agreements at this time.

Since it worked just fine before and it stopped working since I changed the resolution I think there's a difference in data when it saves the state of the machine and when it tries to open it up again. I checked the logs via Events Viewer but that also does not provide any other information.

Hopachi · Apr 11, 2024

That error doesn't have ~~many~~ solutions, if any, from what search results give at the moment... deleting the saved state is the only solution here.

You probably seen this already:

Restored Hyper-V virtual machines won't start - Windows Server

Provides a solution to an issue where Hyper-V virtual machines that are restored to a new Hyper-V Host machine won't start.

learn.microsoft.com

But you only have one host in this case. Causes? There is that network adapter name possibility which I doubt, then what remains is most likely some 'conflict in the saved state data' to blame.

This behavior is expected and by design. Step 4 in the Resolution section will resolve the second cause listed in the Cause section, by deleting the saved state data you allow the machine to reset the video state.

That sounds like the saved state is broken and can no longer be restored, if the video state needs to be reset.

mrPeter · Apr 19, 2024

Sounds like an Windows update problem to me .. I just noticed that one of my test rigs died it runs Win11 22H2 as os with Hyper-V with two Windows10 22H2 and 21H2 on it. Died about 10days ago this should be around where yours died to.

The VM responds with "is not compatible with the physical computer"
the physical computer is not touched

creating a new VM on the device works fine

This is my guesses that the serving OS Windows11 updated and broke something in the "state" of its VM:s
Deleting the saved state made it so I could get it back up again.....

Solution:
Rightclick on VM
select Delete State
finish dialogs
then start VM to show it works

ardelean94 · Apr 23, 2024

Hopachi said:
That error doesn't have ~~many~~ solutions, if any, from what search results give at the moment... deleting the saved state is the only solution here.

You probably seen this already:

Restored Hyper-V virtual machines won't start - Windows Server

Provides a solution to an issue where Hyper-V virtual machines that are restored to a new Hyper-V Host machine won't start.

learn.microsoft.com

But you only have one host in this case. Causes? There is that network adapter name possibility which I doubt, then what remains is most likely some 'conflict in the saved state data' to blame.

That sounds like the saved state is broken and can no longer be restored, if the video state needs to be reset.

Thanks Hopachi for the input.

Weirdly enough, I haven't found that link until you posted it, will check it out as soon as I get the work done here

ardelean94 · Apr 23, 2024

mrPeter said:
Sounds like an Windows update problem to me .. I just noticed that one of my test rigs died it runs Win11 22H2 as os with Hyper-V with two Windows10 22H2 and 21H2 on it. Died about 10days ago this should be around where yours died to.

The VM responds with "is not compatible with the physical computer"
the physical computer is not touched

creating a new VM on the device works fine

This is my guesses that the serving OS Windows11 updated and broke something in the "state" of its VM:s
Deleting the saved state made it so I could get it back up again.....

Solution:
Rightclick on VM
select Delete State
finish dialogs
then start VM to show it works

Are you suggesting to delete the VM state and start over? If so, that's the 'solution' I have atm but not happy with.

What came to mind was to create another VM and try to import a checkpoint that I have from this one.

ardelean94 · May 17, 2024

Reporting back on this thread.
Finally I managed to find a way to have the VM's Saved State feature back.

What I did to fix it:

1. Create a checkpoint of the old VM that had its Saved State broken
2. Export the checkpoint
3. Create a new VM and Import the newly exported checkpoint

Hope that helps,
Alex

Hopachi · May 24, 2024

Thanks for reporting back on this!
Hope the solution will help others on similar cases.

Solved The virtual machine is not compatible with physical computer

New member

My Computer

Well-known member

My Computer

New member

My Computer

Well-known member

My Computer

Well-known member

My Computer

New member

My Computer

Well-known member

My Computers

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Well-known member

My Computers

Similar threads