Microsoft has released security bulletin MS08-069. To view the complete security bulletin, visit one of the following Microsoft Web sites:

• Home users:
  http://www.microsoft.com/protect/computer/updates/bulletins/200811.mspx (http://www.microsoft.com/protect/computer/updates/bulletins/200811.mspx)

  Skip the details: Download the updates for your home computer or laptop from the Microsoft Update Web site now:

  http://update.microsoft.com/microsoftupdate/ (http://update.microsoft.com/microsoftupdate/)
• IT professionals:
  http://www.microsoft.com/technet/security/bulletin/MS08-069.mspx (http://www.microsoft.com/technet/security/bulletin/MS08-069.mspx)

How to obtain help and support for this security update

For home users, no-charge support is available by calling 1-866-PCSAFETY in the United States and Canada or by contacting your local Microsoft subsidiary. For more information about how to contact your local Microsoft subsidiary for support issues with security updates, visit the Microsoft International Support Web site:

North American customers can also obtain instant access to unlimited no-charge e-mail support or to unlimited individual chat support by visiting the following Microsoft Web site:

For enterprise customers, support for security updates is available through your usual support contacts.

Additional information about this security update

• If you have multiple versions of Microsoft XML Core Services (MSXML) installed, you may have to apply multiple packages for this security update. Additionally, if you install a version of MSXML after you apply this security update, you may have to apply an additional package for this security update.For more information about the different MSXML versions that are available or that are included with various Microsoft products or software updates, click the following article number to view the article in the Microsoft Knowledge Base:
  269238  (/Feedback.aspx?kbNumber=269238/ ) List of Microsoft XML Parser (MSXML) versions
• Security update package 954459 for MSXML 6.0 is a complete installation package. You can use this package to install MSXML 6.0 on a computer that has no earlier versions of MSXML 6.0 installed. You can also use this package to update an existing installation of MSXML 6.0.
• Windows Update, Microsoft Update, and Microsoft Systems Management Server (SMS) 2003 Inventory Tool for Microsoft Updates offer security update package 954459 only if an earlier version of MSXML 6.0 is already installed on the computer.
• This security update is installed in the %SystemRoot% SYSTEM32 folder.
• When you remove security update 954459 for MSXML 6.0, MSXML 6.0 is completely removed from the computer.
• To apply this security update in quiet mode together with verbose logging and without restarting the computer, use a command-line command that resembles the following:
  • For x86-based computers:
    msxml6-KB954459-enu-x86.exe/q REBOOT=ReallySuppress/l*v c: KB954459.log
  • For IA-64-based computers:
    msxml6-KB954459-enu-ia64.exe/q REBOOT=ReallySuppress/l*v c: KB954459.log
  • For AMD64-based computers:
    msxml6-KB954459-enu-amd64.exe/q REBOOT=ReallySuppress/l*v c: KB954459.log

  A detailed log of the installation process will be located in the file that you specify in the command. In this example, the file is C: KB954459.log.

For more information about the latest service pack for Windows Vista, click the following article number to view the article in the Microsoft Knowledge Base:

File information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). The dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time (DST) bias. Additionally, the dates and times may change when you perform certain operations on the files.

For all supported versions of Windows 2000

Windows XP and Windows Server 2003 file information notes

• The files that apply to a specific milestone (RTM, SPn) and service branch (QFE, GDR) are noted in the SP requirement and Service branch columns.
• GDR service branches contain only those fixes that are widely released to address widespread, critical issues. QFE service branches contain hotfixes in addition to widely released fixes.
• In addition to the files that are listed in these tables, this software update also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.

For all supported x86-based versions of Windows XP

For all supported x64-based versions of Windows Server 2003 and of Windows XP Professional x64 edition

For all supported x86-based versions of Windows Server 2003

For all supported IA-64-based versions of Windows Server 2003

Windows Vista and Windows Server 2008 file information notes

• The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
  Collapse this tableExpand this table

  Version	Product	Milestone	Service branch
  6.0.6000.16xxx	Windows Vista	RTM	GDR
  6.0.6000.20xxx	Windows Vista	RTM	LDR
  6.0.6001.18xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	GDR
  6.0.6001.22xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	LDR

• Service Pack 1 is integrated into the original release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000. xxxxxx version number.
• GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

For all supported IA-64-based versions of Windows Server 2008

Additional file information for Windows Server 2008 and for Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported IA-64-based versions of Windows Server 2008

Source: Microsoft Support

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

An input method editor (IME) keyboard shortcut lets you switch the input language. By design, the CTRL+SHIFT+0 key assignment is standard for all users. However, some applications might use this keyboard shortcut for other purposes. In this case, the application will not work as expected when you use the shortcut with the application.

Remove the shortcut assignment to make the application work as expected. To do this, follow these steps:

1. Click Start, and then click Control Panel.
2. Double-click Regional and Language Options.
3. Click Keyboards and Languages, and then click Change keyboards.
4. Click Advanced Key Settings, and select Between input languages.
5. Click change Key Sequence.
6. For Switch Keyboard Layout, select Not Assigned.
7. Click OK to close each dialog box.

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

In Windows Vista, you may experience the following symptoms.

Back to the top

Symptom 1

When you try to use Windows Task Scheduler to change the defrag schedule, you may receive the following error message:

Back to the top

Symptom 2

When you try to change the settings for a file backup operation, you may receive the following error message:

Back to the top

These problems occur because of an error in the Transaction Manager.

Back to the top

To resolve this problem, follow these steps:

1.	Click Start, click All Programs, click Accessories, and then right-click Command Prompt.
2.	Click Run as administrator. If you are prompted for an administrator password, type the password. If you are prompted for confirmation, click Continue.
3.	At the command prompt, type the following command, and then press ENTER: fsutil resource setautoreset true DriveLetter: Note The DriveLetter placeholder represents the letter of the hard disk drive that contains the Windows system folder. By default, the drive letter is C.
4.	Restart the computer.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

Consider the following scenario. You have an Apple iPod that is connected to a Windows Vista-based computer through a USB connection. Then, you disconnect the iPod from the computer. In this scenario, the data on the iPod may become corrupted.

This problem may occur if you use one of the following methods to disconnect the iPod:

•	You use the Safely Remove Hardware feature in the notification area to disconnect the iPod. Then, you disconnect the USB cable.
•	You use the Eject command in Windows Explorer to disconnect the iPod. Then, you disconnect the USB cable.

Back to the top

To resolve this problem, install update 936824. To install this update, visit the following Microsoft Web site:

Back to the top

Update information

The following files are available for download from the Microsoft Download Center:

Download the Download the update for Windows Vista 32-bit version (KB936824) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=6A9FC712-F518-44AB-A11F-B6AA22525DEC)
Download the update for Windows Vista 64-bit version (KB936824) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=A7A9FD92-7521-4A6F-BDD2-790EE2612D66)
Release Date: May 8, 2007

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this update.

Update replacement information

This update replaces update 933824.

File information

