In the comments of my blog post above and its German counterpart , other blog readers confirm this problem. The workaround is, to uninstall the January 11, security update.
Tip: To avoid that the DC restarts too quickly during uninstall, just deactivate the network connection pull the plug or deactivate the network driver. German blog reader MOM20xx had the boot loop even after uninstalling the update and notes that the security-only update KB should also be uninstalled on the domain controllers. He then posted the following dump excerpt.
The process wininit. The system will now shut down and restart. Faulting application name: lsass. So there wininit. I also have another feedback on Facebook that update KB on Windows Server is causing the restart of the AD controllers the AD controller is restarted every 15 minutes.
Boot-Loop on Windows Server On reddit. See also the links below. The error message is that the hypervisor is not running: Hypervisor launch failed; The operating systems boot loader failed with error 0xCBB. This is probably update KB for Server R2 — just as a hint, if there should be problems under Windows Server — Many thanks for this.
We were hours trying to resolve this as our HyperV virtual servers wouldn't start. Eventually came across your site, uninstalled update, rebooted and it now works fine. I wouldn't have worked this out to be honest if it wasn't for your site. Echoing this comment — same behavior, same fix. Thank you very much for this thread! Rollback worked and I avoided a coronary episode. Thank you. Not sure if it's the solution, but I added the registry key below and the server hasn't rebooted for 40 minutes now.
FYI — That key was introduced with a November patch for kerberos security. A later patch will enforce it and key won't do anything. But that was planned for the summer, hopefully MSFT has an actual fix by then. I have 2 DC with r2, the updates did fail during install, so there is nothing to remove.. But still got loops. Need te restore them from backups.. I was desperately searching for hints this morning and couldn't find much until I stumbled upon your post.
Thank you! One tip that helped me is that I could catch the DC before a reboot was triggered about 2 minutes after startup and then stop the Netlogon service. That stopped the rebooting such that I could troubleshoot and uninstall the update. Thanks again! Dave, the net stop netlogon tip saved our bacon. Leave it to Microsoft to release a zero-day DC boot loop to their own customers. We had similar issue this morning with Windows Server DC not R2 that kept going in reboot loop every few minutes of showing the signon screen of Windows.
Why don't you just fire up one of each of your systems, do all of your drivers and updates then create an image that can be applied instead of trying to slipstream everything into the install media?
Cloning a VMDK over to the new system usually takes around 10 minutes, you turn the machine on and you're ready to join the domain etc. I already removed the graphics drivers I'll give it a shot! Big Green Man , I am not.
You may end up spending more time troubleshooting this than manually installing updates and drivers. Microsoft did create "convenience roll ups" so you don't have download like something individual updates. This has nothing to do with your issue, though. Your issue is a technical one, most likely due to a driver as mentioned above. I'm just mentioning licensing so you'll know about a potential issue, in case you ever get audited.
To continue this discussion, please ask a new question. Laplink Software, Inc. Neil Laplink. Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Learn More ». Get answers from your peers along with millions of IT pros who visit Spiceworks. Anyone have any ideas that I may have overlooked?
The installation completed without a hitch. I then proceeded installing my screen reader, Window Eyes, which required a reboot. After the reboot, I started installing the critical Windows updates. I rebooted, and Windows restored itself to a previous good state, by my just accepting the default choices. Then the computer is back working but if I shut down, on reboot I get the Blue Screen of Death BSod is back, and the loop starts again, i. I took off the auto update option, I scandisk, updated drivers, disabled bluetooth devices, disabled sideshow, etc, with no positive results.
I called Microsoft for assisstance and the technician acted as this is not a known issue, but he assured me that he could fix the problem. He took over control of my computer remotely, and did not tell me anything except that the computer was going to check and repair any problems on reboot, and if what he did does not fix the problem, I should call back. The computer rebooted without the BSod, but I shut down to check out if the loop is gone, and it is not!
On reboot the BSOd was back. This is a Dell Dimension XPS with a intel Q processer, 3gb ddr2 memory, which came with Vista home premium 32 bit operating system. Upon Googling this problem, it appears this is a known issue without a solution. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
0コメント