Consider the following scenario. On a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Server 2008, you connect a USB device to a USB port. The USB port is located on a generic hub that is attached to the root hub. Then, an overcurrent condition occurs on the USB device. However, you cannot automatically recover from this overcurrent condition. Instead, the USB device becomes unresponsive until you restart the computer. This symptom remains even after you disconnect and then reconnect the USB device.

Notes

• An overcurrent condition occurs on an electrical circuit when devices that are connected to the computer draw too much power from the USB port. An overcurrent condition may occur when the USB wiring is crossed up (short-circuited). This condition may also occur when too many devices are connected to the same hub. (This overloads the hub.)
• This problem does not occur if a USB device is plugged directly into a USB port on the root hub.

In Windows Vista Service Pack 1 (SP1) and in Windows Server 2008, the random number generator (RNG) is not compliant with Federal Information Processing Standard (FIPS) 140-2.

This problem affects all the functions that use the RNG. The CryptoAPI function CryptGenRandom and the CNG function BCryptGenRandom use the RNG directly. Other functions that generate random numbers for keying material or for other purposes may also use the RNG indirectly.

Important This problem does not affect the external behavior of any functions that use the RNG. It does not affect the strength of any system cryptographic implementations. Additionally, it does not change cryptographic functionality in any other way.

Consider the following scenario:

• On a Windows Vista Service Pack 1 (SP1)-based computer, you run the “Connect to a Network Projector” utility (Netproj.exe) to search for projectors on the network.
• There are many projectors on the network.

In this scenario, some network projectors may not be found during the search.

Note: This problem occurs even if the projectors and the computer reside on the same network.

On a Windows Server 2008-based computer or a Windows Vista Service Pack 1-based computer, all services or processes that require authentication may stop responding.

For example, when you type your user name and password, the system stops responding at the “Welcome” screen.

Consider the following scenario. You install Windows Vista Service Pack 1 (SP1). At the time of the installation, you install a Serial ATA (SATA) controller driver other than the Microsoft Advanced Host Controller Interface (MSAHCI) driver. Then, after Windows Vista SP1 is installed, you update the existing SATA driver to the MSAHCI driver. However, when you restart the computer after you update the driver, you receive the following stop error message:

STOP 0×0000007B (parameter1, parameter2, parameter3, parameter4)
INACCESSIBLE_BOOT_DEVICE

Don’t forget, free tech support for SP1 install and compatibility issues! Keep reading →

After an unattended installation of Windows Vista Service Pack 1 (SP1), the customized desktop wallpaper is replaced by the default Windows Vista wallpaper. Typically, this issue occurs if the customized desktop wallpaper is stored on a network share or is located in the user’s redirected My Documents folder.

Consider the following scenario:

• You have a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Server 2008.
• You let the system go idle for some time. Therefore, the monitor enters a low-power state, and the screen turns off.
• To wake up the monitor, you press the computer’s power button, or you use the remote control. The monitor resumes the full-power state, and the screen turns back on.

However, in this scenario, the monitor remains in the full-power state for only several seconds, and then it reverts to the low-power state.

Note: This issue does not occur when you wake up the monitor by pressing a key on the keyboard or by clicking the mouse.

Microsoft has released a hotfix to support the new 64-bit CPU from VIA Technologies. You can apply this hotfix on computers that are running Windows Server 2008 or Windows Vista Service Pack 1 (SP1). This hotfix adds the ID and vendor strings for the new VIA 64-bit CPU. After you apply this hotfix, computers that are running Windows Server 2008 or Windows Vista SP1 can recognize the VIA 64-bit CPU and the system model that is based on this kind of CPU.

You install Windows Vista Service Pack 1 (SP1) on a computer that is running the original version of Windows Vista. When you try to run the Group Policy Management Console (GPMC) snap-in, you receive an error message that resembles the following:

MMC could not create the snap-in.