The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x86-based versions

File name	File version	File size	Date	Time	Platform
Package_1_for_kb936824_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not applicable	1,735	30-Apr-2007	20:43	Not applicable
Package_1_for_kb936824~31bf3856ad364e35~x86~~6.0.1.0.mum	Not applicable	2,440	30-Apr-2007	20:41	Not applicable
Package_2_for_kb936824_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not applicable	1,983	30-Apr-2007	20:43	Not applicable
Package_2_for_kb936824~31bf3856ad364e35~x86~~6.0.1.0.mum	Not applicable	2,720	30-Apr-2007	20:41	Not applicable
Update-bf.mum	Not applicable	1,862	30-Apr-2007	20:43	Not applicable
Update.mum	Not applicable	1,897	30-Apr-2007	20:41	Not applicable
Usbstor.sys	6.0.6000.20588	55,296	28-Apr-2007	02:31	x86
X86_3062b910f8361f96560d8463846fbca1_31bf3856ad364e35_6.0.6000.20588_none_4e137d9609394891.manifest	Not applicable	699	30-Apr-2007	20:41	Not applicable
X86_f2dd01f2032c5b6566762661bf24827f_31bf3856ad364e35_6.0.6000.16478_none_e38721a2fccac79f.manifest	Not applicable	699	30-Apr-2007	20:41	Not applicable
X86_microsoft-windows-ipod-fix-01_31bf3856ad364e35_6.0.6000.16478_none_04e03d3efd49bd96.manifest	Not applicable	1,308	28-Apr-2007	04:01	Not applicable
X86_microsoft-windows-ipod-fix-01_31bf3856ad364e35_6.0.6000.20588_none_055f0a1e166f7951.manifest	Not applicable	1,308	28-Apr-2007	03:33	Not applicable
X86_usbstor.inf_31bf3856ad364e35_6.0.6000.16478_none_465c5f209ade1e53.manifest	Not applicable	1,482	30-Apr-2007	20:43	Not applicable
X86_usbstor.inf_31bf3856ad364e35_6.0.6000.20588_none_46db2bffb403da0e.manifest	Not applicable	1,482	30-Apr-2007	20:43	Not applicable
Usbstor.sys	6.0.6000.16478	55,296	28-Apr-2007	02:39	x86

Windows Vista, 64-bit versions

File name	File version	File size	Date	Time	Platform
Amd64_97c033069d26f2fd361f80da50c07f32_31bf3856ad364e35_6.0.6000.20588_none_333d5b5494183685.manifest	Not applicable	703	30-Apr-2007	20:41	Not applicable
Amd64_ce91649dffd237d9476d3dd44be082c9_31bf3856ad364e35_6.0.6000.16478_none_2b5db0e1045caa2a.manifest	Not applicable	703	30-Apr-2007	20:41	Not applicable
Amd64_microsoft-windows-ipod-fix-01_31bf3856ad364e35_6.0.6000.16478_none_60fed8c2b5a72ecc.manifest	Not applicable	1,310	28-Apr-2007	05:08	Not applicable
Amd64_microsoft-windows-ipod-fix-01_31bf3856ad364e35_6.0.6000.20588_none_617da5a1ceccea87.manifest	Not applicable	1,310	28-Apr-2007	04:44	Not applicable
Amd64_usbstor.inf_31bf3856ad364e35_6.0.6000.16478_none_a27afaa4533b8f89.manifest	Not applicable	1,484	30-Apr-2007	20:47	Not applicable
Amd64_usbstor.inf_31bf3856ad364e35_6.0.6000.20588_none_a2f9c7836c614b44.manifest	Not applicable	1,484	30-Apr-2007	20:47	Not applicable
Package_1_for_kb936824_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not applicable	1,745	30-Apr-2007	20:43	Not applicable
Package_1_for_kb936824~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not applicable	2,454	30-Apr-2007	20:41	Not applicable
Package_2_for_kb936824_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not applicable	1,995	30-Apr-2007	20:43	Not applicable
Package_2_for_kb936824~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not applicable	2,736	30-Apr-2007	20:41	Not applicable
Update-bf.mum	Not applicable	1,862	30-Apr-2007	20:43	Not applicable
Update.mum	Not applicable	1,897	30-Apr-2007	20:41	Not applicable
Usbstor.sys	6.0.6000.16478	66,048	28-Apr-2007	03:20	x64
Usbstor.sys	6.0.6000.20588	66,048	28-Apr-2007	02:58	x64

Back to the top

If the data on the iPod is corrupted, select the iPod in the Apple iTunes user interface. Then, on the Summary tab, click Restore to restore the iPod to working condition.

Apple recommends that you always use iTunes to disconnect or to eject an iPod. To eject an iPod in iTunes, click Eject iPod on the Controls menu. Then, disconnect the USB cable.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

For more information about this problem, visit the following Apple Web site:

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Back to the top

When you use the virtualization feature of Windows Vista, you may the experience file and registry virtualization issues that are described in the following scenarios.

Back to the top

Scenario 1: You receive error messages when you install, upgrade, or use an application

When you install, upgrade, or use an application, you may receive various error messages that indicate that access was denied. For example, you may experience one of the following symptoms:

•	After you install an application in a folder other than the %programfiles% folder, you receive access denied error messages. Additionally, the application does not function as expected.
•	You receive application error messages that resemble the following: Cannot create folder under C: MyApp Temp Cannot create file under C: MyApp Temp output.dat
•	You receive error messages that resemble the following: Error Writing to MyFile.exe This issue may occur when you perform any of the following actions: • You create links in virtualized locations. • You use the Encrypting File System (EFS) to encrypt files. • You try to view compressed files. • You use the command prompt to copy an .exe, .sys, or .dll file into a virtualizable location.
•	Parts of the application that require file input or output no longer work correctly.

Back to the top

Scenario 2: You cannot find the file or the folder that you just created

When you use an application for which virtualization is enabled, you create data files in virtualizable locations of the file system. When you use another application or Windows Explorer to access these newly created files, you cannot find them. For example, if you save a file in a photo editing application in the %programfiles%, %systemroot%, or %programdata% folders, you cannot locate this file.

Back to the top

Scenario 3: You upgrade an application and then experience unexpected program behavior

After you upgrade an application, you receive an error message that resembles the following:

Additionally, the application does not work as expected. The application appears to be using incorrect or pre-upgrade data.

Back to the top

Scenario 4: After you uninstall an application, the application’s files are still present on the computer

In this scenario, you experience one of the following symptoms:

•	In another application, you notice that file and folder information for the uninstalled application still exists in the %programfiles%, %programdata%, or %systemroot% folders.
•	The %userprofile% AppData Local VirtualStore folder is larger than you expect. When you uninstalled the application, the virtualized files that were created during the application’s runtime were not removed.

Back to the top

These issues are caused by one or more of the following conditions:

•	The application tries to create files or folders outside certain specified virtualized folders.
•	Files that are saved by an application in the %programfiles% folder may be directed to a folder other than the user’s virtual store folder.
•	The application uses a file that is not supported for virtualization.

