Froze (for hours) at Applying Security Policy

  • Thread starter Thread starter Stacy
  • Start date Start date
S

Stacy

A system I was recently called to fix is running Windows 2000 Professional.
Upon powering the system on, it freezes at Applying Security Policy every
time. Even after leaving the computer for over an hours, the screen stays
at Applying Security Policy (so I doubt this is a simple DNS issue).

Any ideas?

Thanks!
Skitrees
 
Hi there,

maybe a DNS problem. Try to login locally (>>extended | THIS MACHINE).
This avoids the connection to a domain contoller ("server") and taking
its Security Policies.

- Check, whether this machine is member of the right domain (if you
have any).
- Look after the DNS settings of this computer. At the TCP/IP protocol
of the network device, that connects to the network, the DNS-Server
should be the Domain Contoller (in most cases this "one server"). If
you don't have a Domain Contoller, there should be written the IP of
your router or a public DNS-Server (e.g. from your provider).

Rene
 
In
Stacy said:
A system I was recently called to fix is running Windows 2000
Professional. Upon powering the system on, it freezes at Applying
Security Policy every time. Even after leaving the computer for over
an hours, the screen stays at Applying Security Policy (so I doubt
this is a simple DNS issue).
Any ideas?

Thanks!
Skitrees
Click to expand...


To significantly decrease the time it takes to receive the logon screen:

1. On your Windows 2000 computer, use Regedt32, navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system

2. On the Edit menu, Add (or edit existing) Value name
SynchronousMachineGroupPolicy and toggle the Data type

to REG_DWORD. In the DWORD Editor, set the data value to 0.

3. On the Edit menu, Add (or edit existing) Value name
SynchronousUserGroupPolicy and toggle the Data type to

REG_DWORD. In the DWORD Editor, set the data value to 0.

4. Shutdown and restart your computer.
 
Thanks to everyone for their responses!!

Unfortunately, as I finally gained entry to Windows (after two hours of
waiting - literally). I found the system is simply corrupt somewhere. Even
trying to run explorer from task manager has no effect.

Looks like a reload to me from here.

Thanks again for your time and thoughts.

Stacy
 
Back
Top