Creators Update and Hyper-V - Upgrade Configuration Version

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 17,635
    Windows 10 Pro
       #11

    So you mean that Windows 10 Settings app should only show Check for Windows updates option when there are actual updates available and remove that option from Settings when you are up to date, or various software should not have Check for updates option available when you already run the latest version? That context menu options and Hyper-V manager GUI options should be different for each VM?

    Don't take this too personally but of all pointless complaints about Windows and its software I've heard this one goes easily on Top 5 list :)
      My Computer


  2. Posts : 14
    Windows 10 Pro
       #12

    Sounds like your taking this too serious. Your entitled to your own opinion though
      My Computer


  3. Posts : 17,635
    Windows 10 Pro
       #13

    Exactly the opposite: I can't take a non-issue like this seriously!
      My Computer


  4. Posts : 14
    Windows 10 Pro
       #14

    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.
      My Computer


  5. Posts : 13,536
    Windows10
       #15

    rpmurph83 said:
    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!
      My Computer


  6. Posts : 11,168
    Windows / Linux : Arch Linux
       #16

    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
      My Computer


  7. Posts : 3,257
    Windows 10 Pro
       #17

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


  8. Posts : 19
    Windows 10 Ent x64
    Thread Starter
       #18

    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.
      My Computer


  9. Posts : 17,635
    Windows 10 Pro
       #19

    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:

    Creators Update and Hyper-V - Upgrade Configuration Version-image.png
      My Computer


  10. Posts : 14
    Windows 10 Pro
       #20

    Update on Hyper-V Configration Version


    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)."
    Last edited by rpmurph83; 02 Aug 2017 at 07:35. Reason: add quotes
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 03:50.
Find Us




Windows 10 Forums