.

Back to the top

Scenario 1

To determine whether you have the issue that is described in Scenario 1, look in Event Viewer for FileCreateVirtualExclude events. To do this, follow these steps:

1.	Click Start, type eventvwr in the Start Search box, and then click eventvwr.exe in the Programs list. If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
2.	Expand Applications and Services Logs, expand Microsoft, expand Windows, expand UacFileVirtualization, and then select Operational. If the event ID is 5000, a FileCreateVirtualExclude event has occurred.

To resolve this issue, use one of the following methods:

•	Reinstall the application in the %programfiles% folder if the program is not already installed in the %programfiles% folder.
•	Use an account that has administrative credentials to run this application. To do this, locate and then right-click the application shortcut, and then click Run as administrator. If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
•	Run the application at an elevated command prompt. To do this, follow these steps: 1. Click Start, and then type cmd in the Start Search box, and then click cmd.exe in the Programs list. 2. In the Programs list, right-click cmd, and then click Run as administrator. If you are prompted for an administrator password or for confirmation, type your password, or click Continue. 3. Type MyAppsPath/MyApp, and then press ENTER. MyAppsPath/MyApp represents the path and the name of the application.
•	Change the security settings on the application’s folder. To do this, follow these steps: 1. Log on as a user who has administrative credentials, and then use Windows Explorer to open the application’s folder. 2. Right-click the application’s folder, and then click Properties. 3. On the Security tab, click Edit. If you are prompted for an administrator password or for confirmation, type your password, or click Continue. 4. Under Group or user names, click your user account. 5. Under Permissions for Users, click Allow for the following permissions: • Modify • Read & Execute • List Folder Contents • Read • Write 6. Click OK.

Back to the top

Scenario 2

To resolve this issue, use one of the following methods:

•	Click the Compatibility Files button that appears on the Explorer bar to view virtualized files in the folder. The Compatibility Files button appears only if there are virtualized files in the folder.
•	Look in the C: Users User_name AppData Local VirtualStore folder to locate files and folders.
•	Save your application’s data in a folder under your user profile.

Back to the top

Scenario 3

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To resolve this issue, use one of the following methods:

•	Run the application at an elevated command prompt. To do this, follow these steps: 1. Click Start, type cmd in the Start Search box, and then click cmd.exe in the Programs list. If you are prompted for an administrator password or for confirmation, type your password, or click Continue. 2. Type MyAppsPath/MyApp. MyAppsPath/MyApp represents the path and the name of the application, and then press ENTER
•	Open the virtual store, and then delete the old application data files. To do this, use Windows Explorer to open the C: Users User_name AppData Local VirtualStore Program Files MyApp folder, and then delete any files that are not your documents or data files.
•	Delete the virtual store from the registry. To locate the virtual store in the registry and to remove any unnecessary keys, follow these steps: 1. Click Start, type regedit in the Start Search box, and then click regedit.exe in the Programs list. If you are prompted for an administrator password or for confirmation, type your password, or click Continue. 2. Locate and then click the following registry subkey: HKEY_CURRENT_USER Software Classes VirtualStore 3. For any application registry keys that are no longer needed, right-click the key, click Delete, and then click Yes.

Back to the top

Scenario 4

To resolve this issue, use Windows Explorer to open the C: Users User_name AppData Local VirtualStore MyApp folder, and then delete any obsolete application data.

Back to the top

File and registry virtualization helps users who have restricted access to the registry and to the file system write to these protected areas. Virtualization creates a per user copy and then redirects successive data operations.For example, assume that an application is running under a Limited User Account or under accounts that require User Account Control permissions. When this application writes to a system location, such as to the %programfiles% folder, Windows Vista redirects write operations and read operations to a user-specific location in the user’s profile folder (%localappdata% VirtualStore). By default, this location is C: Users User_name AppData Local VirtualStore Program Files Application_name. Registry virtualization works similarly but applies to registry keys under the HKEY_LOCAL_MACHINE SOFTWARE subtree. The keys and data under this subtree are redirected to the HKEY_CURRENT_USER Software Classes VirtualStore subkey.

For more information, visit the following Microsoft Web site:

Back to the top

On a Windows Vista-based computer, you turn on the wake from sleep option for a network adapter that supports Wake On LAN (WOL) functionality. After you do this, the computer does not wake from sleep when it receives network traffic.

For example, you click to select the Allow this device to wake the computer check box on the Power Management tab of the properties dialog box for the network adapter. You install the sample PassThru driver that is included in the Microsoft Windows Driver Kit (WDK), or you install a virus scanner that uses the same PassThru driver technology. Then, you put the computer to sleep. However, the computer does not wake from sleep when you send a PING command or a magic packet.

Back to the top

To work around this problem, use one of the following methods:

•

Uninstall the sample PassThru driver.

•

Contact the manufacturer of your virus scanning program to find out if a program update is available that does not exhibit this problem. You may have to use a different virus scanning program.For information about how to contact the manufacturer of your virus scanning program, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base: 65416 (/Feedback.aspx?kbNumber=65416/)Hardware and software vendor contact information, A-K 60781 (/Feedback.aspx?kbNumber=60781/)Hardware and software vendor contact information, L-P 60782 (/Feedback.aspx?kbNumber=60782/)Hardware and software vendor contact information, Q-Z Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. Note You should uninstall the existing virus scanning program before you install a different virus scanning program.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

On a Windows Vista-based computer, when you try to copy files from a server on a network, the copy process may stop responding (hang), and you may receive a message that resembles the following:

This problem may occur only occasionally.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x86-based versions

File name	File version	File size	Date	Time	Platform
Smb.sys	6.0.6000.20521	66,048	24-Jan-2007	03:02	x86
Update.mum	Not Applicable	1,986	24-Jan-2007	16:57	Not Applicable
X86_microsoft-windows-nbsmb.d_31bf3856ad364e35_6.0.6000.20521_none_454313304b30a4e0.manifest	Not Applicable	687	24-Jan-2007	16:57	Not Applicable
X86_microsoft-windows-nbsmb_31bf3856ad364e35_6.0.6000.20521_none_5df94bff13fca6fc.manifest	Not Applicable	6,230	24-Jan-2007	16:58	Not Applicable

Windows Vista, 64-bit versions

File name	File version	File size	Date	Time	Platform
Amd64_microsoft-windows-nbsmb.d_31bf3856ad364e35_6.0.6000.20521_none_a161aeb4038e1616.manifest	Not Applicable	691	24-Jan-2007	16:57	Not Applicable
Amd64_microsoft-windows-nbsmb_31bf3856ad364e35_6.0.6000.20521_none_ba17e782cc5a1832.manifest	Not Applicable	6,498	24-Jan-2007	23:59	Not Applicable
Smb.sys	6.0.6000.20521	87,552	24-Jan-2007	03:23	x64
Update.mum	Not Applicable	1,986	24-Jan-2007	16:57	Not Applicable

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

