Windows Server Essentials 2016 – Install Stuck at 17% or 39%
March 10, 2016 8 Comments
This week I had a Skype conversation with a fellow MVP and friend from Brazil, Daniel Santos. He reported an issue he was having installing the Essentials 2016 TP4 OS which was stalling at 17% during the Essentials configuration Wizard.
He also reported that the environment had not changed and that previous TPs had installed correctly.
I volunteered to login to his server and check it out.
His Lab was running on a Windows 10 workstation with Hyper-V.
He was also using a Portuguese language edition of the TP but reported the same issue with the English one, I got him to start over with the English one so I could read it!!
Sure enough at 17% the install, stalled. At this point we had the following logs created in c:\programData\Microsoft\Windows Server\Logs
At 17% the SharedServiceHost-ManagementServiceConfig log shows us that IIS has been installed, and that the AD Binaries are being installed.
What should happen is a reboot should occur, the wizard should push on to 25%, then by 39% DCPromo has completed and the CA is installed.
Daniels server was stuck at 17% even after a manual reboot.
We did a manual DCPromo on the server and installed AD, but again the Essentials wizard was stuck on 17%.
I noticed that the Essentials registry Setup Key had a value for ‘RebootExpected’. and that it was ‘True’. This fit in with what i was expecting in that the server was not registering the fact that it had been rebooted. I decided to change this to False.
As soon as i did that, the Wizard failed, and i was presented with the choice to hit ‘retry’.
After doing that the wizard went through and completed successfully.
We have not had a comment back from Microsoft so far, will update the post when we do!
Daniel has since installed a 2012 R2 Hyper-V Server, and an Essentials 2016 Guest and confirms that has installed correctly. I have installed it on a Bare Metal HP Microserver N40L also without any issue.
Following on with our own research, Daniel and i reproduced the Installation Stall a few more times and Daniel found that starting the Windows Server Essentials Management Service was enough to kick-start the install, without resorting to editing the registry.
The real question to answer now, is what is causing it to stall, but for now at least, we have a workaround!