How to Delay Start of Program Manager For Logon Scripts

Last reviewed: June 13, 1995
Article ID: Q131503

The information in this article applies to:

Microsoft Windows NT Workstation version 3.51
Microsoft Windows NT Server version 3.51

Windows NT version 3.51 allows you to synchronize the logon script and the loading of Program Manager so that Program Manager does not start until the logon script has finished running. This article discusses two methods of delaying the start of Program Manager.

To delay the start of Program Manager, do one of the following:

Modify the user profile. In Windows NT 3.51 User Profile Editor (UPEDIT.EXE), select "Wait For Logon Script To Complete Before Starting Program Manager."

-or-

Modify the registry.
WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.
1. Run Registry Editor (REGEDT32.EXE).
2. From the HKEY_CURRENT_USER subtree, go to the following key:
```
         \SOFTWARE\MICROSOFT\Windows NT\CurrentVersion\Winlogon

   3. Select RunLogonScriptSync.

   4. From the Edit menu, choose DWORD.

   5. Change the Data from 0 (default) to 1. Choose OK.

   6. Quit the Registry Editor.

   7. Log off and log back on.
```

KBCategory: kbusage
KBSubcategory: nthowto
Additional reference words: prodnt 3.51 Profile Logon Startup

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 13, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.