In Windows Vista, you configure Windows Fax and Scan to automatically route incoming faxes to a printer. Then, Windows Fax and Scan becomes unresponsive.

This problem occurs when the printer requires input from the user. For example, the printer may require that you input the name of the file that is to be printed.

Back to the top

This problem occurs because the routing process for incoming faxes is automatic. In this process, the printer waits for input from a user. However, if the printer cannot receive this input, the printer is unable to complete the printing job. Then, Windows Fax and Scan becomes unresponsive if the printer does not finish the printing job.

Back to the top

To work around this problem, restart Windows Fax and Scan.

Back to the top

Steps to reproduce the problem

•

Configure Windows Fax and Scan to route the incoming faxes to a printer that requires that the user input the name of the file that is to be printed. To do this, follow these steps: 1. Click Start, click All Programs, and then click Windows Fax and Scan. 2. On the Tools menu, click Fax Settings. 3. On the General tab, click More options under Send/receive options. 4. In the More options dialog box, click to select the Print a copy to check box under When a fax is received, and then select a printer that prints to file. Note You can select Microsoft Office Document Image Writer or XML Paper Specification (XPS) Document Writer as the printer.

•

Receive a fax in Windows Fax and Scan. For more information about how to receive a fax in Windows Fax and Scan, visit the following Web site: http://windowshelp.microsoft.com/Windows/en-US/Help/811d861e-177b-475d-a34e-72948adb7a061033.mspx (http://windowshelp.microsoft.com/Windows/en-US/Help/811d861e-177b-475d-a34e-72948adb7a061033.mspx)

Back to the top

In Windows Vista, there is no option to control the volume when you click to select the Hear text on screen read aloud (Narrator) check box in the Ease of Access dialog box.

Additionally, internal speaker controls may not change the narrator volume level. These controls include volume controls on a multimedia keyboard and Fn keys and volume knobs on a portable computer.

Back to the top

This issue occurs because of the way that Windows Vista controls audio. In Windows Vista, volume controls are now digital. Therefore, internal speaker controls change the operating system settings instead of the hardware settings. Additionally, you cannot adjust the operating system settings when you are at the Windows Vista welcome screen. Therefore, you cannot use internal speaker controls to control the volume while you are at the Windows Vista welcome screen.

Back to the top

To resolve this issue, modify the voice volume in the Microsoft Narrator dialog box. To open the Microsoft Narrator dialog box, follow these steps:

1.	Click Start, type Narrator in the Start Search box, and then click Narrator in the Programs list.
2.	Click Voice Settings.
3.	In the Voice Settings dialog box, select the voice options that you want to change. To change the speed, the pitch, or the volume of the voice, click a number in the corresponding field.

When you change voice settings, it may take from several seconds to a minute before the new settings take effect.

Back to the top

To access the Ease of Access dialog box, click the Ease of Access icon on the Windows Vista welcome screen.

Back to the top

After you copy an image that is in a RAW file format to a computer that is running Windows Vista or Windows XP Service Pack 2 (SP2), the image does not appear in Windows Photo Gallery or in Windows Live Photo Gallery. Additionally, you may be unable to view thumbnail images of the picture by using Windows Explorer.

Back to the top

This issue occurs if you do not have a RAW image codec for your camera model installed in Windows Vista or in Windows XP SP2.

Back to the top

To resolve this problem, use one or more of the following methods, as appropriate for your situation:

•	Obtain a RAW image codec Obtain and install a Windows Vista-compatible or Windows XP-compatible RAW image codec from the camera manufacturer.
•	Obtain a RAW workflow program Obtain and install a Windows Vista-compatible or Windows XP-compatible RAW workflow program that supports the camera model. Note This does not resolve the issue in which you cannot view the images in Windows Photo Gallery or in Windows Live Photo Gallery. However, this action enables you to process the RAW image files.
•	Save the images in a RAW + JPG format If the camera has this option, configure the camera to save images in a RAW + JPEG format. This option frequently creates a separate JPEG image file together with the RAW image file. This action does not let you view the RAW image files. However, this action lets you view a JPEG representation of each RAW image file.

Back to the top

Windows Vista includes the Windows Imaging Component (WIC). WIC is also available for Windows XP SP2. WIC is an extensible, operating system-wide platform for photo imaging codecs and metadata. WIC contains system codecs for the most common imaging formats such as JPEG, TIFF, PNG, GIF, BMP, and ICO. WIC also offers a pluggable platform for all photo imaging codecs. This includes the RAW image format. Additionally, the WIC platform contains generic metadata readers and writers for EXIF 2.2, XMP 1.0, and IPTC in TIFF.

A codec provider such as a camera manufacturer can create an installable RAW image codec for Windows Vista or for Windows XP SP2. This allows for RAW image files to appear in Windows Explorer, in Windows Photo Gallery, in Windows Live Photo Gallery, and in other programs that support WIC.This development model works in a manner that resembles how video codecs are created. The advantage that is provided when the camera manufacturer creates the codec is that the file format may change. In this situation, new codec versions must be created to support the features that are available in each new camera model.

Back to the top

When you run an application that calls the MessageBeep function on a Windows Vista-based computer, several system page table entries (PTEs) are leaked. Under most circumstances, this minor leak is not noticeable. However, if the MessageBeep function is frequently or repeatedly called, this leak may cause the computer to stop responding (hang).

Note You can view the system PTE usage in Performance Monitor. To do this, add the Free System Page Table Entries counter to Performance Monitor.

Back to the top

In this situation, the port class driver maps a buffer. However, this driver does not always then unmap the buffer as expected. Therefore, the system PTEs that are used to map the buffer are leaked.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Vista service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x86-based versions

