Preparing to configure windows stuck 2008 r2 Domain Controller

I'd give it some more time, if it is hung at the end of the day at some point the only answer is going to be a hard reboot (I know that sucks)

Do you have other DCs...hopeing the answer is yes.

Thanks

Mike

I just connected to Services from other server and checked the services and noticed Windows Modules Installer trying to stop but it looks hanged. Another service Group Policy Client also not started and all options are greyed out so I cannot force it to start. Rest of services started.

Solved the issue myself and sharing the solution

How you do so can please write the steps ??

Connect the Services from other server and go to properties of Windows Modules Installer and set the 3 attempt as Restart (default is, do nothing). As soon as I set this, computer login screen appeared and logged in and system look fine now.

I just experienced this same problem; while the solution elected in this thread did not help in my scenario, I thought I might at least enumerate the steps to try the solution listed here.

From the second server:
1) Click start, type "run", and press Enter.
2) Type "services.msc" and press Enter.  This will load the Services console.
3) From the top menu bar, click "Actions" and select "Connect to another computer..."
4) Type in the name of your computer (e.g., "\\serverone") and click "OK".  Provided you are  logged in to the second server with an account that has administrative access to the first server (The domain Administrator account works nicely.), the list of services will now display the services available on the target machine.
5) Scroll to the bottom of the list of servers, and locate "Windows Modules Installer" -- double click its entry.  Its Properties box will appear.
6) Click the "Recovery" tab.  On this page, you can configure the actions to take if the service fails.

The author gives these instructions at this point:

set the 3 attempt as Restart (default is, do nothing).

There are three drop-down boxes for "First failure," "Second failure," and "Subsequent failures" -- I believe the author suggests that you change the "Subsequent failures" action to "Restart the Service," like the first and second (The default is "Take No Action.").  Click "OK" to apply the new setting and close the dialog box.

-----

This did not solve the problem for me.  I powered off the machine, and turned it back on.  After some waiting while Windows did its thing, I was eventually presented with the log-on prompt.

Weirdly enough, this worked for me too. I have no idea why.

The server was taking hours to get to a logon prompt and then no apps would run. Restarting brought the "Configuring server" error. And setting all three options to Restart immediately produced a logon prompt.

I had this today

Server 2008 R2 - Hangs 'Preparing to configure Windows. Do not turn off your computer'

Pete