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.

When you try to copy files from a Windows Vista-based computer to another computer by using Windows Explorer, you may receive the following error message:

Out of memory
There is not enough memory to complete this operation.

This problem occurs if the following conditions are true:

• The files include extended attributes.
• You copy lots of files in a single operation.

In Windows Vista, you add the CopyFileBufferedSynchronousIo registry entry to improve the speed of a file copy operation. However, when you use Windows Explorer to copy a file from the Windows Vista-based computer to a computer that is running an older Windows operating system, the file copies only slightly more quickly.

Note: The file copies more quickly if you use a command-line tool to copy the file. You can use command-line tools such as Robocopy.exe and Xcopy.exe to copy the file.:

You transfer a file between a Windows Vista-based client computer and a file server that is running a previous Windows operating system. Then, the Windows Vista-based client stops responding. This problem occurs if the following conditions are true:

• Windows Vista and the file server use the Server Message Block (SMB) 1.0 protocol to transfer the file.
• The network connection between the Windows Vista-based client computer and the file server is lost when you transfer the file. For example, the network cable is unplugged when you transfer the file.

Note: When you transfer a file between a Windows Vista-based client computer and a file server that is running a previous Windows operating system, Windows Vista uses the SMB 1.0 protocol to transfer files.

When you modify an offline file in Windows Vista, the changes are not saved to the server when files are synchronized. When this problem occurs, you receive the following error message:

Access Denied.

Additionally, a .tmp file that corresponds to the file appears on the server.

You may experience this symptom even when you have Change permissions to the shared resource.

When you transfer a large file between two Windows Vista-based computers by using a Bluetooth connection, one of the computers may go to sleep during the transfer. When this problem occurs, the file transfer is not completed.

This problem occurs if the file transfer requires more time than the time that is configured for the computer to go to sleep. For example, this problem occurs if you configure the computer to go to sleep after two minutes, and the Bluetooth file transfer requires three minutes to finish.

In Windows Vista, you use a program’s Save As dialog box to save a file by using the name of another file. You select the file name from the history list in the File name box. However, the changes are not saved by using this file name. Instead, the original file is overwritten.

For example, you have two files that are named notepad1 and notepad2. You modify the notepad1 file, and you want to save the changes to a file that is named notepad2. However, your changes are saved to the notepad1 file. The earlier contents of the notepad1 file are overwritten.

When you run any program in Windows, Adobe Reader or Adobe Acrobat loads instead and displays the error message, “not a supported file type”, on Microsoft Windows Vista.

The update sequence number (USN) journal record contains an incorrect file name when you move a file in Windows Vista, in Microsoft Windows Server 2003, or in Microsoft Windows XP.

This problem occurs if a hard link points to the file that you moved. In this situation, the USN journal record contains the name of the hard link instead of the moved file. Therefore, applications that rely on the USN journal may not work correctly.

When you try to install a device driver in Windows Vista, you receive an error message that states that the driver was not installed because of a file copy error.

Note: This message is generated by the driver’s Setup program. The message is not generated by Windows Vista. Therefore, the error message text may vary.

This problem occurs if the following conditions are true:

• The name of the user account or the path of the driver source contains quad-byte Unicode characters. For example, the current user name contains Chinese characters.
• The driver package uses Lempel-Ziv (LZ) compression.