There are new Year 2000 updates that have been delivered after SP5 was released.
Post SP5 Updates:
1. BIOS Date Value does not Immediately Update on January 1, 2000. (Q216913)
When the Window NT System Time value rolls over from the year æ1999Æ to æ2000Æ, the Century Byte value stored in the real time clock (RTC) is not changed until up to one hour later when the time daemon writes out the date. Customers should evaluate their exposure to this issue to determine whether to apply this update. This issue only affects systems with older BIOSes that do not automatically update the century byte on reboot (Contact your hardware manufacturer for BIOS details). This fix was originally included in SP5 but it has been re-released in July 1999 to address additional issues. Please consult the KB article for details.
2. NNTP Service Converts Two-Digit Years Incorrectly (Q238020)
When a messaging client application attempts to post a message to an News Network Transfer Protocol (NNTP) server using a 2-digit year, the fact that the two-digit year is converted incorrectly may cause an error message to be displayed. Microsoft is not aware of any messaging clients that post messages using 2-digit dates. The NNTP server was shipped with Internet Information Server as part of the Windows NT Option Pack and with MCIS 2.0.
3. NET USER /TIME Command does not work in Year 2000 (Q240195).
The /TIMES function can be used to set the valid logon times of Windows NT user accounts via the command line utility NET USER. The Y2K issue causes the /TIMES function to cease functioning in years 2000 or greater. The User Manager GUI application is not affected and can be used to effectively set account valid logon times in the year 2000 and beyond.
These updates are availble on this CD in the following directories:
