Article ID: 193056 - Last Review: November 1, 2006 - Revision: 2.2 Problems in Date/Time after Choosing February 29 in a Leap YearThis article was previously published under Q193056 On This PageSYMPTOMS
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 1When you view any other year in the Date/Time tool, February 29th may be visible, even for non-leap years.Symptom 2If 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 3If you select another year under Date in the Date/Time tool, you may then be unable to select the original leap year.RESOLUTIONWindows NT 4.0To 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
(http://support.microsoft.com/kb/152734/EN-US/
)
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. http://www.microsoft.com/ntserver/nts/downloads/archive/NT4y2kpostSP3/default.asp
(http://www.microsoft.com/ntserver/nts/downloads/archive/NT4y2kpostSP3/default.asp)
ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP3/y2k2-fix/
(ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP3/y2k2-fix/)
STATUSMicrosoft 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
(http://support.microsoft.com/kb/182627/EN-US/
)
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
(http://support.microsoft.com/kb/175093/EN-US/
)
User Manager Does Not Recognize February 2000 As a Leap Year
183123
(http://support.microsoft.com/kb/183123/EN-US/
)
Find Files Displays Garbled Date if Year is 2000 or Greater
183125
(http://support.microsoft.com/kb/183125/EN-US/
)
Shell Doc Property Dialog Custom Date Incorrect after Year 2000
184132
(http://support.microsoft.com/kb/184132/EN-US/
)
Err Msg: Value Entered Does Not Match with the Specified Type
186669
(http://support.microsoft.com/kb/186669/EN-US/
)
FPNW Logout.exe Incorrectly Reports Year After Jan. 1, 2000
191768
(http://support.microsoft.com/kb/191768/EN-US/
)
Date of Print Job May Be Displayed Incorrectly in Print Queue
193434
(http://support.microsoft.com/kb/193434/EN-US/
)
Migration Changes NetWare Accounts Expiration Date
194726
(http://support.microsoft.com/kb/194726/EN-US/
)
FPNW Client Does Not Get Correct Time or Date After Y2K
207799
(http://support.microsoft.com/kb/207799/EN-US/
)
IBM PS/1 will not Boot on or After January 1, 2000
216916
(http://support.microsoft.com/kb/216916/EN-US/
)
NTBACKUP Writes Incorrect Year to Log File
Windows NT Server 4.0, Terminal Server EditionFor information on the Y2K2-fix for Windows NT 4.0, Terminal Server Edition, please see the following article in the Microsoft Knowledge Base:196548
(http://support.microsoft.com/kb/196548/EN-US/
)
Y2K Update for Windows NT 4.0, Terminal Server Edition
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Back to the top
|
