Forum Discussion

  • ChrisKnight's avatar
    ChrisKnight
    Brass Contributor

    In the interest of saving everyone's valuable time, it appears that Hyper-V Server 2019 no longer provides the ability to perform an in-place upgrade. Additionally running setup.exe on an existing Hyper-V Server (checked with 2012 R2 and 2016) and performing either of the setup options (upgrade or clean install) will result in a failed installation. Just tested these options with the latest ISO (17763.737.190906-2324.rs5_release_svc_refresh_SERVERHYPERCORE_OEM_x64FRE_en-us_1.ISO as of writing).

     

    The only way to install Hyper-V Server 2019 is to boot from the ISO and perform a clean install.

     

    It'd be nice if Microsoft documented this somewhere, especially as it's a behavioural change from past releases.

     

  • kgncc's avatar
    kgncc
    Copper Contributor

    The latest download for Hyper-V Server on the Eval site is 17763 (1809). Does anyone know when Hyper-V Server 1903 (18362) might be release? I would really like to use FoD 1903.

    • Mary Hoffman's avatar
      Mary Hoffman
      Icon for Microsoft rankMicrosoft

      kgncc Microsoft Hyper-V Server is part of the Long-Term Servicing Channel (LTSC). It only releases when we release the LTSC version of Windows Server, every 2-3 years. 1903 was a Semi-Annual Channel release, so there is no 1903 version of stand-alone Hyper-V Server.

  • Hermann1235's avatar
    Hermann1235
    Copper Contributor

    Mary Hoffman 

    Hello Mary,

    I've downloaded 17763.557.190612-0019.rs5_release_svc_refresh_SERVERHYPERCORE_OEM_x64FRE_de-de.iso from the Eval center site.

    I have running Hyper-V 2016 and want to update in-place.

    The update finally fails with error 0x80070490 - 0x2000E: 

    "The installation failed in the SAFE_OS phase with an error during SET_Product_Key operation"

    From setupact.log:

    2019-06-29 01:08:28, Error DISM DISM Transmog Provider: PID=1360 TID=1388 Unable to retrieve pkey info; hr = 0x80070490 - CTransmogManager::InitializeProductKey
    2019-06-29 01:08:28, Error DISM DISM Transmog Provider: PID=1360 TID=1388 [Product Key wird festgelegt]: Der angegebene Product Key konnte nicht überprüft werden.
    Stellen Sie sicher, dass der angegebene Product Key gültig ist und der Zieledition entspricht.
    [hrError=0x80070490] - CTransmogManager::EventError"

    The highlighted part means: "The specified Product key could not be verified"

    Since Hyper-V has no Product key might this be the cause?

    How can I get this fixed?

     

    Hermann

      • joachiml's avatar
        joachiml
        Copper Contributor

        Mary Hoffman Ben Armstrong 

        I think it is obvious that upgrade capabilities for Hyper-V make a lot of sense and there is a lot of interest in it. I really hope upgrade is considered for the next release.

        Thanks, Joachim

  • Mary Hoffman

    Hi. I'm sorry, but this is confusing. You see, I've possessed a copy of Hyper-V 2019 for a long time. Downloaded it from Microsoft too. So, what are you saying here exactly? Are you announcing a new version? Or are you announcing the availability six months late?

    • Mary Hoffman's avatar
      Mary Hoffman
      Icon for Microsoft rankMicrosoft

      MasterMysterious It was live very briefly last fall and recalled due to issues discovered after release,  issues that could not be serviced. You should replace the version you have with the one just released as it addresses those issues.

      • MasterMysterious's avatar
        MasterMysterious
        Brass Contributor

        Mary Hoffman 

        That's probably a couple of gigabytes of download and a whole re-installation. Isn't it possible to just fix what I have with an update or service pack?

        Also, what issues? Since I have installed the problematic release, have I been losing data or doing something damaging to myself without knowing?

  • joachiml's avatar
    joachiml
    Copper Contributor

    Mary Hoffman 

    Thanks for making that available. I guess all of us have been waiting for it.

    I downloaded and tried to upgrade a virtual machine that isrunning a Hyper-V 2019 1809. First I encountered an 0xC1900101 - 0x20017 but that disappeared after increasing memory allocation (install could check for that). After increasing memory, setup proceeded, but then stopped with 0x80070490 -0x2000e "The installation failed in the SAFE_OS phase with an error during SET_PRODUCT_KEY operation).

    Any idea what I can try?

    I also want to upgrade a physical host - the VM was just to get experience first..

    Thanks Joachim

    • DannyBoy2042's avatar
      DannyBoy2042
      Brass Contributor

      joachiml We had same exact issue doing an in place upgrade.  In place upgrades have always worked very well in previous versions of Hyper-V.  We never do it in production but always worked very well in testing.

    • Ben Armstrong's avatar
      Ben Armstrong
      Icon for Microsoft rankMicrosoft

      We have never supported in-place upgrade with the stand alone Hyper-V server.  Do you see any issues when performing a clean installation? joachiml 

      • joachiml's avatar
        joachiml
        Copper Contributor

        Ben Armstrong 

        Hi Ben,

        I do. Even running just virtual machines, the host needs configuration, ranging from bitlocker, domain join, backup, etc.. Some 3rd party software ties into the installation without import/export capabilities.

        I definitely appreciate upgrade support, in particular as frequency increases..

        Thanks, Joachim

Resources