We have several generations of HP ProLiant servers in our environment. We recently upgraded SCCM to 1710 then applied ADK 1709. We have been imaging these servers using the ADK 1703 Boot Image without issue. After upgrading to ADK 1709 and creating new boot images, we are unable to boot to into WinPE on any of our Gen9 servers. After doing the standard diagnostics (testing old, testing new, updating drivers, updating firmware, etc) we found that these servers would still freeze after downloading the boot WIM and get stuck on this screen:
We found a support article from HP that referred to Microsoft KB4055537, which didn’t exist at the time we were troubleshooting and our Microsoft contacts didn’t have any information either.
In the meantime, I posted the issue on the TechNet forums and didn’t get much help until earlier this week when Michael Jakob, who has been a TechNet member since 2014, made his first ever post with the solution. I had given up on the issue and turned it over to our server team who where waiting to hear back from Microsoft. As soon as I got the email alert from Technet, I forwarded the info over to the server guys who tested and verified it was indeed the solution.
HP’s initial support article had the correct KB KB055537, but they were about a week early on the release date. Even now, when I use Google or Bing to search for ‘KB4055537’, I only get the HP article referencing it and a handful of TechNet posts including my original and this one which led me to the right info. If you search for ‘Microsoft 4055537’, you can find it (KB4055537 isn’t listed anywhere in the keywords or link, so it’s not getting matched) - Lesson Learned.
The fix for this issue is included in KB 4056892. Search for 2018-01 Cumulative Update for Windows Server 2016 (1709) for x64-based Systems (KB4056892) from Microsoft Update Catalog website to download the rollup.
- From the ‘Deployment and Imaging Tools Environment’, you will need too mount your boot WIM and apply the update using DISM.
- Go to your WIM source directory and check the date stamp to ensure that it was updated.
- Redistribute your boot WIM and test with a Gen9 server.
So, there you have it, a very long winded way to tell you to just use DISM to apply a hotfix. Enjoy.