Windows 10: Creators Update and Hyper-V - Upgrade Configuration Version

In the past when the button to upgrade hyper-v config version appears after a major update, clicking on it always upgrades the config version and no they shouldn't remove the check for updates button when there aren't any updates. This is completely different. It's not asking me to check for an upgrade version, it's asking if I want to upgrade them now.

 

Who cares - you click on it and nothing happens. You can have lots of VMs and you want Hyper-V to be more intelligent to conditionally hide the button based on what info it gets. Why bother - it just adds more programming complexity to Hyper-V interface and more risk of bugs? Flexibility comes at a price!

 

Hi there

OT but sometimes the OPPOSITE is true -- when an application is DUMBED DOWN too much e.g some of those 1-click easy install things then it becomes almost impossible to fix or re-do if something goes wrong.

However I agree with the previous post in this case -- HYPER-V works fine the way it currently does.

KISS is good so long as everything is not TOO simple.

Cheers
jimbo

 

Slightly off topic, but why is 8.0 the default anyways?

 

I don't know.
You cannot change it to 8.1 although it is available, as you can see in screenshot in my first post.

 

I openly admit that regarding what amuses me, I am a bit pervert. This thread is a good example of that.

What do you guys expect to achieve if you could now upgrade to 8.1? What would be the benefits?

We are still using configuration version 8.0 as column "IsDefault" in cmdlet Get-VMHostSupportedVersion shows (value TRUE). It is the default.

Version 8.1 is still shown as FALSE, it will most certainly become new default after one of the near future cumulative updates:

 

This is from a Microsoft employee on TechNet..

"Hey all,

Thanks to everyone for reporting this bug. We are aware of the underlying issue and a fix is in the works.
The upgrade button is incorrectly showing up in Hyper-V Manager for virtual machines with Configuration Version 8.0, when upgrade is not really available. The default VM configuration version for Windows 10 Creators Update is version 8.0. Version 8.1 is currently only accessible through PowerShell or WMI during virtual machine creation (Windows Server 2016 does not support version 8.1 and won't be able to run these VMs)."

 

@rpmurph83, it would be interesting if you had a link for that quote as clearly there are some differences between 8.0 and 8.1 - even if they are not yet documented.

 

I have upgraded now to Fall Creators Update (1709), and now when I click on "Upgrade Configuration Version" in Hyper-V, my VMs are upgraded to version 8.2.

So I'm gonna marked this as solved *Smile

 

What is the difference then? Any new features in 8.2?