none
Hyper-V 2019 - Guest VM's shutdown unexpectedly RRS feed

  • 问题

  • Hi,

    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.

    Any help would be appreciated, but my money is on it being another bug.

    2018年12月12日 8:26

答案

全部回复

  • Hi,

    Thanks for posting in our forum!

    I am a bit confused about your description, as i understand, you upgrade your hyper-v server from 2016 to 2019, and when you restart the 2019 host, the vm also restart automatically. if i misunderstand, please let me know.

    In addition, could you please provide a screenshot of your vm settings? just like below:

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    2018年12月13日 8:19
    版主
  • Daniel,

    You misunderstand.

    Quite simply, when I reboot the 2019 host, the VM's are set to shutdown, not restart.

    The host is NOT waiting for the guest VMs to shutdown, resorting in the guests all saying "Why did I unexpectedly shutdown" e.g. the power was pulled....

    The host restarts as expected, but it is NOT waiting for the VM's to shutdown cleanly before doing so.

    2018年12月13日 9:10
  • Hi,

    Thanks for your reply!

    May i know which option do you check in automatic stop action in hyper-v settings:

    In addition, you can refer to the following link,maybe can help you:

    https://support.microsoft.com/en-gb/help/2028504/windows-kernel-event-id-41-error-the-system-has-rebooted-without-clean

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    2018年12月14日 8:19
    版主
  • I absolutely agree with ProximusAl that there is a bug in Windows Server 2019.

    I believe ProximusAl selected the "Shut down the guest operating system" option and the guest VMs fail to gracefully shutdown

    We need to receive update from Windows to fix this bug. I wish to highlight that Windows Server 2012 R2 and Windows 8.1 previously had this problem until Microsoft released an update to fix the bug.

    https://support.microsoft.com/en-my/help/2896800/hyper-v-guest-os-does-not-shut-down-when-you-restart-the-host-computer

    2018年12月14日 13:49
  • I am also seeing this behavior on our test system with Server 2019. I even made a powershell shutdown script to run guest shutdown on the VMs, and it works perfectly if I run it manually, but if I ask the server to restart/shutdown the VMs all get stopped improperly. They are all configured for "shut down the guest operating system" in Hyper-V manager.

    2018年12月14日 15:19
  • Hi,

    This is Daniel and wish you all the best!

    May I know whether your problem is solved? If you have any question, please let me know.

    Thanks for your time and have a nice day!

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    2018年12月17日 2:13
    版主
  • Hi Daniel, 

    Unfortunately, this problem is not fixed. We will need an update from windows to rectify this bug in Windows Server 2019. 

    This error was previously reported for Windows Server 2012 R2 and Windows 8.1 

    https://support.microsoft.com/en-my/help/2896800/hyper-v-guest-os-does-not-shut-down-when-you-restart-the-host-computer

    Here's the except from the article: 

    Hyper-V guest OS does not shut down when you restart the host computer that is running Windows Server 2012 R2 or Windows 8.1

    Applies to: Windows 8.1Windows 8.1 ProWindows 8.1 Enterprise More

    Symptoms

    Consider the following scenario:

    You set up a Hyper-V virtual machine on a host computer that is running Windows Server 2012 R2 or Windows 8.1.
    You set the Automatic Stop Action setting of the virtual machine to Shut down the guest operating system.
    You restart the host computer.

    In this scenario, the guest operating system (OS) on the virtual machine does not shut down. Additionally, after you restart the virtual machine, the following event is logged on the guest OS: Note If the computer is part of a cluster, this issue does not occur.


    Cause
    This issue occurs because the Virtual Machine Management Service tries to shut down the virtual machine by using the Virtual Machine Worker process. However, the process encounters a logic failure that causes the shutdown operation to fail and reverts the shutdown operation. Therefore, power cycling occurs instead of a clean shutdown.


    Resolution
    Update information
    To resolve this issue, install update rollup 2887595. For more information about how to obtain this update rollup package, click the following article number to go to the article in the Microsoft Knowledge Base:
    2887595 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: November 2013


    2018年12月17日 3:21
  • Hi Daniel, 

    Thank you for looking into this issue and I hope it can be fixed. 

    Best regards,

    Jeff

    2018年12月17日 7:45
  • Hi jeff,

    I will post in our forum if i have any progress.

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    2018年12月17日 8:11
    版主
  • Hi,

    Hope you are doing well!

    I haven't received your reply for a while, how is the problem now, if your problem is solved, would you please share your experience with us? if there is anything need to help, please let me know. In addition, if anyone’s reply is helpful to your problem, please mark it as an answer at your convenience so that other people who have similar problem can refer to. I appreciate your cooperation!

    Thanks for your time and have a nice day!

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    2018年12月19日 2:43
    版主
  • I am also seeing this behavior on our test system with Server 2019. I even made a powershell shutdown script to run guest shutdown on the VMs, and it works perfectly if I run it manually, but if I ask the server to restart/shutdown the VMs all get stopped improperly. They are all configured for "shut down the guest operating system" in Hyper-V manager.

    I got the exactly same issue through on the testing server.  The VMs just export from a Server 2016 Hyper-v.

    on Server 2019, the host system reboot, the VMs are just "lost power". It looks like 2019 host os never wait the VMs shutdown gracefully, or just skip the shutdown VM procedure.

    after comb the events, no error found. So I assume this is a bug of Server 2019

    2018年12月19日 11:39
  • I got the same issue, no fix found. 

    So we have to write powershell script to work around it like the others.

    Still waiting MS to fix the bug. Our Server Updating plans have to be postponed 

    2018年12月19日 11:44
  • I'd like to add to this. Although I made a powershell script to shutdown the guest VMs and this does work when I run it manually, if I add it to "shutdown scripts" via group policy, it looks like it kills the VMs before running the script, so this doesn't even function as a work around.

    Microsoft needs to take a look at this and fix whatever is causing it as it is now confirmed by several different people with Server 2019 (per this thread).

    2018年12月19日 21:38
  • Hi bud. 

    group policy script runs after most service had already stopped.

    If you put your script to "shutdown scripts" in group policy, when the system get to your script, those Hyper-v services are already stopped, that means the VMs are already been killed before the script running.

    My way is to create a schedule task to run the script.

    Hope this might help you.

    2018年12月20日 7:26
  • Thanks Colin. I was just trying to clarify that a group policy shutdown script didn't seem to be a valid work-around in case my previous comment was read that way.

    2018年12月20日 15:44
  • Hi ProximusAl,

    How is the problem now? if you have any other concerns, please let me know.

    Merry Christmas!

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    2018年12月21日 9:33
    版主
  • Hi ProximusAl,

    How is the problem now? if you have any other concerns, please let me know.

    Merry Christmas!<o:p></o:p>

    Best Regards,<o:p></o:p>

    Daniel<o:p></o:p>


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Errr, the problem still exists as it’s a BUG. Nothing I can do will fix it, these needs action from Microsoft. You can clearly see from this thread that many people have the problem. Merry Christmas
    2018年12月21日 14:10
  • Hi,

    Thanks for your reply!

    I need to reproduce your environment and test it, would you please help me clarify the following information?

    1. What's the version number of your Host?

    2. What are your virtual machine settings?


    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    2018年12月24日 7:06
    版主
  • Forgive me for losing my cool, but the information you are asking for are literally the first two sentences of the OP and has been reiterated several times by many of us.

    If it helps, I'll unnecessarily post my settings in a screenshot (which are the same as his, per his comments).

    Guest shutdown works correctly via powershell, but not if initiated by a Hyper-V host shutdown.

    It affects all of my guests on this host, regardless of guest OS version.

    Merry Christmas everyone.



    2018年12月24日 15:27
  • Forgive me for losing my cool, but the information you are asking for are literally the first two sentences of the OP and has been reiterated several times by many of us.

    If it helps, I'll unnecessarily post my settings in a screenshot (which are the same as his, per his comments).

    Guest shutdown works correctly via powershell, but not if initiated by a Hyper-V host shutdown.

    It affects all of my guests on this host, regardless of guest OS version.

    Merry Christmas everyone.




    Cheers Fill I hate these forums so much sometimes with a passion as you explain everything quite clearly in the first post and get utter **** in return. It’s quite simple. 1. Install the Hyper-V role on server 2019 2. Install a VM of your choice 3. Set the VM settings to shutdown when the host shutsdown 4. Shutdown the host and observe the consequences on the VM It can’t be anymore simple. My stomach turns everytime I read a new post on this forum, especially from Microsoft. Just fix the ruddy bug FFS.
    2018年12月24日 21:26
  • Forgive me for losing my cool, but the information you are asking for are literally the first two sentences of the OP and has been reiterated several times by many of us.

    If it helps, I'll unnecessarily post my settings in a screenshot (which are the same as his, per his comments).

    Guest shutdown works correctly via powershell, but not if initiated by a Hyper-V host shutdown.

    It affects all of my guests on this host, regardless of guest OS version.

    Merry Christmas everyone.



    Exactly same condition I encountered.

    By the way, my Host system upgraded to 17763.195, and the problem is still there

    Merry Christmas everyone.

    2018年12月25日 9:37
  • So many guys repeat this problem so clearly.

    Just make a bug report to the coding team or some other Dpt, Please.

    Sometime discussing errors in this forum feels like talking to the wall.

    Please make the bug report already! please please!

    Merry Christmas

    2018年12月25日 9:46
  • Hi,

    I am testing now, please wait for my update!

    Merry Christmas!

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    2018年12月25日 9:49
    版主
  • Hi,

    I am testing now, please wait for my update!

    Merry Christmas!

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    So what's the story Danie1zhou?

    Have you managed to recreate this issue and reported it as a bug?

    2019年1月2日 13:21
  • Hi,

    Thanks for your reply!

    The results of my tests are the same as yours.I have reported the result. Please wait patiently. I will let you know as soon as the result is available.

    Thanks for your understanding!

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    2019年1月3日 3:03
    版主
  • Has passes 1 year...

    Is the problem solved?

    I still run into it!

    2019年1月9日 14:46
  • Just wanted to add to this that we have started to see this behavior (2 maybe 3 months now) with our 2016 Hyper-V hosts as well...

    So PLEASE include the 2016 OS in any bug-fix/resolution

    2019年1月16日 14:30
  • Hi,

    Thanks for your reply!

    The results of my tests are the same as yours.I have reported the result. Please wait patiently. I will let you know as soon as the result is available.

    Thanks for your understanding!

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Jan 10 updates had been already rolled out and installed, The problem still there.

    Is this topic going cold? We still look forward to update our servers to 2019

    2019年1月25日 5:16
  • Hi,

    Thanks for your reply!

    The results of my tests are the same as yours.I have reported the result. Please wait patiently. I will let you know as soon as the result is available.

    Thanks for your understanding!

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Jan 10 updates had been already rolled out and installed, The problem still there.

    Is this topic going cold? We still look forward to update our servers to 2019

    I would have been surprised if this was addressed in January but it would be nice to get a confirmation that this has been acknowledged by the developers and a fix is in the works for February.

    2019年1月25日 22:23
  • Wow. How can a bug like this be introduced into a "Production" level build of Windows Server not once, but TWICE? This is the exact same issue that occurred when 2016 was released. It took the Microsoft rep close to a month to acknowledge that this was even a problem, now we are just waiting for a fix with no official report from Microsoft.

    I finished upgrading my test host cluster to 2019 a few days ago. Power cycle the all of the hosts and am greeted with the lovely "why did the computer shut down" message on all VMs.

    Microsoft clearly does not care about QA anymore. Issues like this make me want to switch to VMware.

    As a couple posters above mentioned, it makes me want to throw something every time I see a Microsoft rep use the most useless canned response on a thread like this. All of the info is in the OP, there is no reason why this could not have been addressed quicker. I honestly trust random community members more than official Microsoft reps due to all the crap I see posted by them.

    2019年1月26日 1:54
  • Hi,

    Thanks for your reply!

    The results of my tests are the same as yours.I have reported the result. Please wait patiently. I will let you know as soon as the result is available.

    Thanks for your understanding!

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact 

    I have the same problem. Now it's February and the BUG is still there, this is a shame.
    2019年2月3日 22:09
  • Could anybody of the affected crowd test if setting the automatic stop action to "Save the virtual machine state" (=suspend the VM) makes a difference? Because that is the default and what we use and never had any problem on no version of hyper-v.

    By the way, I would encourage people to use suspend, we never had any problems with it and we host all sorts of VMs (SQL Servers, DCs, File servers, clients,...).

    2019年2月5日 16:56
  • It does seem that Save works still yes. However, this is not a solution. It's good to know that Save works on DCs, I've always avoided it on them. One of the problems with Save is that it reserves space for the amount of RAM a VM is using. On systems with large amounts of RAM, this could be terabytes of space used just to enable Save.

    I'm hoping that there is a fix released this patch Tuesday.



    2019年2月8日 21:28
  • Hi,

    Thanks for your reply!

    The results of my tests are the same as yours.I have reported the result. Please wait patiently. I will let you know as soon as the result is available.

    Thanks for your understanding!

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    I just updated to the February 2019 update and this issue is still not fixed.

    Kolby is right - "Save" is not an option for everyone.

    I think this thread has been abandoned - the closest thing to a Microsoft employee we've seen hasn't replied to anything lately. We've had no confirmation that this has been recognized by developers.

    I'll see if I can find a better way to report this.

    2019年2月14日 17:21
  • Hi,

    Thanks for your reply!

    The results of my tests are the same as yours.I have reported the result. Please wait patiently. I will let you know as soon as the result is available.

    Thanks for your understanding!

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    I just updated to the February 2019 update and this issue is still not fixed.

    Kolby is right - "Save" is not an option for everyone.

    I think this thread has been abandoned - the closest thing to a Microsoft employee we've seen hasn't replied to anything lately. We've had no confirmation that this has been recognized by developers.

    I'll see if I can find a better way to report this.

    I hope there's another way to get Microsoft to fix this bug. It's still remains unresolved at my end. =(
    2019年2月16日 1:37
  • Same issue here. Server 2019, build 10.0.17763.316. This is a huge bummer.
    2019年2月16日 15:51
  • I wanted to chime in we've seen the same behavior.  Fresh Windows 2019 installs with the latest Windows Updates on new Dell servers.  VMs were exported from Windows 2012 Hyper-V server and imported into Windows 2019 Hyper-V server and had their Config Version upgraded to 9.0.  All replicate to an identical equipped and configured server.

    I've had a lot of issues with Windows Server 2019 as a Hyper-V host system being unstable.

    • This issue
    • Some VMs don't start even though automatic start is set if a delay is assigned
    • The main VMM service becomes unresponsive to communications from itself, PowerShell, and Hyper-V Manager remotely requiring a hard power off since the system won't shutdown
    • If a teamed NIC is using LACP and Hyper-V starts before LACP completes negotiation Hyper-V will fail to start some VMs because of a lack of network resources

    Systems Administrator Senior - University of Central Florida

    2019年2月20日 16:09
  • Anyone want to put a bet on this getting sorted with cumulative update tonight?
    2019年3月12日 15:03
  • Did any get this to work after the CU? I'm withholding my updates until this gets resolved. 
    2019年3月14日 4:18
  • Nope!

    The problem is still unsolved. 

    Our heavy load servers still run on Server 2016. Testing server stick with the shutdown script and waiting the patch or the update.

    This kind situation is really disappointing. 

    2019年4月2日 15:59
  • Nope!

    The problem is still unsolved. 

    Our heavy load servers still run on Server 2016. Testing server stick with the shutdown script and waiting the patch or the update.

    This kind situation is really disappointing. 

    This is very sad.

    This problem is also described in these websites too:

    https://borncity.com/win/2019/02/08/hyper-v-vm-shutdown-issue-in-windows-server-2019/

    https://appuals.com/hyper-v-vm-shutdown-problem-in-windows-server-2019/


    2019年4月3日 7:09
  • I have the same issue.
    I can not belive that MS does not fixing it.
    Every update is a nightmare.
    2019年4月5日 16:53
  • I cannot believe this. This is f***** Microsoft, not a laughable little software company. This should not at all be your standard, Microsoft. I cannot take a company like this seriously. Here you have the feedback. Why do you even collect telemetry data, if you can't even listen to what people say?

    I cannot say anything else than that Microsoft is really p****** me off at this point. It is one thing, if that occurs on a client OS, but this is a serious issue on servers. Thank god that at least Microsoft Windows can handle the unexpected shutdown quite well. I don't want to know what happens on other OSs, not to mention on DBMSs that are not as bullet-proof as MSSQL Server.

    Sorry, but I really had to get this off my chest!



    2019年4月10日 14:17
  • Being completely sincere and no hyperbolic, I have NEVER seen a helpful or intelligent reply from anyone claiming to represent Microsoft on these forums. Their phone support is even worse. I've been kept on hold for an hour only to be told they wouldn't support an issue relating to hyper-v without charging $500. It's almost like they use support agents to dissuade people from seeking support. You can say Windows Update won't work (because it breaks frequently) and their first suggestion will be to see if running Windows Update resolves your issue. I know dominatrixes that cannot inflict the same kind of pain as the perpetually oblivious rank and file of Microsoft "support".

    2019年4月10日 18:33
  • same issue here,  we have installed frish windows server 2019  with the lates update  on both Dell and HP G10 servers and we keep notice the hyper-v state stuck on stopping and when the main server is remoted the server get stuck on rebot or shotdown .

    shutting down service:  Hyper-V Virtual Machine Management.

    April 9, 2019—KB4493509 (OS Build 17763.437)

    has been installed

    Please advise


    PJ Moka

    2019年4月11日 9:22
  • Well, Christmas passed for quit some time. And now we celebrated Easter already and Pentecost is coming closer. I hope you decide to fix this bug before the Lord returns?

    I set up a new one-Hyper-V-Host environment with DC, SQL, Application Server and WSUS and was wondering about this Event ID 41 that the system was not shutting down properly. I used the most recent March ISOs to install everything because I thought I would handle with wisdom to wait some time before using this thing after I ignored the 2016 Server-mess.
    So, yes, I also can see this error; and I must say it is shocking to see this quality of development. To be honest it is somehow a shame... really. And it makes me sad.
    And I was wondering why the servers where shutting down so fast (I only have Server Core) when I press the shut down button on the VM-Connect window. Ha, no I know :D

    Off topic: In addition to that I noticed that the systems with 2019 don't boot anymore after I turned on the secure lunch or however it is called. It instantly boots in the repair mode - no chance; I needed to recover the machine from a backup.
    Real fun today with the operating system.



    2019年5月1日 19:38
  • This is insane! Microsoft must not be aware of this problem. I do not know how it hasn't became a much bigger deal over these last 5 months. This is something that should never had made it out of beta and into production. Does anyone know of any better way to get Microsoft to recognize this issue/bug?
    2019年5月8日 14:43
  • This is crazy, I've just migrated and virtulised everything with Server 2019, fingers crossed this is addressed soon.
    2019年5月9日 11:45
  • I regret to inform everyone that cumulative update KB4494441 released on Patch Tuesday 5/14/2019 does not resolve this issue.

    Microsoft, this is unacceptable.  It has been at least five months now.

    Virtual Machine guests should be able to be shut down by the hyper-v host normally.

    Where can we submit this bug through official channels.  Because this thread does not appear to be getting the job done (despite all information necessary to document, reproduce, and investigate the issue being present since day one, in the original post).

    --B

    2019年5月14日 18:28
  • I wanted to confirm that the (ignored) issue still persist. 
    2019年5月14日 19:05
  • Yes same thing here also... waiting for the fix
    2019年5月16日 11:53
  • +1 - yet another user experiencing this bug.

    A few pieces of info in case somebody at Microsoft who can fix this stumbles upon this thread:

    - My host is Server Standard 2019 fully updated, including the May cumulative patches

    - My VMs are all Server Standard 2019 fully updated, including the May cumulative patches

    - I have 2 VMs: My DBServer VM is set to "Always Start" and "Save" for the Stop action. My DC VM is set to "Always Start" and "Shutdown" for the Stop action.

    - When my host reboots due to Windows Updates or just via the Reboot UI, my DBServer VM seems to have successfully saved its state but my DC VM seems to have been powered off rather than shutdown. I tell this by the existence (or non-existence) of Event ID 41 in the VM.

    - If I use the Hyper-V Manager to shut down the DC VM, it shuts down successfully. Just not when the host itself shuts down.

    2019年5月16日 16:26
  • A fun fact:

    I am used to set my guest Systems to allways shutdown if there is a database on it to be sure that the database won't be damaged through the saved state. And now? The system is just turned off with a database on it. :D

    In the current state my database is more secure using the save state. Great. I have doubts that anyone, who is responsible to decide, whether a bug is critical or not, is failing in seeing how critical this bug is!

    2019年5月17日 8:13
  • +1 here. In my case it's a Windows 10 developer machine running Hyper-V. Automatic windows updates were restarting the host and the VM was not gracefully shutdown. I've disabled the automatic updates on the host via editing the registry but the behaviour (not waiting for the VM's to shut down) is appalling.

    @Microsoft: please fix this issue ASAP!

    2019年5月20日 6:55
  • Hi 

    Using Hyper-V manager to stop the VM-s works.

    But still funny way to patch the VM-s:

    1 installing the updates
    2 stop the VM via Hyper-V manager

    Still better way as hardresetting the hosts after "stopping critical" with unkillable VM processes.

    Hope dies last (waiting for the fix)

    2019年5月25日 13:22
  • It's unbelievable that this issue has not been fixed.  I guess Microsoft doesn't see virtualization as market segment worth supporting ¯\_(ツ)_/¯. 

    The company I work for decided to go with vmware as their virtualization platform. The CTO was using this issue and it's lack of attention and an example of why Windows Server is not suitable for a production environment.  At this point I can't disagree with the CTO's assessment.

    2019年5月30日 0:58
  • What the HELL is Microsoft thinking!!!!

    Enterprise grade products? Yeah RIGHT. 

    Biggest bug I've seen from MS in a LONG time. This has screwed up Domain Controllers, Exchange servers and I hope that is all. Very worrisome that this is "status quo" for MS these days.

    2019年6月12日 6:20
  • There is no excuse for the way Microsoft has handled this problem, but VMware might not be much better for you. 

    There have been several data VMware data corruption bugs over the last year or two.

    Here is one example:

    https://kb.vmware.com/s/article/59216

    2019年6月13日 16:34
  • How on earth is this still not fixed!? I was planing to upgrade all Hosts to 2019, and i find this huge problem.
    As DCs and Database Servers cannot use the "save state" option, there is no way to run them safely under this OS.
    Worse: i even readed on the net that it also affects 2016!? Is that true!?
    Very dissapointing. How can we trust Hyper-V if such a huge problem is unresolved for more than half a year, and counting!?
    With all the hype on the Cloud, how can Microsoft afford to have such a problem on their hypervisor, and not care to fix it? Does this affect Azure?

    2019年6月21日 15:01
  • Unbelievable that this is still an issue after so many years - I thought it was something I was doing, but my fresh Windows 2019 Core server running Hyper-V does this and it's completely up-to-date.

    Come on Microsoft.

    2019年6月28日 8:40
  • I opened a premier support request on this.  It took them several weeks to reproduce it because they had limited access to physical servers (seems like that should be improved for Hyper-V issues).  The bottom line is I was told they would fix this in the August update.
    • 已建议为答案 simdoc 2019年7月1日 14:29
    2019年7月1日 14:29
  • I opened a premier support request on this.  It took them several weeks to reproduce it because they had limited access to physical servers (seems like that should be improved for Hyper-V issues).  The bottom line is I was told they would fix this in the August update.
    Thank you for helping all of us here as you managed to get Microsoft to acknowledge and rectify this issue. We'll wait for the August update. 
    2019年7月3日 10:38
  • We just converted to Hyper-V 3 months ago and are having this exact issue on Server 2016 with Hyper-V. Has anyone been able to confirm is this also affects 2016?
    2019年7月3日 18:31
  • A fix for this issue Host shutdowns unexpectedly turns VMs off when configured to shutdown on a WS 2019 host is planned to release in September 2019 update package for Windows Server 2019.

    • 已编辑 Nicolas Rojas 2019年7月4日 15:13 now I have the correct information
    2019年7月3日 21:10
  • Thanks for the update Nicolas - This major issue has been affecting us for way too long.  I can also confirm, which should be included in this bug - is an issue with Hyper-V starting machines which have a delayed startup time.

    For example, if a machine has a startup delay of 1-X seconds, the machine does not start.  Only the machines that have a time of 0 will startup.

    Are you able to provide any comments on this, and if it will also be fixed?

    Thanks,

    DP



    2019年7月4日 21:16
  • It took them several weeks to reproduce it because they had limited access to physical servers

    Thanks for bringing attention to the problem and helping to resolve it.  I have to say, though, that this excuse from MS that was passed along does not pass the sniff test.  Reproducing this issue did not require "physical servers". . . any rudimentary desktop laying around the office could have been pressed into service, Hyper-V enabled, and the problem reproduced in an hour.

    This really does honestly make me worry about Hyper-V and MS as a whole going forward.  Something this serious, so widespread, and so easily reproduced. . . takes this long to be resolved?  It's just astounding.

    2019年7月6日 7:05
  • I've just had this confirmed by the ticket I submitted last week over this:

    It took a while for us to get back to you and update you regarding the same.The issue that you have been facing has already been reported and acknowledged by the product team and they are working on the fix. 

    The tentative date of release of the fix as of now is the 3rd week of Sept 2019. However, this is only tentative and may get revised. 

    As of now there is no test fix available. 

    If any changes, we will provide you the update. Let us know if any concerns.


    2019年7月12日 11:06
  • I also can confirm 3rd week of Sept.  When they told me August in my support case, they meant internally not externally.

    It should not take so long to fix a major problem.  This product is unusable in its current state as a Hyper-V host system.

    2019年7月13日 16:11
  • Thanks for the update Nicolas - This major issue has been affecting us for way too long.  I can also confirm, which should be included in this bug - is an issue with Hyper-V starting machines which have a delayed startup time.

    For example, if a machine has a startup delay of 1-X seconds, the machine does not start.  Only the machines that have a time of 0 will startup.

    Are you able to provide any comments on this, and if it will also be fixed?

    Thanks,

    DP



    I also found this problem on all 2016 and 2019 hyper-v hosts, but only for the 5.0 version vm. After the conversion to a higher version the problem of failed start delayed vm disappears.
    2019年7月16日 8:21
  • Can anyone else confirm this works?  Too much work to try this out.

    Thanks

    Tim

    2019年7月18日 20:52
  • For those with HypeV host shutdown problem:

    If you have 2019 Hyper V servers you can install this service on them

    https://github.com/platformcoders/vmmshutfix

    and set machines to "Save"  to not have Hyper V freak out on them.  This will get you rolling until there is a fix. This service sends preshutdown notification from Host OS to VM's, that way critical services will start shutting down before the Hyper V saves or turns them off.  You can compile it with free Visual Studio community downloaded from Microsoft.

    If you want to test this code but you dont have 2019 HyperV lab  you can use Self-paced lab for 2019 Software Defined Networking Microsoft has over here: https://www.microsoft.com/handsonlabs/SelfPacedLabs



    2019年8月8日 15:15
  • Hello,

    I cannot believe this is an issue with WS2019 too. We have just migrated our entire production environment (approx 4000 servers) from 2008 R2 to WS2016 and ever since, patch days have been a nightmare. The bug we have discovered in Windows 2016 is a bit different. Once the Hyper-V host is rebooted, if there are any patches pending for installation, the VMMS service will gracefully shut down the VMs then will be stopped and while Windows will start processing the updates, VMMS service suddenly will re-start and also starting the VMs at the same time. Once the host completes loading the patches and finally reboots it will kill the VMs which are now running because VMMS has re-started itself. This has caused multiple issues with DCs and database servers becoming corrupted and resulting in data loss. This is not acceptable for a production environment.


    • 已编辑 GeoBog 2019年9月2日 10:30
    2019年9月2日 10:30
  • I also can confirm 3rd week of Sept.  When they told me August in my support case, they meant internally not externally.

    It should not take so long to fix a major problem.  This product is unusable in its current state as a Hyper-V host system.

    was this fixed today???
    2019年9月10日 19:16
  • I verified this issue.
    But unfortunately it has not been solved. It's the worst.
    2019年9月11日 3:52
  • Does anyone think about Energy-Options on Hyper-V Server 2019? Like:

    powercfg /l
    
    powercfg /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c
    
    powercfg /q
    
    powercfg /setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 4f971e89-eebd-4455-a8de-9e59040e7347 5ca83367-6e45-459f-a27b-476b1d01c936 000
    
    powercfg /setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 4f971e89-eebd-4455-a8de-9e59040e7347 5ca83367-6e45-459f-a27b-476b1d01c936 000
    
    powercfg /setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 4f971e89-eebd-4455-a8de-9e59040e7347 96996bc0-ad50-47ec-923b-6f41874dd9eb 000
    
    powercfg /setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 4f971e89-eebd-4455-a8de-9e59040e7347 96996bc0-ad50-47ec-923b-6f41874dd9eb 000
    
    powercfg /setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 4f971e89-eebd-4455-a8de-9e59040e7347 7648efa3-dd9c-4e3e-b566-50f929386280 003
    
    powercfg /setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 4f971e89-eebd-4455-a8de-9e59040e7347 7648efa3-dd9c-4e3e-b566-50f929386280 003
    
    powercfg /setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 7516b95f-f776-4464-8c53-06167f40cc99 3c0bc021-c8a8-4e07-a973-6b14cbcb2b7e 0
    
    powercfg /setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 7516b95f-f776-4464-8c53-06167f40cc99 3c0bc021-c8a8-4e07-a973-6b14cbcb2b7e 0
    
    powercfg /setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 238c9fa8-0aad-41ed-83f4-97be242c8f20 29f6c1db-86da-48c5-9fdb-f2b67b1f44da 0
    
    powercfg /setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 238c9fa8-0aad-41ed-83f4-97be242c8f20 29f6c1db-86da-48c5-9fdb-f2b67b1f44da 0
    
    Restart

    Cannot test it...

    Would be nice someone can test it?

    Regards

    Alitai

    2019年9月11日 10:54
  • I verified this issue.
    But unfortunately it has not been solved. It's the worst.

    Same here, I just installed the Sept (09-2019) Cumulative Update for Server 2019 and tested it. VM's still reported unclean shutdown.

    2019年9月12日 20:08
  • I've re-opened the case with Microsoft I placed back in July where they said it would be fixed in the September update. Let's see what excuse they give this time.
    2019年9月13日 8:56
  • So the September update has come and gone, yet this issue still exists.
    Does anyone have an open case with Microsoft where we can get a response?

    The issue isn't even listed in the known issues for Windows Server 2019 or 2016 for that matter.

    It's ridiculous that such an issue can exist for so long with almost no acknowledgment from Microsoft.
    We have production environments with automatic updates that are suffering due to this issue.

    2019年9月13日 9:00
  • Tomorrow is the Day. Hopefully
    2019年9月16日 9:00
  • Tomorrow is the Day. Hopefully

    where did you get this information?

    surprise surprise..

    2019年9月16日 11:44
  • Hi  Give a try to the vmmshutfix code from github.  If you want set machines to SAVE. That way machines will get shutdown notifications and in extreme slowness they will save and finish shutdown after host comes back online. You can compile .exe using free version of Visual Studio.   You won't need the vmms hotfix and with "save" option will keep machines safer.
    2019年9月16日 12:22
  • My VMs also forcefully shutdown 50% of times when host restarts, for real MS, how long it takes you to acknowledge and fix such bugs?
    2019年9月17日 12:35
  • Hello,

    Same issue here in France.

    When HYPER-V 2019 restart : VM guest are not shut down properly ( New HP DL380 Gen10 Installed yesterday with last cumulative update )

    Version 5.0 VM guest  configured for delayed starting ( > 0 seconds ) randomly not starting.

    ( I heard if VM config is converted to new version, this issue disappear )

    So many bugs for basic features !!

    Regards

    Cedric Beaumois


    Cedric Beaumois


    • 已编辑 HANSOLO2 2019年9月19日 10:44
    2019年9月19日 10:38
  • I forgot another hyper-v bug.

    Sometimes, ramdomly, VM are not accessibles, when we launch hyper-v 2019 manager, we are stuck on:

    " Connecting to virtual machine manager service ......"

    3 times in one week

    Only way: Reboot server !!

    another bad bug

    Regards

    Cedric Beaumois


    Cedric Beaumois

    2019年9月19日 10:40
  • This bug also seems to affect Windows 10 1903 when used as a Hyper-V host. I thought I just needed to increase my timeout (HKLM\Software\Microsoft\Windows NT\CurrentVersion\Virtualization\ShutdownTimeout) but when I did a test reboot on the host, it shut down instantly, simply pulling the plug on the guest VM.

    Will the "third week of September" fix also apply to Windows 10?

    Also:  is there a KB article where we can track the progress of this fix? Sorry if I missed that above...
    • 已编辑 mcbsys 2019年9月23日 23:32
    2019年9月23日 23:30
  • I like how this is now marked as "answered". It has never been answered.

    An answer would be "Microsoft is quality-testing our fix for this and will release it on X day of Y month"

    Your customers were seeking a fix for your bug IN JANUARY and it is September. This isn't a UI bug or an inconvenience with a simple work-around. Unbelievable.

    2019年9月26日 19:24
  • Agreed. Our Windows Server Standard 2019 core host is running Version 10.0.18362.356 with all updates and still has this issue.

    Alex



    • 已编辑 Jinseng 2019年9月28日 19:16
    2019年9月28日 17:51
  • I've read this thread and can't belive it...
    existing bug since December 2018 and not fixed in 10 months....

    they do not take us seriously.

    I have this issue with 2016 Hosts... are 2012 Hosts also affected?

    timo

    2019年9月29日 18:19
  • This isn't the answer to anything. Why did you marked it as answer?

    A 10 months old CRITICAL bug! Unbelievable!!!

    The only possible answer is to patch the OS to fix the bug, and then announce that it was fixed by that patch.

    Do you understand that Hyper-V 2019 "PULLS THE PLUG" on all VMs set to "shut down the guest OS"? I cannot overstate how BAD that is. Would you pull the power plug of an entire rack full of physical servers?

    Some critical VMs like DCs and Database servers cannot even use the "save" option as a workaround.

    I want to be clear: Hyper-V 2019 is absolutely USELESS as a virtualization platform while this bug exists. That's how SERIOUS it is.

    2019年9月30日 14:47
  • I completely agree that a bug like this shouldn't exist for that long. But i'm actually a little surprised, that you guys treat that like there is no other way to do maintenance on a hyper-v host. Why are you shutting down your VMs? Why not just migrating them to another host? Do you all run single-host environements??
    2019年10月1日 10:36
  • Not every customer can afford, or wants to pay for a multi host environment. We take what we can get.
    My company has automatic maintenance in place on single host environments which are now botched.

    It's ridiculous that a bug of this caliber has existed for so long without official recognition (or a fix) by Microsoft.

    2019年10月1日 11:31
  • Unbelievable, got this from support after re-opening my ticket:

    Thank you for your patience!
    
    As per the latest information, the fix was released along with the 9 D patches. This was the patch released on September 24 2019.

    And after checking the server for what updates were installed they confirmed I was patched.

    So I rebooted.

    The restart was almost instant.

    All five VMs were crashed out.

    Microsoft are a bunch of muppets.

    2019年10月2日 18:41
  • Is there any chance for Microsoft to re-look into this ticket? Like everyone in this thread, we waited but to no avail😢
    2019年10月4日 5:36
  • What are 9D patches?  Did they give you a KB article for the supposed fix?

    Hyper-V 2019 is ABSOLUTELY USELESS until this is fixed!

    2019年10月4日 23:26
  • Anyone tested with the new Security Update (this includes 9 = November and D = Week 4 Patches, which are not available over windows update)?

    October 8, 2019—KB4519338 (OS Build 17763.806)

    • 已编辑 Alitai12 2019年10月9日 13:58
    2019年10月9日 13:54
  • No, still not fixed with KB4519338 !!!!!

    2019年10月9日 20:47
  • 9 is September on my calendar.
    2019年10月11日 19:52
  • What are 9D patches?  Did they give you a KB article for the supposed fix?

    Hyper-V 2019 is ABSOLUTELY USELESS until this is fixed!

    I was told KB4516077 but after reporting back their ineptitude their response was:

    Unfortunately for this particular branch, fix is rescheduled to be released on 10C.

    I got this update after checking internally.

    I will keep a watch on this and update you! Apologize for the inconvenience caused!

    Useless.


    <u5:p></u5:p>

    2019年10月15日 12:11
  • I wanted to chime in we've seen the same behavior.  Fresh Windows 2019 installs with the latest Windows Updates on new Dell servers.  VMs were exported from Windows 2012 Hyper-V server and imported into Windows 2019 Hyper-V server and had their Config Version upgraded to 9.0.  All replicate to an identical equipped and configured server.

    I've had a lot of issues with Windows Server 2019 as a Hyper-V host system being unstable.

    • This issue
    • Some VMs don't start even though automatic start is set if a delay is assigned
    • The main VMM service becomes unresponsive to communications from itself, PowerShell, and Hyper-V Manager remotely requiring a hard power off since the system won't shutdown
    • If a teamed NIC is using LACP and Hyper-V starts before LACP completes negotiation Hyper-V will fail to start some VMs because of a lack of network resources

    Systems Administrator Senior - University of Central Florida

    Windows 2019 has been a hot mess for us.  Of all the issues I listed above back in Feb of this year we're still seeing almost all of them still.  The LACP network one is the only items that has actually been resolved.

    • This issue
    • Some VMs don't start even though automatic start is set if a delay greater than 0 is set
    • The main VMM service becomes unresponsive to communications from itself, PowerShell, and Hyper-V Manager remotely requiring a hard power off since the system won't shutdown (seems to be related to Gen 2 Secure Boot + TPM systems)


    Systems Administrator Senior - University of Central Florida

    2019年10月15日 20:18
  • The changelog of KB4520062 does not list any fixes regarding Hyper-V.
    2019年10月16日 16:10
  • The changelog of KB4520062 does not list any fixes regarding Hyper-V.

    Installed KB4520062 and at first glance, looks like it may be fixed.

    Log from a VM following reboot of 2019 Host which also show shutdown request and processes terminating.

    The last shutdown's success status was true. The last boot's success status was true.


    • 已编辑 Mike_CIT 2019年10月16日 21:26
    2019年10月16日 21:24
  • Have tested KB4520062 on Hyperv-2019 and Server 2019 with HyperV and both shut down the VMs on restart now.

    :)

    2019年10月16日 22:17
  • But, it is fixed afterwards, isn't it?

    1. I install the update on guests and on the host

    2. Then, if I reboot the host, will it shutdown the guest once (because the update needs a reboot) more inproperly?

    Edit:

    The next reboot after I applied the update and restarted was successful.

    2019年10月17日 7:35
  • Hi All,

    I am going to be deploying our second identical Dell R740xd server, again with a fresh install of Server 2019 within the next two weeks

    Thankfully, this affords me some flexibility in testing because the VMs will not yet be in production.

    I will let you all know whether the issue seems to be fixed or not. However, I really wish something was mentioned in the release notes anywhere that addressed the Hyper-V Guest Shutdown bug as being addressed. I don't have the warm and fuzzy feeling about this problem being done and dusted, as evidenced by other posters here who indicated that the problem has RESURFACED in Server 2016 Hyper-V. 

    Either way, the only scenario where I might be shutting down the Hyper-V host without manually (interactively or powershell) shutting down the guests first would be a power failure. And in that case, each host has apcupsd installed, and they all know when the power to the UPS has been lost, and do their thing and shut down in an orderly fashion. The Hyper-V host does the same, but with a wide margin after the guests do.

    Thanks to all for staying with it on this forum. Y'all did the heavy lifting for over a year before I even took delivery of my first 2019-destined hardware.

    Chris


    "Time is an illusion, Lunchtime, doubly so..." - Ford Prefect


    13 小时 10 分钟以前