This article was previously published under Q256320
This article has been archived. It is offered "as is" and will no longer be updated.
Your Windows 2000-based computer may appear to stop responding (hang) if the computer has a local policy that runs a startup script that may require user input. For example, if you have a startup script for "The Local Computer", and the script connects to domain resources and you move the machine to a workgroup, you do not see the dialog box that is requesting logon credentials for the resource. The computer will stay in this condition until you reach the timeout value for group policy scripts, and you receive the following message:
Please Wait Running Startup Scripts
To work around this behavior, wait for the time-out, or restart the computer in safe mode and then edit the group policy.
This behavior is by design.
To remove the startup script:
Click Start, click Run, type gpedit.msc, and then press ENTER.
Double-click Maximum wait time for Group Policy scripts.
Click Enabled. In the Seconds box, type a number from 1 to 32,000 for the number of seconds you want the computer to wait for the set of scripts to finish. To direct the computer to wait until the scripts have finished, no matter how long they take, type 0.
This interval is particularly important when other computer tasks must wait while the scripts complete. By default, each startup script must complete before the next one runs. Also, you can use the "Run logon scripts synchronously" policy to direct the computer to wait for the logon scripts to complete before loading the desktop. An excessively long interval can delay the computer and inconvenience users. However, if the interval is too short, prerequisite tasks might not be done, and the computer can appear to be ready prematurely.