File name	File version	File size	Date	Time	Platform
Package_1_for_kb951119~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,814	10-Apr-2008	16:09	Not Applicable
Package_2_for_kb951119~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,687	10-Apr-2008	16:09	Not Applicable
Package_3_for_kb951119~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,525	10-Apr-2008	16:09	Not Applicable
Package_4_for_kb951119~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,819	10-Apr-2008	16:09	Not Applicable
Package_5_for_kb951119~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,527	10-Apr-2008	16:09	Not Applicable
Package_6_for_kb951119~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,815	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_client_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,426	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,367	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_client~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,713	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,422	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_sc~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,423	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,425	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_server~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,431	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,422	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,430	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_winpe_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,420	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_winpe~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,424	10-Apr-2008	16:09	Not Applicable
Update.mum	Not Applicable	3,571	10-Apr-2008	16:09	Not Applicable
X86_hdaudbus.inf_31bf3856ad364e35_6.0.6000.20810_none_75ba2300a28648da.manifest	Not Applicable	1,881	10-Apr-2008	16:19	Not Applicable
X86_hdaudbus.inf_31bf3856ad364e35_6.0.6001.22154_none_777921389fc9b1c4.manifest	Not Applicable	1,881	10-Apr-2008	16:19	Not Applicable
X86_wdmaudio.inf_31bf3856ad364e35_6.0.6000.20810_none_5effe9323624d0b2.manifest	Not Applicable	4,606	10-Apr-2008	16:19	Not Applicable
X86_wdmaudio.inf_31bf3856ad364e35_6.0.6001.22154_none_60bee76a3368399c.manifest	Not Applicable	4,606	10-Apr-2008	16:19	Not Applicable
Hdaudbus.sys	6.0.6000.20810	553,472	10-Apr-2008	02:51	x86
Hdaudbus.sys	6.0.6001.22154	561,152	10-Apr-2008	02:57	x86
Drmk.sys	6.0.6000.20810	130,048	10-Apr-2008	04:26	x86
Drmkaud.sys	6.0.6000.20810	5,632	10-Apr-2008	02:51	x86
Portcls.sys	6.0.6000.20810	167,424	10-Apr-2008	02:51	x86
Sysfxui.dll	6.0.6000.20810	338,944	10-Apr-2008	04:59	x86
Wmalfxgfxdsp.dll	11.0.6000.6503	1,312,256	10-Apr-2008	04:59	x86
Drmk.sys	6.0.6001.22154	130,048	10-Apr-2008	04:26	x86
Drmkaud.sys	6.0.6001.22154	5,632	10-Apr-2008	02:57	x86
Portcls.sys	6.0.6001.22154	167,424	10-Apr-2008	02:57	x86
Sysfxui.dll	6.0.6001.22154	338,944	10-Apr-2008	05:02	x86
Wmalfxgfxdsp.dll	11.0.6001.7102	1,312,256	10-Apr-2008	05:02	x86

Windows Vista, x64-based versions

File name	File version	File size	Date	Time	Platform
Amd64_hdaudbus.inf_31bf3856ad364e35_6.0.6000.20810_none_d1d8be845ae3ba10.manifest	Not Applicable	1,883	10-Apr-2008	16:23	Not Applicable
Amd64_hdaudbus.inf_31bf3856ad364e35_6.0.6001.22154_none_d397bcbc582722fa.manifest	Not Applicable	1,883	10-Apr-2008	16:23	Not Applicable
Amd64_wdmaudio.inf_31bf3856ad364e35_6.0.6000.20810_none_bb1e84b5ee8241e8.manifest	Not Applicable	4,608	10-Apr-2008	16:23	Not Applicable
Amd64_wdmaudio.inf_31bf3856ad364e35_6.0.6001.22154_none_bcdd82edebc5aad2.manifest	Not Applicable	4,608	10-Apr-2008	16:23	Not Applicable
Package_1_for_kb951119~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,824	10-Apr-2008	16:09	Not Applicable
Package_2_for_kb951119~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,703	10-Apr-2008	16:09	Not Applicable
Package_3_for_kb951119~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,539	10-Apr-2008	16:09	Not Applicable
Package_4_for_kb951119~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,829	10-Apr-2008	16:09	Not Applicable
Package_5_for_kb951119~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,541	10-Apr-2008	16:09	Not Applicable
Package_6_for_kb951119~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,825	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_client_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,434	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,375	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_client~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,723	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,430	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,431	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,433	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_server~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,439	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,430	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,438	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_winpe_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,428	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_winpe~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,432	10-Apr-2008	16:09	Not Applicable
Update.mum	Not Applicable	3,597	10-Apr-2008	16:09	Not Applicable
Hdaudbus.sys	6.0.6000.20810	937,984	10-Apr-2008	03:11	x64
Hdaudbus.sys	6.0.6001.22154	949,248	10-Apr-2008	03:30	x64
Drmk.sys	6.0.6000.20810	120,832	10-Apr-2008	04:37	x64
Drmkaud.sys	6.0.6000.20810	6,144	10-Apr-2008	03:11	x64
Portcls.sys	6.0.6000.20810	221,696	10-Apr-2008	03:11	x64
Sysfxui.dll	6.0.6000.20810	376,832	10-Apr-2008	05:09	x64
Wmalfxgfxdsp.dll	11.0.6000.6503	1,391,104	10-Apr-2008	05:09	x64
Drmk.sys	6.0.6001.22154	122,368	10-Apr-2008	04:52	x64
Drmkaud.sys	6.0.6001.22154	6,144	10-Apr-2008	03:30	x64
Portcls.sys	6.0.6001.22154	217,600	10-Apr-2008	03:30	x64
Sysfxui.dll	6.0.6001.22154	376,832	10-Apr-2008	05:29	x64
Wmalfxgfxdsp.dll	11.0.6001.7102	1,391,104	10-Apr-2008	05:29	x64

Windows Vista, IA-64-based versions

File name	File version	File size	Date	Time	Platform
Ia64_wdmaudio.inf_31bf3856ad364e35_6.0.6001.22154_none_60c08b6033664298.manifest	Not Applicable	3,236	10-Apr-2008	16:09	Not Applicable
Package_1_for_kb951119~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,824	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,429	10-Apr-2008	16:09	Not Applicable
Package_for_kb951119_server~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,434	10-Apr-2008	16:09	Not Applicable
Update.mum	Not Applicable	1,425	10-Apr-2008	16:09	Not Applicable
Drmk.sys	6.0.6001.22154	237,056	10-Apr-2008	03:24	IA-64
Drmkaud.sys	6.0.6001.22154	6,656	10-Apr-2008	03:24	IA-64
Portcls.sys	6.0.6001.22154	573,952	10-Apr-2008	03:24	IA-64

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

For more information about the MessageBeep function, visit the following Microsoft Web site:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

This article describes how to prepare to upgrade from Microsoft Windows XP to Windows Vista.

Back to the top

Back up important files

Back up important files on the Windows XP-based computer before you upgrade to Windows Vista. A backup of files helps prevent the loss of files if you make a mistake during the upgrade. For more information about how to back up files in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Install Windows XP Service Pack 2

Before you can upgrade from Windows XP to Windows Vista, you must install Windows XP Service Pack 2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Verify the upgrade status of the Windows XP-based computer

To determine whether you can upgrade the edition of Windows XP on the computer to Windows Vista, visit the following Microsoft Web site:

Additionally, you can use the Windows Vista Upgrade Advisor to help determine which edition of Windows Vista you can install. For more information about the Windows Vista Upgrade Advisor, visit the following Microsoft Web site:

If you cannot upgrade the version of Windows XP to Windows Vista, perform a custom installation. (This kind of installation is also known as a clean installation.) When you perform a custom installation, you cannot migrate the Windows XP settings to Windows Vista. For more information about how to perform a custom installation of Windows Vista, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Verify that the programs that you are using are supported by Windows Vista

For more information about how to determine whether programs are compatible with Windows Vista, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Verify the free space on the hard disk

To upgrade from Windows XP to Windows Vista, you must have about 15 gigabytes (GB) of free space on the hard disk on which Windows XP is installed.

To determine how much free space is on the hard disk, follow these steps:

