VMHostSupportedVersion update config version

Joe 1 Reputation point
2021-03-05T19:28:06.803+00:00

When can I update my VMs? According to the docs here: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/upgrade-virtual-machine-version-in-hyper-v-on-windows-or-windows-server#supported-vm-configuration-versions-for-semi-annual-channel-hosts

v1903 should allow me to update to 9.1

Edition Windows 10 Pro Version 20H2 Installed on ‎8/‎14/‎2020 OS build 19042.844 Experience Windows Feature Experience Pack 120.2212.551.0

I'm running version 1904 according to the above string.

> Get-VMHostSupportedVersion

Name Version IsDefault ---- ------- --------- Microsoft Windows 10 Anniversary Update/Server 2016 8.0 False Microsoft Windows 10 Creators Update 8.1 False Microsoft Windows 10 Fall Creators Update/Server 1709 8.2 False Microsoft Windows 10 April 2018 Update/Server 1803 8.3 False Microsoft Windows 10 October 2018 Update/Server 2019 9.0 True Microsoft Windows 10 May 2019 Update/Server 1903 9.1 False Microsoft Windows 10 May 2020 Update/Server 2003 9.2 False

but it does not work.

> Update-VMVersion myvm -Force WARNING: No update was performed for the virtual machine "myvm" because its configuration version is already at the maximum level supported by this server. For clustered servers, the maximum supported configuration version can be limited by the cluster functional level.

Is there something I need to do to enable this update feature that exists on my host?

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,546 questions
0 comments No comments
{count} votes

5 answers

Sort by: Most helpful
  1. Xiaowei He 9,871 Reputation points
    2021-03-08T08:25:33.893+00:00

    Hi,

    According to the "Get-VMHostSupportedVersion", version 9.1 and 9.2 is not supported, so the VM is unable to update configuration version, would you please run "winver" in powershell and then show the screenshot of the Hyper V host system version for us.

    Thanks for your time!
    Best Regards,
    Anne


    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Joe 1 Reputation point
    2021-03-08T19:30:26.617+00:00

    This appears to be the same information I already provided above. What else do you need?

    75592-image.png

    0 comments No comments

  3. Joe 1 Reputation point
    2021-03-08T19:34:32.593+00:00

    I'm not sure if you understand my question.

    Microsoft Documentation says that semi-annual release channel should support VM Configuration version 9.1.

    I am on that channel from what I can tell, and my windows version is higher than the documentation says supports 9.1 (Windows 10 May 2019 Update (version 1903)).

    In fact, my host even says it supports 9.1 AND 9.2 (which is not even in documentation) but they are not default..? Is that correct?

    So, where is the disconnect here between the documentation and reality? Why does my host not support what documentation says it should?

    0 comments No comments

  4. Eric Siron 1,251 Reputation points MVP
    2021-03-08T22:54:35.173+00:00

    I haven't looked at these in a while, but I had not ever heard that 9.1 or 9.2 moved out of "experimental" status. They have no feature or fix data beyond 9.0. I have a lot of suppositions that I could make here, but the only guess that I've got enough background to publish would be that if you get your hands on a v9.1 or v9.2 VM, it will run on this host. The ability to run a VM at that level does not necessarily mean that it can update VMs to that level.


  5. SpamFiltration 1 Reputation point
    2022-11-14T01:29:49.27+00:00

    I know this is old but I have the same issue when trying to update the existing VM. I'm still searching for an answer. One thing that does work though is creating a new vm with the higher version:
    (New-VM -Name "NewVM" -Version 9.2)

    0 comments No comments