Notifying services that windows is shutting down

In November and also December 2019, Microsoft released a couple of brand-new patches simply favor any other month to patch specific worries in Windows Server 2012. It has actually recently pertained to my attention that these patches seem to break Windows Server 2012 virtual machines! They appear to cause a reboot loop, which cannot be interrupted.

You watching: Notifying services that windows is shutting down

Because this was happening on a fairly large range I didn’t recognize that the reboot loop was bereason of some faulty Windows patches. I figured I would certainly simply inspect the atmosphere to view if anything framework related was leading to the issues. In a reboot loop this is very unmost likely, but hey, since this was happening on even more than one online machine we simply desire to be sure right?

After some troubleshooting it appeared that, the reboot loop was an outcome of patching Windows Server 2012 virtual equipments the incorrect means. Both the November 2019 Servicing Stack Update (SSU) KB4523208 and the December SSU KB4532920 for Windows Server 2012 seem to be resulting in the reboot loops according to some customers on Twitter and Reddit. It seems that these two patches, as through a lot of SSU patches, should be installed exclusively (which Microsoft does point out in the installation procedure). This suggests they have to be set up prior to any kind of various other patches get set up. When you install patches in the environment with WSUS or also unattfinished, the installation sequence will certainly be ignored and also the rollup patch gets installed before the SSU patch, which in this situation renders the online server break. Some have actually sassist that patch KB890830 is additionally responsible for the reboot loop. When you are suffering this concern, the servers store gaining stuck in the following screen:

Stage 2 of 4Preparing to connumber WindowsDo not revolve off your computer

After which the virtual machine will certainly just tell you:

Notifying services that Windows is shutting down.

And it will reboot. So exactly how execute we fix this? Well the resolution is rather basic yet it relies on wbelow you are in the process:

If you haven’t installed the November or December SSU patch, you have the right to proproactively take treatment of the situation by complying with the installation guidelines for the patch. Which means, install these patches prior to the rollup patches. This method you have to be fine.Did you already install the patch and also are you experiencing the issue? Then you will certainly have to boot right into Safe Mode and reboot (twice sometimes). When the VM boots into Safe Setting the installation completes or stops working and you can reboot and usage the digital machine as usual.

However, what do you do as soon as you cannot boot right into Safe Mode? If you are for example utilizing EFI boot, booting right into the Windows “Modern Boot Options” menu is disabled. Some say it is disabled by default in Windows Server 2008 R2 and above to have actually much faster boot times on the VM, also once making use of Legacy BIOS mode. I myself have actually not been able to proof this to be true though. I have done tests on Windows Server 2012, 2012 R2 and also 2016 VM’s with Legacy BIOS allowed and eincredibly time I could hit F8 and also boot into the Windows Cutting edge Boot Options menu.

See more: What Does ' The Exception Breakpoint Has Been Reached Windows 10

So what carry out we should execute to get right into the Windows Cutting edge Boot Options menu once we usage UEFI Boot for our VM’s? Well we deserve to gain into the UEFI Boot Manager by pressing F2 when a VM boots. You will get the UEFI Bios Manager display such as below:


From there on you can carry out all sorts of things, yet you can’t obtain the Windows Cutting edge Boot Options food selection without doing some tricks. Below are three means of entering the Windows Modern Boot Options menu as soon as using UEFI Boot:

Connect the Windows 2012(R2) ISO.Start the VM hit F2 for the UEFI Boot Manager.Run the Virtual CDROM.Choose Use a Device -> UEFI Internal Shell (Unsupported Version).Press F8 on the selected GuestOS for progressed choices.Press Save Mode (via options) and also continue.


Start the VM and push F2 throughout boot.In the UEFI Boot Manager go to “Get in Setup” and pick “Boot from a File”.Choose file with “NO VOLUME LABEL”. Press Get in twice.Go to “Microsoft” and press Enter.Press Enter on “Boot”.Go dvery own to “bootmgfw.efi” and also push Enter.

See more: How To Fix Mac Unable To Connect To Printer Due To An Error, Not Able To Connect To Printer Due To Error


Start the VM and also push F2 in the time of boot.In UEFI Boot Manager go to UEFI Internal Covering (Unsustained Version).Let the shell fill, carry out map -r -b (-b to break after one screen).Choose the fs0 mapping or blk0 mapping by entering fs0: or blk0:.Go into dir or ls to see content of mapping/disk.Go to the “UEFI” folder via cd EFI.Enter dir or ls to check out content of mapping/disk. Do cd Boot to enter the Boot folder.Execute bootx64.efi by just entering bootx64.efi.Press F8 on the selected GuestOS for progressed choices.Press Save Mode (with options) and proceed.