When you add the Windows Sidebar Calendar gadget to the desktop of a Windows Vista-based computer, you may notice that the date displays incorrectly in the Windows Sidebar Calendar gadget.

Note: Although the Windows Sidebar Calendar gadget shows the incorrect date, the system clock still shows the correct date.

This problem will occur if the following conditions are true:

• The computer is set to use a time zone in which the daylight saving time change starts at midnight, such as the (GMT-3:00) Brasilia time zone.
• In the Time Zone Settings dialog box, the Automatically adjust clock for Daylight Saving Time check box is selected.

Consider the following scenario. You create a custom application on a computer that is running Windows Vista or Microsoft Windows Server 2003 with Service Pack (SP1) or a later version. The custom application opens a file on a network share for write access. Additionally, the custom application uses the WriteFile function to write data to the file. When you run the custom application, you experience the following symptoms:

• The WriteFile function returns an error message.
• The WriteFile function returns a value of 0 (zero) for the lpNumberOfBytesWritten parameter.

You expect that the write operation failed and that no data is written to the file. However, you find that some data is successfully written to the file.

The following is an example of a scenario in which you experience this behavior.

• The custom application opens a file for an unbuffered write operation. The WriteFile function extends the file.

  Note: In certain cases, the write operation may be unbuffered even though the application does not specifically set the FILE_FLAG_NO_BUFFERING flag when the application opens the file. For example, if you open the file for write-only access instead of for read and write access, write operations to the file are unbuffered.

• Part of the write operation fails because the disk is full. However, some disk space is freed on the server. Later parts of the write operation are successfully completed.

In this scenario, the following results occur:

• The file contains blank spaces.
• The WriteFile function returns a “STATUS_DISK_FULL” error message.
• The value of the lpNumberOfBytesWritten parameter is set to 0 (zero).

Consider the following scenario:

• You configure a Data Collector Set on a remote computer that is running a pre-Windows Vista version of Microsoft Windows.
• You are a member of only the Performance Log Users group on a Windows Vista-based computer and on the remote computer.

If you then run the logman query command from the Windows Vista-based computer to query the Data Collector Set on the remote computer, the command runs successfully. However, if you run the logman update command to change the credentials under which the Data Collector Set runs, you receive the following error message:
Error:

Collection already exists.