Is there anything I can do to streamline that portion of the boot? I found there was some stuff you can do in the Group Policy editor run gpedit.
This will show you what's going on during the boot. In my case, I seem to have some sort of install trying to run and failing. I end up getting a "Windows Installer" help window popping up a window with the Command-Line Options. When I click on the Okay button, the rest of the startup continues. I'm thinking that someone added an install to my workstation's AD group, and its parameters are broken. I see this message when my computer-specific group policy settings are being applied.
Some domains have really complicated policies, and may make this process take a long time. Also, some policies may require network access. In that case, if your computer has no network access, this may prolong the startup process too. It is quite common for this problem to be DNS related. Make sure the clients DNS settings are correct.
If you are on an active directory domain make sure your primary DNS server is set to the Domain Controller. In addition to GP's, services start at that time, and most importantly, so does the network stack it's a service, of course. If the machine loses connectivity or its NIC , everything breaks.
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. This article provides a solution to an issue where the computer stops responding or the "Applying computer settings" screen appears for longer than you expect. When you restart a Windows Server based computer or a Windows Server-based computer, you experience one of the following symptoms:.
During startup, the "Applying computer settings" screen appears, and the computer stops responding. During startup, the "Applying computer settings" screen appears and remains for longer than you expect. During startup, before the logon screen appears, a blue screen that has a blinking pointer appears, and the computer stops responding.
Enter the value as ffffffff. I added DisabledComponents several times. On each reboot the entry had gone and the issue remained. Jep I had the same. But when the server is booted you have to disable IPv6 on your interface and then the problem is over. Since you can get into safe mode, do you see any errors in the event logs correlating to the time frames of when you were booting normally?
Have you tried booting with the network cable unplugged? Errors at this stage are typically group policy related, although the coincidence of new updates is not lost on me. The following article is old, but still relevant for troubleshooting. Is this a domain machine? In many cases, Windows will hang for an unreasonable amount of time during the bootup process trying to locate a domain controller if DNS is unresponsive.
If you're an AD member, double-check that your networking is configured correctly and is responsive, that DNS servers are configured correctly, that all servers are reachable, and that all of your AD SRV records are resolving correctly from the system. Sign up to join this community. The best answers are voted up and rise to the top.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?
0コメント