When Windows Server 2012 R2 hangs on boot after update and shows errors like “ We couldn’t complete the updates. Run DISM command to revert pending updates In the System Recovery Options window, choose “Command Prompt”.Īfter entering Command Prompt, you can try one or more measures presented in the following text based on your own situations. Choose "Repair your computer" and Windows Server 2012 R2. Choose a language to install, time and currency format, keyboard or input methods, and click "Next".Ĥ. Press a key when “Press any key to start from CD or DVD” prompts.ģ. Insert Windows Server 2012 R2 installation CD/DVD into the machine and boot from it by changing boot order in BIOS.Ģ. If boot failure still exists, you may need to access Command Prompt and then revert pending updates, restore system registry, scan system files, rebuild BCD or do something else.ġ.
To fix this issue, you can unplug all peripheral devices, roll back drivers or disable Automatic Restart at first. The reasons for Server 2012 R2 endless boot loop are complicated and different. Five fixes for Windows Server 2012 R2 boot loop
Why does Windows Server 2012 R2 keep rebooting?īefore knowing how to fix Windows Server 2012 machine not booting normally problem, have a look at what can account for it: Whatever the case may be, it is a vexing problem.
It is not rare to encounter Server 2012 boot loop and the specific situation of boot cycle can be widely different: “your machine can run into reboot loop with a “ We couldn’t complete the updates” message after update”, “it may always boot into blue “ Choose an Option” screen”, “it could catch in reboot loop with BSOD like Your PC ran into a Problem, and now restart with an error code”. I’m working with the Azure Stack team to fix that particular issue, possibly checking for token status after the initial VHD upload and refreshing it if expired.Windows Server 2012 R2 stuck in boot loop In that case, you can manually add the image and create the gallery item. Occasionally the token for uploading the VHD and creating the Gallery Item will time out. I picked the SU1Fileserver share as a target since it should have ample space, but your mileage may vary. Minimum Viable Product right? Lastly, the image is a whopping 128GB in size, so be congizant of that when you select a destination location for the VHD. I am looking into turning this into a proper script that can take some arguments and do the whole thing for you, but that’s not quite ready yet. These commands could easily be repurposed to capture custom VM images using other operating systems too, assuming they support WinRM. The key is to allow WinRM traffic from the public subnet so that the script can remote in and sysprep the server.
The ARM template being used is sitting on my GitHub, but feel free to use whatever template you like. There are a few fields to change here and there and I have added on either side of the text to indicate a necessary change. The commands assume that you have already logged into Azure Cloud and selected the proper subscription. You also need to have a valid subscription in Azure, obviously, in which to spin up the VM. This set of commands is meant to be run from the MAS-CON01 VM, and it assumes that you have installed the proper version of AzureRM PowerShell and the AzureStack tools from Github. That is essentially what the script below does. Then using the Add-VMImage cmdlet in AzureStack.ComputeAdmin I’ll add it to the Azure Stack Install.
So I figured, why not go to the source? I can spin up a Windows Server 2012 R2 Datacenter VM in Azure, sysprep it, and then copy the VHD down locally. So you are on your own when it comes to creating them. But what if you wanted that good ole Server 2012 R2 image?įor whatever reason, VM Images are not yet part of the marketplace syndication.
You are prompted to download a Windows Server 2016 ISO as part of the Azure Stack POC download, and there is a script in the AzureStack.ComputeAdmin module called New-Server2016Image that will take that ISO and turn it into a Core or Datacenter image. With Azure Stack TP3 (original and extra-crispy) there are no default VM Images included in the install. In this post I am going to detail a simple (if slow) way of adding a Server 2012 R2 image to Azure Stack as well. In a previous post I covered how to add a Linux image to Azure Stack.