1.	Click Start, and then click My Computer.
2.	Right-click Local Disk (C:), and then click Properties. Note If Windows XP is installed on a different hard disk on the computer, right-click the appropriate hard disk.
3.	On the General tab, view the value in the Free space field.

If the hard disk on which Windows XP is installed does not meet the free space requirements, you cannot perform the upgrade. If insufficient space is available, increase the free space on the hard disk. Or, perform a custom installation. For more information about how to free space on the hard disk, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Verify the file system

Before you perform the upgrade, you must verify that the hard disk or the partition on which Windows XP is installed uses the NTFS file system.To do this, follow these steps:

1.	Click Start, and then click My Computer.
2.	Right-click Local Disk (C:), and then click Properties. Note If Windows XP is installed on a different hard disk on the computer, right-click the appropriate hard disk.
3.	On the General tab, view the File system field.

For more information about how to convert a hard disk from the FAT32 file system to NTFS, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

This article describes step-by-step instructions for how to disable certain Microsoft Internet Protocol version 6 (IPv6) components in Windows Vista. To disable IPv6 components, you must be logged on to the Windows Vista computer as a member of the Administrators group, or your user account must be granted permissions to edit the Windows registry.

Back to the top

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To disable certain IPv6 components in Windows Vista, follow these steps:

1.	Click Start, type regedit in the Start Search box, and then click regedit.exe in the Programs list.
2.	In the User Account Control dialog box, click Continue.
3.	In Registry Editor, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Tcpip6 Parameters
4.	Double-click DisabledComponents to modify the DisabledComponents entry. Note If the DisabledComponents entry is unavailable, you must create it. To do this, follow these steps: a. In the Edit menu, point to New, and then click DWORD (32-bit) Value. b. Type DisabledComponents, and then press ENTER. c. Double-click DisabledComponents.
5.	Type any one of the following values to configure the IPv6 protocol, and then click OK: a. Type 0 to enable all IPv6 components. Note The value 0 is the default setting. b. Type 0xffffffff to disable all IPv6 components, except the IPv6 loopback interface. This value also configures Windows Vista to use Internet Protocol version 4 (IPv4) instead of IPv6 in prefix policies. c. Type 0×20 to use IPv4 instead of IPv6 in prefix policies. d. Type 0×10 to disable native IPv6 interfaces. e. Type 0×01 to disable all tunnel IPv6 interfaces. f. Type 0×11 to disable all IPv6 interfaces except for the IPv6 loopback interface.

Note You must restart your computer for these changes to take affect.

Note Administrators must create an ADMX file in order to expose the settings in step 5 in a Group Policy setting.

Back to the top

For more information about how to manage Group Policy settings by using ADMX files, visit the following Microsoft TechNet Web site:

For more information about the Windows registry, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

As part of an ongoing commitment to provide detection tools and deployment recommendations for security updates, Microsoft is delivering this detection and deployment guidance for all updates that are released during a Microsoft Security Response Center (MSRC) release cycle.

This guidance contains recommendations that are based on the kinds of scenarios that may exist in various Microsoft operating system environments. This guidance includes how to use tools such as the following tools:

•	Windows Update
•	Microsoft Update
•	Office Update
•	The Microsoft Baseline Security Analyzer (MBSA)
•	Windows Server Update Services (WSUS)
•	Microsoft System Center Configuration Manager
•	Microsoft Systems Management Server (SMS)
•	The Extended Security Update Inventory Tool

This article describes the detection and deployment guidance for the security release that is dated August 12, 2008.

Back to the top

Detection and deployment

Environments that detect and deploy security updates by using Windows Update, Microsoft Update, Office Update, and Mactopia

Security updates that were released on August 12, 2008 are available through the following Web sites. Any exceptions are described in each Web site section. The products that are supported by each Web site are also listed.

NoteNot every update is available on every Web site that is listed here.

Windows Update

The products that are supported by this Web site are as follows:

•	Microsoft Windows 2000
•	Windows XP
•	Windows Server 2003
•	Windows Vista
•	Windows Server 2008

Microsoft Update

The products that are supported by this Web site are as follows:

•	Microsoft Internet Security and Acceleration Server 2004
•	Microsoft Internet Security and Acceleration Server 2006
•	Microsoft Exchange 2000 Server
•	Microsoft Exchange Server 2003
•	Microsoft Exchange Server 2007
•	Microsoft Office 2002
•	Microsoft Office 2003
•	The 2007 Microsoft Office system
•	Windows 2000
•	Windows XP
•	Windows Server 2003
•	Windows Vista
•	Windows Server 2008
•	Microsoft SQL Server 2005
•	Microsoft Forefront Client Security
•	Microsoft Visual Studio 2005

General exceptions

•	Microsoft Update does not support SQL 7.0 or Microsoft Date Engine (MSDE) 1.0.
•	Microsoft Update does not support Office 2000 components.
•	Microsoft Update does not support any Apple Macintosh products.
•	Microsoft Update does not support MSN Messenger or Windows Live Messenger.

Specific exceptions

•

955702 (MS08-050) – Microsoft Update only supports Windows Messenger 4.7 on Windows XP Service Pack 2 (SP2) and on Windows XP Service Pack 3 (SP3). No other versions of Windows are supported. Windows Messenger 5.1 is not supported.

Office Update

The products that are supported by this Web site are as follows:

•	Office 2000
•	Office 2002
•	Office 2003
•	The 2007 Office system

General exceptions

•	Office Update does not support 2007 Office components when they are installed on computers that are running Windows Vista or Windows Server 2008. You must use Microsoft Update instead.
•	Office Update does not support any Macintosh products.

Mactopia

The products that are supported by this Web site are as follows:

•	Microsoft Office 2001 for Mac
•	Microsoft Office 2004 for Mac
•	Microsoft Office X for Mac
•	Microsoft Office 2008 for Mac

Environments that detect security updates by using Microsoft Baseline Security Analyzer (MBSA) version 2.1

You can detect security updates that were released on August 12, 2008 if you use MBSA version 2.1.

NoteMBSA version 2.1 is now released and fully supports security and vulnerability assessment scans on Windows Vista and on Windows Server 2008.

General exceptions

•	MBSA version 2.1 does not support SQL 7.0 or MSDE 1.0.
•	MBSA version 2.1 does not support any Office 2000 components.
•	MBSA version 2.1 does not support any Macintosh products.
•	MBSA version 2.1 does not support Microsoft Works 8 when using an offline scan. For more information, see the Offline and Online scans section, later in this section.
•	MBSA version 2.1 does not support MSN Messenger or Windows Live Messenger.
•	MBSA version 1.2.1 and 2.0.1 are no longer supported.

Specific exceptions

•	955702 (MS08-050) – MBSA only supports Windows Messenger 4.7 on Windows XP SP2 and on Windows XP SP3. No other versions of Windows are supported. Windows Messenger 5.1 is not supported.
•	924090 (MS08-044) – MBSA only supports detection of Microsoft Works when doing an online scan. For more information, see the Offline and Online scans section, later in this section.

