KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q180122: After Changing the Time, Windows NT May Skip a Day

Article: Q180122
Product(s): Microsoft Windows NT
Version(s): winnt:4.0
Operating System(s): 
Keyword(s): kbYear2000 kbWinNT400sp4fix
Last Modified: 16-MAY-2002

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Windows NT Server version 4.0 
- Microsoft Windows NT Workstation version 4.0 
- Microsoft Windows NT Server, Enterprise Edition version 4.0 
- Microsoft Windows NT Server version 4.0, Terminal Server Edition 
-------------------------------------------------------------------------------

SYMPTOMS
========

After performing the following steps, Windows NT may skip a day:

1. In Control Panel, double-click Date/Time.

2. Set the time to 11:59:55 PM.

3. Set the date to anything (for example, July 1, 1998).

4. Click Apply.

5. Perform the following three actions in 5 seconds:

  a. Set the year to 1999.

  b. Set the month to 7.

  c. Set the day to 1.

6. Set the clock to 11:59:55 PM and then click Apply. After 5 seconds, the clock
  advances to 7/3/1999 rather than 7/2/1999.


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,
please see the following article in the Microsoft Knowledge Base:

  Q152734 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

  ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP3/y2k2-fix/

STATUS
======

Microsoft has confirmed this to be 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
================

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

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

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

  Q183125 Shell Doc Property Dialog Custom Date Incorrect after Year 2000

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

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

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

  Q193056 Problems in Date/Time after Choosing February 29 in a Leap Year

  Q193434 Migration Changes NetWare Accounts Expiration Date

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

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

  Q216916 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:

  Q196548 Y2K Update for Windows NT 4.0, Terminal Server Edition

Additional query words: 4.00

======================================================================
Keywords          : kbYear2000 kbWinNT400sp4fix 
Technology        : kbWinNTsearch kbWinNTWsearch kbWinNTW400 kbWinNTW400search kbWinNT400search kbWinNTSsearch kbWinNTSEntSearch kbWinNTSEnt400 kbWinNTS400search kbWinNTS400 kbNTTermServ400 kbNTTermServSearch
Version           : winnt:4.0
Hardware          : ALPHA x86
Issue type        : kbbug
Solution Type     : kbfix

=============================================================================

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.