Consider the following scenario. You have a client computer that is running Windows Server 2008 or Windows Vista. You also have a server that is running Windows Server 2008 or Windows Vista. You run an application that uses the named pipes protocol to transfer data between the client computer and the server. After interprocess communication (IPC) between the client computer and the server runs for some time, the application is aborted on the client computer. Additionally, you receive the following error code:

Error code 1450 (ERROR_NO_SYSTEM_RESOURCES)

When this problem occurs, the value of the Pool Nonpaged Bytes performance counter keeps increasing. If you use a memory monitoring tool to monitor the memory pool, you see that the memory leak occurs in the nonpaged pool and in the SmMs tag.

Note: This problem does not occur if the server runs Windows XP or Windows Server 2003.

Consider the following scenario. On a Windows Vista-based computer or on a Windows Server 2008-based computer, you transfer multiple large files at the same time through a high-bandwidth network connection. You transfer the large files at 1 gigabit per second (Gbps). In this scenario, you expect the network bandwidth to be almost fully used. However, in Task Manager, you notice that only part of the network bandwidth is used.

In Microsoft Windows Media Player 11, you transfer media to a portable device. For example, you transfer music files. When you cancel the transfer process, Windows Media Player 11 stops responding (hangs).

This problem occurs when the device uses the Media Transfer Protocol (MTP).

When you use an application to transfer media from a computer that is running Windows Vista or Windows XP to a portable device, the memory for the application increases for each file that you transfer. The memory increase may cause the application to stop responding (hang) or to crash. This problem occurs when you transfer audio, video, or pictures.

Consider the following scenario:

• You attach an external “Institute of Electrical and Electronics Engineers” (IEEE) 1394 Serial Bus Protocol 2 (SBP2) hard disk and an external IEEE 1394 SBP2 optical drive to a Windows Vista-based computer.
• You copy files from the attached optical drive to the system internal hard disk.
• At the same time, you copy files from the attached hard disk to the system internal hard disk.

In this scenario, the file transfer from the attached devices to the system internal hard disk cannot be completed. The file transfer dialog box does not disappear until the system restarts. Additionally, the attached hard disk cannot be accessed, and the attached optical device loses its drive letter.

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 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.

A ‘better’ way to do an ill-advised Vista ‘Upgrade’ Keep reading →