Offline and Online scans

•	Online scan This is when the system that is scanned by MBSA 2.1 has connectivity to Microsoft Update. This is shown in the completed scan report.
•	Offline scan This is when the system that is scanned by MBSA 2.1 is managed by WSUS or in an offline secure environment that forces the system to use the WSUSSCN2.CAB offline catalog.

Environments that detect and deploy security updates by using Windows Server Update Services (WSUS)

You can detect and deploy security updates that were released on August 12, 2008 if you use any of the following items:

•	WSUS 2.0 Service Pack 1 (SP1)
•	WSUS 3.0
•	WSUS 3.0 SP1

General exceptions

•	WSUS does not support SQL 7.0 or MSDE 1.0.
•	WSUS does not support Microsoft Works 8.
•	SUS 1.0 SP1 is no longer supported. It will not receive security updates.

Specific exceptions

•

955702 (MS08-050) – WSUS only supports Windows Messenger 4.7 on Windows XP SP2 and on Windows XP SP3. No other versions of Windows are supported. Windows Messenger 5.1 is not supported.

Environments that detect and deploy security updates by using SMS 2.0, SMS 2003, or SCCM 2007

You can detect and deploy all security updates that were released on August 12, 2008 if you use any of the following items:

•	Systems Management Server (SMS) 2.0 together with the SUS Feature Pack
•	Systems Management Server (SMS) 2003 together with the SUS Feature Pack
•	Systems Management Server (SMS) 2003 together with Inventory Tool for Microsoft Updates (ITMU)
•	System Center Configuration Manager (SCCM) 2007

General exceptions

•	Microsoft Systems Management Server 2003 SP3 includes support for, and is required for, Windows Vista and Windows Server 2008 manageability.
•	SMS 2003 together with ITMU and SCCM 2007 do not support the following products: • SQL 7.0 • MSDE 1.0 • Microsoft Works 8
•	SMS together with the SUS Feature Pack do not support the following products: • MSDE 1.0 • SQL 2005 • SQL 2008 • Exchange 2007 • Microsoft Works 8 • The 2007 Office system • Windows Internet Explorer 7 • Windows Vista • Windows Server 2008 • Any x64-based versions of Windows or of SQL • Any Itanium-based versions of Windows or of SQL
•	The SMS SUS Feature Pack, SMS ITMU, and SCCM do not support any Macintosh products.

Specific exceptions

•

955702 (MS08-050) – SMS SUSFP, SMS ITMU, and SCCM 2007 only support Windows Messenger 4.7 on Windows XP SP2 and on Windows XP SP3. No other versions of Windows are supported. Windows Messenger 5.1 is not supported.

NoteThe SMS SUS Feature Pack requires the Extended Security Update Inventory Tool to detect all the security updates.

To obtain the Extended Security Update Inventory Tool, visit the following Microsoft Web site:

Summary of detection and deployment guidance

The following table summarizes the detection and deployment guidance for each new security update.

NoteTo simplify this table, items that were listed under the general exceptions heading for each detection and deployment technology are not included.

For example, the SMS SUS Feature Pack column in this table may include a Yes. However, the security bulletin lists a Windows Vista component as affected. Previously, we would have stated in the table that the SMS SUS Feature Pack partly supported the deployment of the security update because the SMS SUS Feature Pack does not support Windows Vista components. Currently, we no longer account for that specific exception in the table because the exception is always listed as a general exception.

Security update	Bulletin	Component	Office Update	Windows Update	Microsoft Update	MBSA 2.1	WSUS 2.0 and WSUS 3.0	SMS SUS Feature Pack	SMS Inventory Tool for Microsoft Updates	System Center Configuration Manager 2007
			Detect and deploy	Detect and deploy	Detect and deploy	Detect only	Detect and deploy	Detect and deploy	Detect and deploy	Detect and deploy
955617	MS08-041	Access	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
955048	MS08-042	Word	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
954066	MS08-043	Excel	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
924090	MS08-044	Office Filters	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
953838	MS08-045	Internet Explorer	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
952954	MS08-046	Windows ICM	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
953733	MS08-047	IPsec	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
951066	MS08-048	Outlook Express/Windows Mail	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
950974	MS08-049	Event System	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
955702	MS08-050	Windows Messenger	Not applicable	Partly, see the Windows Update section	Partly, see the Microsoft Update section	Partly, see the MBSA section	Partly, see the WSUS section	Partly, see the SMS section	Partly, see the SMS Update section	Partly, see the SCCM section
949785	MS08-051	PowerPoint	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes

Rereleased security updates

There are no rereleases this month.

Back to the top

Frequently asked questions

What is Microsoft doing to provide guidance about how to deploy these updates?

We encourage system administrators to join the monthly technical Webcast to learn more about security updates. The Webcast for this security update airs on August 13, 2008 at 11:00 A.M. (Pacific Time). To register, visit the following Microsoft Web site:

What other information should I know about MBSA?

For more information about the programs that MBSA currently supports, visit the following Microsoft TechNet Web site:

Can I use SMS or System Center Configuration Manager to determine whether the updates are required?

Yes. SMS helps detect and deploy these security updates. SMS 2.0 together with the SUS Feature Pack and SMS 2003 together with SUSFP use MBSA version 1.2.1 technology for detection. Therefore, SMS 2.0 together with the SUS Feature Pack and SMS 2003 together with the SUS Feature Pack have limitations that resemble the limitations of MBSA version 1.2.1.

For more information about SMS, visit the following Microsoft Web site:

The SUS Feature Pack together with the Extended Security Update Inventory Tool is required to detect all the security updates on Microsoft Windows and on other affected Microsoft products.

For more information about the limitations of the SUS Feature Pack, click the following article number to view the article in the Microsoft Knowledge Base:

SMS 2.0 together with the SUS Feature Pack and SMS 2003 together with the SUS Feature Pack also use the Microsoft Office Inventory Tool to detect the required security updates for Microsoft Office programs such as Microsoft Word.

SMS 2003 customers can also use ITMU to detect and deploy security updates. ITMU uses technology from Microsoft Updates. For more information about ITMU, visit the following Microsoft Web site:

System Center Configuration Manager 2007 uses WSUS 3.0 for detection and deployment of these security updates. Therefore, anything that is supported by WSUS 3.0 is also supported by System Center Configuration Manager 2007.

Back to the top

Consider the following scenario:

•	On a Windows Vista-based computer, you print to an Internet Printer Protocol (IPP) printer.
•	A paper outage or a paper jam occurs.

In this scenario, the print job is canceled 30 seconds after the paper outage or the paper jam occurs. Additionally, the print queue displays an error status.

Back to the top

This problem occurs because Windows Vista has a time-out setting for print queues that are configured to use IPP. When an IPP printer does not receive data for more than 30 seconds, the print job is canceled.

Back to the top

To work around this problem, use one of the following methods.

Method 1: Resolve printer errors within 30 seconds.

Method 2: Print to a print server.

