DOCUMENT:Q216913 TITLE :BIOS Date Value Does Not Immediately Update on January 1, 2000 PRODUCT :Windows NT PROD/VER:4.0 OPER/SYS:WINDOWS NT KEYWORD :kbbug4.00 kbfix4.00 ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Windows NT Workstation versions 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3, 4.0 SP4, 4.0 SP5 - Microsoft Windows NT Server versions 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3, 4.0 SP4, 4.0 SP5 - Microsoft Windows NT Server, Enterprise Edition versions 4.0, 4.0 SP4, 4.0 SP5 - Microsoft Windows NT Server versions 4.0, 4.0 SP4, Terminal Server Edition ------------------------------------------------------------------------------- SYMPTOMS ======== Windows NT 4.0 Service Pack 5 addresses the following problem in Windows NT 4.0: When the Windows 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. 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 issue may cause unexpected behavior under two conditions: - When your computer is configured using the dual boot option where another operating system may not handle this situation properly. All versions of MS-DOS fall into this category. - Some computer hardware BIOS configurations detect this behavior as an invalid date and present a query for the correct date. This may prevent a computer from restarting without user input. NOTE: This problem only occurs if the computer is restarted during the time lapse when the dates were out of synch. On August 5, 1999, Microsoft released an updated version of BIOS-fix (BIOS2-fix) that was originally included with Windows NT 4.0 Service Pack 5. In addition to the above, the latest version of this update corrects the following problems: - If a computer is set to a time zone which does not participate in Daylight Saving Time, refreshing the real time clock for the Year 2000 does not work. - The original update did not replace the multi-processor kernel if it existed. The updated version does. On November 3, 1999, Microsoft released an updated version of BIOS-fix (Microsoft BIOS3 Y2K Update) that, in addition to fixing the above, fixes the problems listed below: - In rare cirumstances where the real time clock is slightly behind the system clock, refreshing the real time clock for the Year 2000 may not work. - Q241040 Daylight Saving Time Change Not Applied Immediately RESOLUTION ========== Windows NT 4.0 -------------- To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to: - http://www.microsoft.com/windows/servicepacks/ -or- - Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web: http://www.microsoft.com/support/supportnet/overview/overview.asp For your convenience, a supported software update that corrects this problem is also available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you install the latest Windows NT service pack that contains this software update. If you are running Windows NT 4.0 Service Pack 6: The Microsoft BIOS3 Y2K Update is installed as part of Windows NT 4.0 Service Pack 6. If you are running Windows NT 4.0 Service Pack 4 or 5: The following files are available for download from the Microsoft Download Center or Microsoft's FTP site. Click the file names below to download the appropriate file: x86: Microsoft Download Center: Biosfixi.exe (http://download.microsoft.com/download/winntsrv40/Update/3/NT4/EN-US/Biosfixi.exe) FTP: Biosfixi.exe (ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP5/Y2K/BIOS3-fix/Biosfixi.exe) Alpha: Microsoft Download Center: Biosfixa.exe (http://download.microsoft.com/download/winntsrv40/Update/3/ALPHA/EN-US/Biosfixa.exe) FTP: Biosfixa.exe (ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP5/Y2K/BIOS3-fix/Biosfixa.exe) For more information about how to download files from the Microsoft Download Center, please visit the Download Center at the following Web address http://www.microsoft.com/downloads/search.asp and then click "How to use the Microsoft Download Center". WINDOWS NT SERVER 4.0, TERMINAL SERVER EDITION A supported software update that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT Server 4.0, Terminal Server Edition service pack that contains this software update. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the software update. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web: http://www.microsoft.com/support/supportnet/overview/overview.asp This software update has been posted to the following Internet location as Biosfixi.exe (x86) and Biosfixa.exe (Alpha): ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40tse/hotfixes-postSP4/Y2K/BIOS3-fix/ To determine if a localized version of this software update is available, change "USA" in the URL above to the appropriate localized abbreviation. Click here (ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/readme.txt) for a list of these abbreviations. STATUS ====== WINDOWS NT 4.0 Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5. WINDOWS NT SERVER 4.0, TERMINAL SERVER EDITION Microsoft has confirmed this to be a problem in Windows NT Server 4.0, Terminal Server Edition. Additional query words: y2k tse wts ============================================================================ 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.