[German]There is an issue with Hyper-V on Windows Server 2019 (and possibly Windows Server 2016). The Hyper-V platform cannot shut down virtual machines properly.
German blog reader Oli has informed me about the issue by mail a few days ago (thanks for that). Since it might be of interest to other administrators, here are some details. Oli wrote:
Windows Hyper-V Server 2019 – Shutdown issues with VMs
Since I just have this issue myself, here is a hint about a but in Hyper-V Server 2019 (and possibly Hyper-V Server 2016 as well?):
VMs, if you set them to “Shutdown” instead of “Save” (aka Snapshot, which is not a good idea e.g. for virtualized domain controllers), will not be shut down properly. After booting you will be greeted with the “Windows wasn’t shut down properly” message.
The joke is that this issue with Windows Hyper-V Server 2012R2/8.1 AND Windows Server Hyper-V 2016 also already occurred in the past, or occurs with Windows Hyper-V Server 2016 now again.
I didn’t have had this issue because I’m coming from Windows Hyper-V Server 2012 and the problem never occurred in 6 years. Maybe this is interesting for one or the other admin.
Oli sent the link to this Technet forum thread, where the problem has also been discussed.
Hyper-V 2019 – Guest VM’s shutdown unexpectedly
Since upgrading my Hyper-V servers to Windows Server 2019, including KB4471332 from last night, my guest VM’s do not power down on restart of the 2019 host.
I can confirm integration components are as up to date as possible, and each guest is configured to shutdown when the host restarts.
Each guest gets the “Why did I shutdown unexpectedly message”.
The even viewer yields the following all within 30 seconds of restarting the host: Shut down physical computer. Stopping/saving all virtual machines…
‘ADFS’ failed to perform the ‘Shutting Down’ operation. The virtual machine is currently performing the following operation: ‘Shutting Down’. (Virtual machine ID 0CFDF648-EE9D-4141-9EBD-9A6D911C3442)
‘ADFS’ failed to shut down. (Virtual machine ID 0CFDF648-EE9D-4141-9EBD-9A6D911C3442)
The Update Orchestrator Service service terminated with the following error: This operation returned because the timeout period expired.
Failed to restore configuration for port 59229EE2-C880-4BF2-9849-89A21EC17772 (Friendly Name: ) on switch 300C0E17-E123-4182-BE62-AAD1860BE841 (Friendly Name: ), status = Object Name not found..
Everything is configured as it was on the 2016 Hyper-V host.
The message ADFS failed to shut down because it is shutting down seems terribly odd to me. Of course its shutting down, just need the host to wait. (Yes the registry is set to 120 as the default time for the host….)
Fairly simple to recreate….just spin up a 2019 server, install Hyper-V role, throw in a VM and test.
There the issue has been discussed since December 2018, with users confirming the issue. It’s unpleasant that this bug has been reported earlier within the support article KB289680 from Microsoft. In my view it’s stupid what the Microsoft employees posting within the Technet tread. A user wrote ‘posting a bug here in the forum is like discussing with a wall’. In any case, the hope of those affected that a fix would come in January 2019 was disappointed. Whether an update in February will solve the issue will have to be seen. Maybe it will help you if someone is affected.
Cookies helps to fund this blog: Cookie settings