Method 3: If the printer is equipped with a hard disk, use the spool function to spool the print job to the hard disk before the print job is rendered.

Back to the top

When you try to install Windows Vista on a Microsoft Windows 2000-based computer, you receive the following error message when you try to load any storage driver:

Back to the top

This issue occurs if you must provide a driver for a storage device that is required for Windows Vista Setup.

Back to the top

To work around this issue, you must install the full version of Windows Vista. Use the Windows Vista Setup DVD to start the computer, and then install Windows Vista, instead of running Windows Vista Setup in Windows 2000.

You cannot work around this issue if you have an upgrade version of Windows Vista.

Back to the top

For more information about how to install Windows Vista, visit the following Web site:

Back to the top

In Windows Vista, ink programs may not work correctly on a digitizer. For example, you may experience symptoms that resemble the following when you use a stylus to input ink:

•	When you draw but do not lift the pen, nothing appears on the screen until you lift the pen. Then, all the ink that you used to draw appears.
•	When you try to draw straight lines, unexpected jagged lines appear.

These symptoms occur if the following conditions are true:

•	You are using a touch screen device on a Windows Vista-based computer.
•	The touch screen device is set to use a digitizer.
•	The Stylus and Touch input program was written by using the Windows Presentation Foundation (WPF) Host. The input program is hosted in Windows Media Center or in Internet Explorer.

These problems do not occur if you use a mouse instead of a stylus to input ink.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x86-based versions

File name	File version	File size	Date	Time	Platform
Presentationhostdll.dll	3.0.6920.1	106,272	01-Dec-2006	01:21	x86

Windows Vista, x64-based version

File name	File version	File size	Date	Time	Platform
Presentationhostdll.dll	3.0.6920.1	132,384	01-Dec-2006	01:11	x64

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

When you try to install a device driver by using its installation program in Windows Vista, you are unsuccessful.

You may experience this issue if the following conditions are true:

•	The driver uses an executable file-based installation program.
•	The installation program was not designed for Windows Vista.

Back to the top

Problems with executable file-based installation programs may occur if any one or more of the following conditions are true:

•	The installation program is incompatible with Windows Vista.
•	The driver is incompatible with Windows Vista.
•	An issue occurs that is related to the user rights that are required to install the driver.

Back to the top

To resolve this problem, run the driver installation program in compatibility mode. Or, use an account that has administrative credentials to run the driver installation program. You can also locate the .inf file for the driver, and then manually install the driver.

Important Before you use one of these methods, we recommend that you contact the device manufacturer or the driver manufacturer for more information about how to install the driver in Windows Vista.

Back to the top

To run the driver installation program in compatibility mode

Configure the driver installation program to run in Microsoft Windows XP Service Pack 2 compatibility mode. To do this, follow these steps:

1.	Locate the executable file for the driver installation program.
2.	Right-click the file, and then click Properties.
3.	In the PackageName Properties dialog box, click the Compatibility tab.
4.	Click to select the Run this program in compatibility mode for check box, click Windows XP (Service Pack 2) in the Run this program in compatibility mode for list, and then click OK.
5.	Double-click the executable file to start the installation program.

Back to the top

To run the driver installation program by using administrative credentials

Configure the driver installation program to run in the context of the Administrator account. To do this, follow these steps:

1.	Locate the executable file for the driver installation program.
2.	Right-click the file, and then click Run as administrator. If you are prompted for an administrator password or confirmation, type your password or click Continue.
3.	Follow the steps to install the driver.

Back to the top

To locate the .inf file and manually install the driver

Use Device Manager to install the driver. To do this, follow these steps.

Step 1: Locate the .inf file

Locate the .inf file that is included with the driver installation program. Generally, the .inf file is located in one of the following folders on the driver installation media:

•	In the same folder as the Setup program.
•	In a subfolder that is in the folder that contains the Setup program. Generally, the subfolder has a name such as Windows XP, Drivers, or WinXP.

If the driver files are packaged in a single executable file, you may be able to extract them or otherwise access them. To do this, use one of the following methods, as appropriate for your situation:

•	Use a file compression program to extract the files. If the driver files are packaged in a single executable file, you may be able to use a file compression tool such as WinZip or WinRAR to extract the contents of the driver package to a folder. The .inf file should be among the files that you extract.
•	Use the Windows Compressed Folders feature to extract the files. If you do not have the WinZip program or the WinRAR program, you may be able to extract the files by using the Windows Compressed Folders feature. To do this, change the file name extension from .exe to .zip. Then, use Windows Explorer to copy the files from the compressed folder.
•	Extract the contents from the .cab file. If there is no .inf file in the driver package, but there are one or more .cab files, you may be able to extract the contents of the .cab files. Note This method is usually unsuccessful. Typically, these kinds of driver packages are created by using the InstallShield program. The InstallShield program uses a special .cab format that is not designed to be accessed by tools such as WinZip or WinRAR.
•	Locate the files in the Temp folder. If you still cannot access the installation files, try to locate extracted temporary files. Typically, files are extracted to a local Temp folder when you install a program. You may be able to view the contents of the driver package by examining the contents of the Temp folder. To do this, follow these steps: 1. Remove the contents of the Temp folder. By removing the contents of the Temp folder, you can more easily locate the temporary files that are created when you run the driver installation program. To remove the contents of the Temp folder, follow these steps: a. Click Start, and then click Computer. b. Right-click the hard disk on which Windows Vista is installed, and then click Properties. c. In the Local Disk (DriveLetter) Properties dialog box, click the General tab, and then click Disk Cleanup. d. In the Disk Cleanup Options dialog box, click Files from all users on this computer. If you are prompted for an administrator password or confirmation, type your password or click Continue. e. Under Files to delete, click to clear all the check boxes, click to select the Temporary files check box, and then click OK. f. When you are prompted to permanently delete the files, click Delete Files. 2. Use Windows Explorer to open the Temp folder. To do this, click Start, type %temp% in the Start Search box, and then press ENTER. 3. Start the driver installation program. Note Some installation programs automatically delete the temporary files when the installation program exits. Therefore, leave the driver installation program running in the background. 4. Examine the contents of the Temp folder to locate the driver files.

Step 2: Manually install the driver

After you locate the .inf file for the driver that you want to install, manually install the new driver. To do this, follow these steps:

1.	Click Start, right-click Computer, and then click Properties.
2.	In the Tasks pane, click Device Manager. If you are prompted for an administrator password or confirmation, type your password or click Continue.
3.	In Device Manager, locate the device for which you want to install the driver. Note To display hidden devices, click Show hidden devices on the View menu.
4.	Right-click the device, and then click Update Driver Software.
5.	Click Browse my computer for driver software, click Let me pick from a list of device drivers on my computer, and then click Have Disk.
6.	In the Install From Disk dialog box, click Browse, locate an .inf file for the device driver that you want to install, and then click Open.
7.	Follow the steps in the Update Driver Software DeviceName dialog box to update the driver.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Back to the top