No Password Expiration Notice Is Presented During the Logon Process

Support for Windows XP has ended

Microsoft ended support for Windows XP on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article was previously published under Q313194
This article has been archived. It is offered "as is" and will no longer be updated.
Windows XP may not display a notice to a user that the user's password is about to expire. This problem may occur if the user logs on to a Microsoft Windows 2000-based domain from a Windows XP Professional-based computer on which the user has previously logged on, and the user's password will expire in the specified expiry period.
The following policy determines whether Windows XP waits for the network during startup and the user logon process:
Computer Configuration\Administrative Templates\System\Logon: Always wait for the network at computer startup and logon
By default, Windows XP does not wait for the network to be fully initialized during startup and the logon process. Existing users are logged on by using cached credentials. This results in shorter times for the logon process. Group Policy is applied in the background after the network becomes available.

Because this is a background refresh, extensions such as Software Installation and Folder Redirection take two logon processes to apply the changes. To be able to operate safely, these extensions require that no users be logged on. Therefore, these extensions must be processed in the foreground before users are actively using the computer. Additionally, changes that are made to the user object, such as adding a roaming profile path, home folder, or user object logon script, may take up to two logon processes to be detected.

If a user with a roaming profile, home folder, or user object logon script logs on to a computer, Windows XP always waits for the network to be initialized before logging the user on. If a user has not logged on to the computer before, Windows XP always waits for the network to be initialized.

If you turn on the setting that is listed earlier in this article, logon processing is performed in the same way as for Windows 2000-based clients. Windows XP waits for the network to be fully initialized before users are logged on. Group Policy is applied synchronously in the foreground.

If you turn off or do not configure the setting, Windows XP does not wait for the network to be fully initialized and users are logged on with cached credentials. Group Policy is applied asynchronously in the background.

If you want Folder Redirection, Software Installation, or roaming user profile settings to be applied with only one logon process, turn on the setting to make sure that Windows XP waits for the network to be available before applying the policy.

Note that for servers, the startup and logon processing always behaves as if this policy setting were on.
To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
322389 How to Obtain the Latest Windows XP Service Pack
The English version of this fix should have the following file attributes or later:
   Date        Time    Version       Size     File name   -----------------------------------------------------   2-28-2002   16:11   5.1.2600.31   968192   Msgina.dll				

To work around this problem, turn on the following group policy:
Computer\Administrative Templates\System\logon\Always wait for the network at computer startup and logon
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows XP Service Pack 1.

Article ID: 313194 - Last Review: 12/07/2015 08:12:57 - Revision: 1.2

Microsoft Windows XP Professional

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbsetup kbwinxpsp1fix KB313194