Problems in Date/Time after Choosing February 29 in a Leap Year (193056)



The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition
  • Microsoft Windows NT Workstation 4.0
  • Microsoft Windows NT Server 4.0
  • Microsoft Windows NT Server, Enterprise Edition 4.0

This article was previously published under Q193056

SYMPTOMS

If you use the Date/Time tool in Control Panel to select February 29th in any leap year, you may experience any of the following symptoms:

Symptom 1

When you view any other year in the Date/Time tool, February 29th may be visible, even for non-leap years.

Symptom 2

If you change to another year in the Date/Time tool, and click Apply or OK, and move your mouse pointer over, the clock on the taskbar may display the last leap year you chose.

Symptom 3

If you select another year under Date in the Date/Time tool, you may then be unable to select the original leap year.

RESOLUTION

Windows NT 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack


The English version of this post-SP3 hotfix has been posted to the following Internet locations.

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

MORE INFORMATION

These problems also occur in Windows 95 and Windows 98. For more information, please see the following article in the Microsoft Knowledge Base:

182627 Problems in Date/Time After Choosing February 29 in a Leap Year

For more information on what is fixed in Y2K2-fix, please see the following articles in the Microsoft Knowledge Base:

175093 User Manager Does Not Recognize February 2000 As a Leap Year

180122 After Changing the Time, Windows NT May Skip a Day

183123 Find Files Displays Garbled Date if Year is 2000 or Greater

183125 Shell Doc Property Dialog Custom Date Incorrect after Year 2000

184132 Err Msg: Value Entered Does Not Match with the Specified Type

186669 FPNW Logout.exe Incorrectly Reports Year After Jan. 1, 2000

191768 Date of Print Job May Be Displayed Incorrectly in Print Queue

193434 Migration Changes NetWare Accounts Expiration Date

194726 FPNW Client Does Not Get Correct Time or Date After Y2K

207799 IBM PS/1 will not Boot on or After January 1, 2000

216916 NTBACKUP Writes Incorrect Year to Log File

Windows NT Server 4.0, Terminal Server Edition

For information on the Y2K2-fix for Windows NT 4.0, Terminal Server Edition, please see the following article in the Microsoft Knowledge Base:

196548 Y2K Update for Windows NT 4.0, Terminal Server Edition


Modification Type:MajorLast Reviewed:6/28/2004
Keywords:kbbug kbfix kbQFE KB193056