KB980356

Consider the following scenario:

  • You join a computer that is running Windows Server 2008 or Windows Vista to a Windows Server 2008-based domain.
  • You enable a Group Policy preferences setting that schedules a task to run at a specific time in a Group Policy object (GPO).
  • You apply the GPO to the computer.

In this scenario, an incorrect date for the scheduled task is displayed on the computer. This incorrect date is one day earlier or one day later.

For example, you use the Central Time (US and Canada) time zone and schedule the task to run at the 6:00 PM 12/30/2009 time on the computer. However, the 6:00 PM 12/29/2009 time that is one day earlier is displayed.

KB979535

Consider the following scenario:

  • You have an application that uses a DateTimePicker control.
  • This DateTimePicker control has two properties: MinDate and MaxDate. The month of the MinDate and the MaxDate are not set to the current month.
  • You run the application in a Windows Vista or a Windows Server 2008 environment.

In this scenario, the current date value is set either to the MinDate or to the MaxDate.

For example, assume that the current date is January 26, 2010. You add two DateTimePicker controls to a Microsoft Windows Forms application.

For control 1, you set the MinDate and the MaxDate properties as follows:

  • Me.DateTimePicker1.MinDate as 2009/12/01
  • Me.DateTimePicker1.MaxDate as 2009/12/30
  • Me.DateTimePicker1.Value as 2010/01/26

You select any dates on this DateTimePicker control. When you click this DateTimePicker control again, the current date is set to the value of the MaxDate.

For control 2, you set the MinDate and the MaxDate properties as follows:

  • Me.DateTimePicker2.MinDate as 2009/02/01
  • Me.DateTimePicker2.MaxDate as 2009/02/28
  • Me.DateTimePicker2.Value as 2010/01/26

You select any dates on this DateTimePicker control. In this example, when you click the DateTimePicker control again, the current date is set to the value of the MinDate.

KB976470

The Date and Time window in Control Panel may display the following error message:

Daylight Saving Time ends on [Date out of range] at 0:00. The clock is not set to adjust for this change.

KB967920

On a Microsoft Windows Vista-based computer using the HotStart button, if the system clock is reset to the time before the system was started, or to the time before the HotStart button was last used, the program may not be started even if the HotStart button is pressed.

Note that this behavior does not occur if the date or the time is changed on the Time Zone tab.

KB967666

After you sync a file in Windows Vista or in Windows Server 2008, the Date Modified time for the destination file may be updated to the current time. This behavior may cause a re-sync of the file attributes and may cause the Windows Search service to re-index the whole file.

For example, you click Always Available Offline to pin a network folder in Windows Vista. You visit the folder, and then create a file in the folder. You select Work Offline for the folder, and then replace the file. When you sync the file, the file is synced from the client to the server correctly. However, when you sync the file again, the file is synced from the server to the client again, even though no content changed during this period.

KB933812

Consider the following scenario. You take the following actions on a computer that is running Microsoft Windows XP or Microsoft Windows Server 2003:

  1. You install the 2007 time zone update for Microsoft Windows operating systems that is documented in the following Microsoft Knowledge Base article:
    928388 2007 time zone update for Microsoft Windows operating systems
  2. You install the C run-time (CRT) update that is documented in the following Microsoft Knowledge Base article:
    932590 FIX: Windows-based applications that use the TZ environment variable may not work as expected because of changes to DST
  3. You set the TZ environment variable.

In this scenario, when you create a custom application that uses the JScript version 5.7 Date object, the time is reported incorrectly for dates that are between the second Sunday in March and the first Sunday in April for the year 2007. Instead of the time being reported in daylight saving time, the time is reported in standard time. For example, for March 30, 2007, the JScript Date object reports time in standard time instead of in daylight saving time.

Note: JScript version 5.7 is included with Windows Vista. Additionally, when you install Internet Explorer 7 on a computer that is running Windows XP with Service Pack 2 (SP2), Windows XP Professional x64 Edition, or Windows Server 2003 SP1, JScript version 5.7 is installed.

KB942532

Consider the following scenario:

  • You download a compressed (zip) file from the Internet to a computer that is running one of the following operating systems:
    • Windows Vista
    • Windows Server 2003 Service Pack 1
    • Windows Server 2003 Service Pack 2
    • Windows XP Service Pack 2
  • You save this file to a disk that is formatted by using the NTFS file system.
  • You extract the files from the compressed file by using the Extract All Files wizard.

In this scenario, the modified date of the extracted files changes to the date that you extracted the files.

Note: This problem does not occur when you use a third-party tool, such as WinZip, to extract the files.

KB938454

Consider the following scenario. You have a domain on which user accounts reside and another domain on which computer accounts reside. You have established a trust relationship between these domains. However, when you try to log on to a Windows Vista-based client computer across the trust, the logon process fails. Additionally, you receive an error message that contains a white “X� inside a red circle. The text of this error message resembles the following:

There is a time and/or date difference between the client and server.

Note: This issue occurs even though there is no significant time difference between the client computer and the server. This issue occurs only on Windows Vista-based client computers.