06-14-2019 09:14 PM - edited 06-19-2019 09:20 AM
06-14-2019 09:14 PM - edited 06-19-2019 09:20 AM
Also live on Visual Studio Subscriptions on 6/19/19: https://my.visualstudio.com/Downloads?q=Microsoft%20Hyper-V%20Server%202019.
Thank you for your patience.
06-16-2019 02:29 AM
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..
06-17-2019 12:13 PM
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
06-17-2019 12:31 PM
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..
06-17-2019 11:54 PM - edited 06-17-2019 11:56 PM
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?
06-18-2019 03:21 AM
@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.
06-18-2019 06:21 AM
@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.
06-18-2019 06:26 AM
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?
06-18-2019 06:54 AM
@MasterMysterious Please refer to this earlier post. https://techcommunity.microsoft.com/t5/Windows-Server-Insiders/Microsoft-Hyper-V-Server-2019-release...
06-18-2019 07:27 AM
I am aware of KB4489899, and installed it on two systems, one pulling upgrades, the other does not. I was hoping the re-release is now a stable path forward.
I am willing to accept manual workarounds, but in essence I am hoping for an upgrade path rather than clean installs. Whether the upgrade updates only what changed, or replaces everything but preserves my app installs and configuration - I don´t really care.
06-20-2019 06:30 AM
We use the initial version of Hyper-V server since February 2019. It updates trough an WSUS without any issue. I notice that the memory leak in the storage pool is solved since the update 2019-06.
Now I have download and install the "newest" version of the Hyper-V Server 2019.
When I compare the version info of the initial release (now full patched) and the "newest" Hyper-V Server 2019 I see the same version (10.0.17763.557).
Not sure, but I think it's not necessary reinstall it.
06-20-2019 06:48 AM
@Thomas Heuberger If you have the same minor build number then you're probably fine.
06-21-2019 06:09 AM
06-29-2019 01:27 AM - edited 06-29-2019 01:30 AM
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"
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?
06-29-2019 06:51 AM
@Hermann1235 Hyper-V upgrade is not officially supported. Have you tried a clean install?
06-29-2019 07:44 AM
I haven't tried a clean install because it's my only one Hyper-V. So I cannot move VM and It's a lot of effort to reconfigure the server in a short time slot.
It seems the upgrade process is aware of in-place upgrade because and offer preserving existing data and also complain if VMs are running.
Also others mention that it finished successfully in prior versions.
07-02-2019 10:05 AM
07-02-2019 10:20 AM
07-02-2019 01:42 PM
Hyper-V Server upgrades aren't officially supported (nor has the validation of upgrades of various configurations of Hyper-V Server). I can put this on the potential feature list for future versions, but I do want to be clear that this isn't supported.
07-02-2019 01:45 PM
@Jim Wooldridge Understood. We didn't do this in production, but in-place upgrades have been a handy for us to update our dev environments without having to move VMs around and needing additional hardware.
07-02-2019 01:45 PM
Hyper-V Server upgrades aren't officially supported (nor has the validation of upgrades of various configurations of Hyper-V Server been conducted). Point well made that the install experience should handle and communicate this better. I can put upgrades on the potential feature list for future versions, but I do want to be clear that this isn't supported.
07-24-2019 04:23 PM
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.
07-24-2019 09:01 PM
@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.
08-02-2019 07:45 AM
@Jim Wooldridge If upgrades are not supported in any way, why is it even an option on the installer? Shouldnt it only allow clean installs?
09-18-2019 08:35 AM
I have tried both options in the installation UI of Hyper-V Server 2019: Either keep files (which I guess means upgrade) or delete all files (which I guess means clean install). Either way, the installation fails and automatically reverts back to the original Hyper-V Server 2016 that I had running before trying the installation. Currently, if I simply run setup.exe without any arguments, there is no way I can install Hyper-V Server 2019 on a machine running Hyper-V Server 2016. Also, I would like to comment that the new setup UI leaves a vast amount to be desired. The "clean install" options claims that it will delete all files, but it does not. I also didn't see a way to specify the installation location.
10-10-2019 08:44 PM
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.
10-15-2019 12:25 PM
@kamalswami Please refer to Jim Wooldridge's response on this thread from July: "Hyper-V Server upgrades aren't officially supported (nor has the validation of upgrades of various configurations of Hyper-V Server been conducted). Point well made that the install experience should handle and communicate this better. I can put upgrades on the potential feature list for future versions, but I do want to be clear that this isn't supported." Hyper-V is only released along with our LTSC versions so a new version is not expected in the short-term. At this point, we are still investigating options.
01-10-2020 02:54 PM
Not being able to inplace upgrade to Hyper-V Server 2019 would not be an issue if after a clean install it would be easy to reapply configurations to the new Host.
Neither the less, it would be an appreciated feature in future Hyper-V Server Releases.
Thanks for taking this to the feature list.