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.

When you play a video in a video playback application that uses Media Foundation on a computer that is running Windows Vista Service Pack 1 (SP1), you receive an error message. Additionally, the application crashes.

For example, when you play a video by using Media Center in full-screen mode, you receive the following error message:

Media Center has stopped working.

A problem caused the program to stop working correctly. Please close the program.

Consider the following scenario:

• You install Windows Server 2008 or Windows Vista Service Pack 1 on a GUID partition table (GPT) disk.
• Then, you convert the GPT disk from the Basic disk type to the Dynamic disk type.
• Later, you increase or reduce the size of the boot partition on the dynamic disk by using the Disk Management snap-in.

In this scenario, the system cannot start. When you try to start the system, you receive the following error message:

Windows Boot Manager
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. Insert your Windows installation disc and restart your computer.
2. Choose your language settings, and then click “Next.”
3. Click “Repair your computer.”
If you do not have this disc, contact your system administrator or computer manufacturer for assistance.
File: boot_file
Status: 0xc0000225
Info: The selected entry could not be loaded because the application is missing or corrupt.

On a computer that is running Windows Vista Service Pack 1 or Windows Server 2008, when an application tries to obtain an exclusive lock to a volume, the attempt is unsuccessful. Additionally, you may receive the following error message:

Access is denied

For example, when a backup application restores data on a volume, the application may try to obtain an exclusive lock to the volume. In this case, the restore operation is unsuccessful.

This problem typically occurs after the system runs for several hours. When this problem occurs, you may discover that the System process is holding handles to some volumes.

Note: This problem does not occur on a computer that is running Windows Vista without Service Pack 1.

Though earlier versions seemed to work fine, version 6.0.4 officially supports 32-bit and 64-bit Vista SP1. Keep reading →