What's happening in windows when you boot it and it gets to the portion that displays the message: Applying Computer Settings?

I seem to get hung up there for a long time. Is there anything I can do to streamline that portion of the boot?

I've made some progress on this.

I found there was some stuff you can do in the Group Policy editor (run gpedit.msc) to see what's going on.

If you got to Console Root->Computer Configuration->Administrative Templates->System, you can update Verbose vs normal status messages to Enabled. You can also go to Console Root->Computer Configuration->Administrative Templates->System->Scripts and Enable run startup scripts visible. 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'm thinking about changing the Maximum wait time for Group Policy scripts (also in Console Root->Computer Configuration->Administrative Templates->System->Scripts) from the default (which is 600 seconds) to something much smaller like 180 seconds.

  • At my school it takes a good 3 minutes on that part for every windows login.
    – Flame
    Apr 30, 2009 at 17:21

5 Answers 5


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.

  • +1 and accepted. Note: I was able to see better what was going on by turning on "Verbose vs normal status messages" and "Enable run startup scripts visible" in the Group Policy editor
    – BIBD
    Jun 23, 2009 at 19:24

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.

[Edit] See this link for further details on whats happening during this process and what problems can occur.


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. This will present itself as a hung machine (which will respond, eventually, after 20 minutes.) This will for sure affect GP's. As others have said, GP's depend on a healthy network and DNS so troubleshoot that first.

On the other hand don't panic: It's normal for servers and domain controllers to take more time in this phase; SBS is famous for "slow" boot and shutdown times, but they're normal and there's nothing wrong.


If you can log on with a local account rather than a domain account and don't have the problem, it is likely related to group policies being applied as others have mentioned. Do you use roaming profiles?


Another possibility that we run into all the time is a software installation ran by a GP that is failing. Often this software will attempt to install each time the computer is booted.

If you look in the Event viewer you will see any errors relating to this and usually a fix can be found. In our case often a previous installation is failing causing the GP policy installation to time-out. Once we correct the issue, or do a full uninstall of the previous version, allows the software to install correctly and the delay goes away.

Hope that helps!

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.