This update improves support in Windows Vista for the following applications:

•	IBM Rescue and Recovery with Rapid Restore 3.00
•	Rosetta Stone 2.1.3
•	MS Encarta Standard 2007
•	Family Feud Online
•	Crystal Player Professional 1.97
•	Photoshop 7.0.1
•	Total Commander 6.55
•	Sony FeliCa Port (PaSoRi) 3.0.0.0
•	Label Mighty 6
•	AVG Anti-Spyware 7.5.0.47
•	Lego Star Wars
•	HD Tach 3
•	Adobe Photoshop Elements Version 4.0
•	Digital Zenkoku Map Townpage Database 7
•	Auslogics Disk 1.0.3
•	EasyRecovery Professional Version 6.04
•	Microsoft Money 2005 Microsoft Money 2006
•	SmartInstall 2.16
•	Adobe Create Suite CS2
•	Jv16 Power Tools
•	SG TCP Optimizer 2.0.3
•	Cyber link Power Cinema 4.0
•	Google desktop 4.2006.1008
•	Roxio Easy Media Creator 7.5
•	Premiere Elements 3
•	Battlefield 2 Deluxe
•	Opera 9.02
•	Palm Desktop 6.0
•	Digital Image Suite 2006
•	Flight Simulator X
•	SmartSuite Millennium Edition – Freelance Graphics 9.8
•	LimeWire 4.12
•	Point 5.3
•	BitVise Tunnelier 4.20
•	Java Control Panel
•	ACDSee 8
•	Azureus 1.0
•	HD Tune 2.5.1
•	BeatJam 2006 SE
•	ICHITARO 2006
•	Adobe Photoshop CS 8.0
•	Arcsoft Photo Impression 5
•	J2SE Runtime Environment 5.0 Update 9
•	AOL 9.0 – x64 DevStudio 9.0
•	The Weather Channel Desktop 5.0.1
•	Absolute Poker Version 5.7
•	BitLord 1.1.5.6
•	RealPlayer 6.0.12.1700
•	Speedfan 4.31
•	Delphi 7 Professional
•	TweakNow PowerPack 2006
•	Office 2003 Web Folders
•	Outlook 2003
•	Ulead DVD MovieFactory 5 Plus
•	Virtual CD 8
•	Fireworks MX2004 7.0.2.295
•	Doranet Kids Nyugaku Jyunbi Taikenban
•	Doranet Shogaku Ichinensei Taikenban
•	Minna de TV Denwa Starter
•	Power Utility – Remote administration 3.1.0.0
•	MotionDV STUDIO 5.8J for FUJITSU OmniPass 1.0.0.1
•	Minna de TV Phone Starter 2.1.0.1
•	ColdFusion MX 7 Enterprise Edition
•	Age of Empires III
•	Age of Empires III : The WarChiefs Expansion Pack
•	Zoo Tycoon 2
•	Zoo Tycoon 2: African Adventure Expansion Pack
•	Zoo Tycoon 2: Endangered Species Expansion Pack
•	Zoo Tycoon 2: Marine Mania Expansion Pack
•	Zoo Tycoon 2: Zookeeper Collection Expansion Pack
•	Rise of Nations: Rise of Legends
•	Fable: The Lost Chapters
•	Dungeon Siege II
•	Dungeon Siege: Legends of Aranna

Back to the top

Update information

Important The update that is described in this article has been replaced by a more recent update. Apply the latest update as described in the following Microsoft Knowledge Base article:

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.

Back to the top

This problem occurs when any of the following characters are in the file name.

Character	Name
<	Left angle bracket
>	Right angle bracket
	Backslash
	Quotation mark
/	Slash mark
:	Colon
|	Vertical bar
?	Question mark
*	Asterisk
	Space

Back to the top

Back to the top

Back to the top

When a cache entry is committed, the file name is included in the cache entry. Because the CreateFileA() method on the named stream works, the WinInet.dll file does not generate an error. Instead, it uses a random name. Therefore, when the cache entry is retrieved, and the caller tries to open the file, the open operation fails because WinInet.dll file tries to open the FileName file. Instead, the WinInet.dll file must open the FileName:$DATA file.

Therefore, you cannot cache or download content when the Content-Disposition file name token contains a file name that uses one of the special characters that are listed in the Symptoms section. The new version of the WinInet.dll file resolves this problem by checking for these characters and replacing them with an underscore character.

Back to the top

Therefore, the applications that handle these events perform very slowly.

Back to the top

Hotfix information

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

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have the .NET Framework 2.0 Service Pack 1 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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.

File name	File version	File size	Date	Time	Platform
System.windows.forms.dll	2.0.50727.1819	5,173,248	14-Mar-2008	03:40	x86

Back to the top

Back to the top

Back to the top

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

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

Windows Vista, 64-bit versions

Back to the top

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

Back to the top

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

Back to the top

Windows Mobility Center does not display the Wireless Network tile if a wireless network adapter driver that is enabled on the mobile PC is not supported in Windows Vista. By design, Windows Vista works in this manner.

Back to the top

Back to the top

Consider this scenario. You use redirected folders in GPO or map a network path in a logon script and you make folders available offline in Windows Vista.  Some files may not be synchronized or you can open the files but cannot save them.

Back to the top

This behavior occurs under, but is not limited to, the following conditions:

 

The CSC Cache was corrupted because the Sync Center starts to synchronize the files and does not stopping even if you do not have the necessary permissions on the network path. Some files are synchronized, but you cannot make changes to the files. The Sync Center does not check the permissions on the root folder of a share that is mapped with deep net use. For example, permissions on the userhome folder for the mapping server userhome userhomedir are not checked.

Back to the top

1.       Make sure that users have the necessary permissions on the network path and the folders.  In the example that was mentioned earlier the user needs “List Folder /Read” permission for the userhome folder.

2.       Reinitialize the CSC Cache, as described in the following section. 

 

Reinitialize the offline files cache and database

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:

 

322756 (/Feedback.aspx?kbNumber=322756) How to back up and restore the registry in Windows

 

To reinitialize the offline folder cache in Windows Vista, follow these steps:

1.       Click Start, type regedit in the Start Search box, and then click regedit in the Programs list.

If you are prompted for an administrator password or confirmation, type your password or click Continue.

2.       Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Csc Parameters

Note If the Parameters subkey does not exist, create it.  To do this, follow these steps:

a.       Click the following registry subkey:

HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Csc

b.      On the Edit menu, point to New, and then click Key.

c.       Type Parameters, and then press ENTER.

3.       On the Edit menu, point to New, and then click DWORDValue.

4.       Type FormatDatabase, and then press ENTER.

5.       On the Edit menu, click Modify.

6.       Type 1 in the Value data box, and then click OK.

7.       Exit Registry Editor

8.       Restart the computer.

 

 

Back to the top

This behavior is by design.

Back to the top

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.

Back to the top

What time functions are updated?

The following time functions are updated by this update:

• SystemTimeToTzSpecificLocalTime() Converts a time in Coordinated Universal Time (UTC) to a specified time zone’s corresponding local time.
• TzSpecificTimeToSystemTime() Converts a local time to a time in Coordinated Universal Time (UTC).

Note The functions that are listed here use a TIME_ZONE_INFORMATION structure that specifies the START DATE and the END DATE for daylight saving time (DST). By default, the current DST rules are used when no such structure is provided.

Back to the top

When to use these functions in an application

Most date and time stamps that are created and displayed in Windows and in many applications are stored as UTC. Then, they are rendered in local time by using system APIs. Examples of these include Windows file time stamps, Outlook sent and received dates, and event logging time stamps.

Not all built-in, Windows-based applications use these newly updated APIs. However, they are available to all applications, including third-party applications. These functions are useful in many scenarios, such as a user auditing scenario in which the ability to use DST rules for previous years on a current Windows service pack is important.

Generally, if an application requires historically accurate time stamps, these functions should be used.

Back to the top

How to use these functions in an application

For information about syntax, parameters, return value, and examples on how to use these functions in an application, please visit the following Microsoft Developer Network (MSDN) Web sites:

SystemTimeToTzSpecificLocalTime Function

TzSpecificLocalTimeToSystemTime Function

Note This article supersedes article 944340, which describes an earlier version of these APIs. This update improves the performance of the functions, and enables historically accurate time-stamp lookup functionality that was introduced in 944340.

This update applies to the following Windows operating systems:

• Windows XP Service Pack 3 (SP3)
• Windows Server 2003 Service Pack 2 (SP2)
• Windows Vista Service Pack 1 (SP1)
• Windows Server 2008

Back to the top

Hotfix information for Windows XP

A supported hotfix is 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.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows XP SP3 installed.

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

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces the following hotfix:

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

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 XP with Service Pack 3, x86-based versions

Back to the top

Hotfix information for Windows Server 2003

A supported hotfix is 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have the following installed:

• Windows Server 2003 SP2

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

  889100  (/Feedback.aspx?kbNumber=889100/ ) How to obtain the latest service pack for Windows Server 2003
• The 944340 hotfix

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

  944340  (/Feedback.aspx?kbNumber=944340/ ) The time stamps are incorrect after you apply update 928388 and then change the time settings to a year that is earlier than 2007 in Windows XP and in Windows Server 2003

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces the following hotfix:

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

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 Server 2003 with Service Pack 2, x86-based versions

Windows Server 2003 with Service Pack 2, Itanium-based versions

Windows Server 2003 with Service Pack 2, x64-based versions

Back to the top

Hotfix information for Windows Vista and for Windows Server 2008

A supported hotfix is 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix on Windows Vista-based computer, you must have Windows Vista SP1 installed.

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

No prerequisites are required for Windows Server 2008-based computers.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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 and Windows Server 2008 file information notes

The .manifest files and the .mum files that are installed in each environment are listed separately in the Additional file information for Windows Server 2008 and for Windows Vista section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

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

Back to the top

Additional file information for Windows Server 2008 and 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

Back to the top

Hotfix information

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

A supported hotfix is 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Subsystem for UNIX-based Applications installed on the computer.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 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 Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
• The .manifest files and the .mum files that are installed in each environment are listed separately in the Additional file information for Windows Server 2008 and for Windows Vista section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

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

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

For all supported Itanium-based versions of Windows Server 2008

Back to the top

Back to the top

Additional file information for Windows Server 2008

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

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

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

Back to the top

For example, you may experience this problem when you use the application to return a list of 16-bit Notepad instances.

Back to the top

Hotfix information

A supported hotfix is 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 software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows Vista or Windows Vista Service Pack 1 installed.

Restart requirement

You do not have to 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

Windows Vista SP1, x86-based versions

Back to the top

Back to the top

Back to the top

• 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)

Back to the top

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.

Back to the top

Known issues with this security update

• When you install this security update on a computer that is running Windows Vista or Windows Server 2008, you may have to restart the computer two times to complete the installation. This issue may occur if you install an XML Core Services 4.0–based update together with an update that contains inbox drivers. For example, the following updates contain inbox drivers:
  956697  (/Feedback.aspx?kbNumber=956697/ ) Windows Server 2008 Hyper-V VSS writer is not used during a backup job because of corrupted or invalid virtual machine configuration files
  938371  (/Feedback.aspx?kbNumber=938371/ ) A software update is available for the Windows Vista installation components

  This issue occurs because Microsoft Windows Installer (MSI)-based installations will not continue while inbox drivers are updating. This is because inbox drivers set the impactful transaction flag and the reboot required flag at the servicing stack level for Windows Vista and Windows Server 2008. Therefore, the update for XML Core Services 4.0 will fail during installation if an update that contains an inbox driver is applied first. After the inbox driver has installed, and then the computer is restarted, the installation of security update for XML Core Services 4.0 will succeed. However, an additional restart is required to complete the installation.

  To avoid this issue, install the security update for XML Core Services 4.0 before you install the update that contains inbox drivers.

• This security update may repeatedly appear in the update list on Microsoft Update or on Windows Update if one of the system files is corrupted or if it has not been updated correctly.For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
  941729  (/Feedback.aspx?kbNumber=941729/ ) Security updates for Microsoft XML Core Services 4.0 Service Pack 2 may repeatedly appear in the update list on Microsoft Update or on Windows Update
• After you install security update 954430, certain application compatibility issues and reliability issues may occur in Microsoft XML Core Services 4.0 SP2 on a Windows Vista-based computer. To resolve these issues, install the update that is described in Microsoft Knowledge Base article 941833.
  For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
  941833  (/Feedback.aspx?kbNumber=941833/ ) An update is available that improves the compatibility and the reliability of Microsoft XML Core Services 4.0 Service Pack 2 on a Windows Vista-based computer

  An update is available that improves the compatibility and the reliability of Microsoft XML Core Service 4.0 Service Pack 2 on a Windows Vista-based computer

• The following security updates do not support the complete removal of MSXML 4.0:
  • Security update 954430 for Microsoft XML Core Services (MSXML) 4.0
  • Security update 936181 for Microsoft XML Core Services (MSXML) 4.0
  • Security update 936181 for MSXML 4.0 Service Pack 1 (SP1)
  • Security update 936181 for MSXML 4.0 Service Pack 2 (SP2)

  This situation occurs because this version of MSXML is installed in side-by-side mode. To work around this issue, follow these steps:

  1. Remove security update 954430 by using the Add or Remove Programs item in Control Panel.
  2. Delete the Msxml4.dll file from the %SystemRoot% System32 folder.
  3. Repair the previous installation of MSXML 4.0 by using the Add or Remove Programs item in Control Panel.

  The earlier versions of the Msxml4.dll file and of the Msxml4r.dll file are restored to the side-by-side folder and to the %SystemRoot% System32 folder.

• You may receive the following error message when you install security update 954430 from Windows Update:
  Could not register type library for file c: Windows system32 msxml4.dll. Contact your support personnel.

  When this error occurs, you may also notice information that resembles the following in the log file:

  Error 1911. Could not register type library for file c: Windows system32 msxml4.dll. Contact your support personnel.
  MSI (s) (20:18) [17:52:31:612]: Product: MSXML 4.0 SP2 (KB954430) — Error 1911. Could not register type library for file c: Windows system32 msxml4.dll. Contact your support personnel.
  === Logging stopped: 11/10/2006 17:53:07 ===
  MSI (c) (34:20) [17:53:07:252]: Note: 1: 1708
  MSI (c) (34:20) [17:53:07:260]: Product: MSXML 4.0 SP2 (KB954430) — Installation failed.
  MSI (c) (34:20) [17:53:07:267]: Windows Installer installed the product. Product Name: MSXML 4.0 SP2 (KB954430). Product Version: 4.20.9839.0. Product Language: 1033. Installation success or error status: 1603.
  MSI (c) (34:20) [17:53:07:313]: Grabbed execution mutex.
  MSI (c) (34:20) [17:53:07:319]: Cleaning up uninstalled install packages, if any existMSI (c) (34:20) [17:53:07:331]: MainEngineThread is returning 1603
  === Verbose logging stopped: 11/10/2006 17:53:07 ===

  To work around this problem, manually install the security update from the Microsoft Download Center, and then click Ignore when the error message is displayed. To confirm that the installation was successful, verify that the version of the Msxml4.dll file in the %SystemRoot% System32 folder is 4.20.9870.0.

Back to the top

File information

The English (United States) version of this security 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.

Back to the top

Back to the top

Back to the top

Back to the top

In this scenario, you may receive the following error message:

However, when you check the Internet connection, everything works correctly. There are no problems with the computer’s Internet connection.

Back to the top

Therefore, the computer cannot reach the Corporate Error Reporting server.

Back to the top

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

To apply this hotfix, you must have Windows Vista Service Pack 1 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

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 with SP1, x86-based versions

Windows Vista with SP2, x64-based versions

Windows Vista with SP2, Itanium-based versions

Back to the top

Back to the top

For more information about the Windows Error Reporting tool, 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

In this scenario, the application may crash.

Back to the top

Back to the top

Windows Vista hotfix information

A supported hotfix is 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 software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

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

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

Windows Vista with Service Pack 1, x86-based versions

Windows Vista, x64-based versions

Windows Vista with Service Pack 1, x64-based versions

Windows Vista with Service Pack 1, Itanium-based versions

Back to the top

Windows Server 2008 hotfix information

A supported hotfix is 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 software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

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

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 Server 2008, x86-based versions

Windows Server 2008, Itanium-based versions

Windows Server 2008, x64-based versions

Back to the top

Back to the top

For more information about how an application can provide performance counter data by using the performance counter version 2.0 APIs, visit the following Microsoft Web site:

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

Back to the top

Back to the top

Back to the top

Back to the top

Back to the top

Files in the working directory do not have the read only attribute even though they are not checked out from Visual SourceSafe.

Several scenarios can cause this behavior:

1. You may have selected make writable option when getting files from SourceSafe.

2.  You may not have Tools> Options> Local Files tab  Use Read-only Flag for files not checked out selected.

3. You may be sharing a working directory with another user that does have the file checked out.

4. You may have intentionally uncheck the read only attribute in order to do testing on the file without checking the file out.

5. You may not have NTFS permissions to set the read only in the working directory. 

6. In the dialog Tools> Options> expand Source Control and choose Environment, you set the On Edit option to do nothing and you have checked the box in the same dialogue to Allow checked in items to be edited.

Back to the top

Make sure the user has full permissions to their working folder.

In VSS  Explorer:

Open the Tools> Options> Local Files tab and make sure the Use Read-only Flag for files not checked out option has a check mark in it.

or

In Visual Studio:

 Go to Tools> Options> expand Source Control and choose Plug-in Settings.  Click on the advance button and select the Local Files tab and make sure the Use Read-only Flag for files not checked out option has a check mark in it.

In Visual Studio you have the option to be prompted when editing or to automatically check the file out.

In the dialog Tools> Options> expand Source Control and choose Environment.

Set the On Edit option to Prompt for Check out or Automatically check out depending on preference.

Move all the files from the working folder and re-issue the Get Latest (making sure you do not select make writable) and try to edit the file.

Back to the top

If you do a Get Latest, typically the files should be marked with a read only attribute.  However, sometimes the attribute is not set for some reason. Please review the cause section for most common reasons.

Sharing of working directories is not recommend because it can easily lead to the problem described in this article.

If you are editing directly from the SourceSafe Explorer

Open the Tools> Options> General tab and make sure that the Double-click on a file option is set to Ask.

You are prompted by a dialog that contains the following question in a option group:

Do you want to:

View SourceSafe’s copy of this file

Check out this file and edit it in your working folder.

Back to the top

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.

Back to the top

To move Internet Explorer favorites from the earlier version of Windows to the Internet Explorer Favorites folder in Windows Vista, follow these steps:

1.	Click Start, and then click Internet Explorer.
2.	Press ALT+C to display the Favorites Center, click Favorites, and then click the left arrow icon to pin the Favorites Center.
3.	Click Start, type %systemdrive% Windows.old in the Start Search box, and then press ENTER. Note In this step, %systemdrive% is a placeholder for the drive where you installed Windows Vista. Typically, Windows Vista is installed on drive C.
4.	Double-click Documents and Settings, double-click the User_Name folder, and then double-click Favorites. Note In this step, User_Name is a placeholder for the user account name that you used to log on to the computer.
5.	Use a drag-and-drop operation to move all files from the Favorites folder to the Internet Explorer Favorites area that you pinned in step 2.
6.	After you finish moving all files, click the x button in the Favorites Center in Internet Explorer to close the Favorites Center.

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

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.

Back to the top

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

Note After you install this hotfix package, the Choose a digital certificate dialog box appears in front of all windows as expected. Additionally, this hotfix package does not affect any other dialog box prompt that might occur as the result of other configurations.

Back to the top

This guidance contains recommendations that are based on the types 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 March 11, 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 March 11, 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.

Note Not 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 Office 2000 components.
•	Microsoft Update does not support any Apple Macintosh products.

Specific exceptionsMicrosoft Update does not support the part of security update 933103 that involves the following products:

•	Microsoft Visual Studio 2002
•	Microsoft Visual Studio 2003
•	Microsoft BizTalk Server 2000
•	Microsoft BizTalk Server 2002
•	Microsoft Commerce Server 2000
•	Microsoft Internet Security and Acceleration (ISA) Server 2000

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

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

You can detect security updates that were released on March 11, 2008 if you use MBSA version 2.0.1.

General Exceptions

•	MBSA version 2.0.1 does not support any Office 2000 components.
•	MBSA version 2.0.1 does not support any Macintosh products.
•	MBSA version 2.0.1 is not supported on Windows Vista. However, MBSA version 2.0.1 supports remote scans of computers that are running Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 931943 (/Feedback.aspx?kbNumber=931943/)Microsoft Baseline Security Analyzer (MBSA) support for Windows Vista
•	MBSA version 1.2.1 is no longer supported. It will not detect security updates that were released after October 2007.

Specific exceptionsMBSA version 2.0.1 does not support the part of security update 933103 that involves the following products:

•	Visual Studio 2002
•	Visual Studio 2003
•	BizTalk Server 2000
•	BizTalk Server 2002
•	Commerce Server 2000
•	ISA Server 2000

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

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 March 11, 2008 if you use any of the following items:

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

General Exceptions

•	WSUS 2.0 SP1, WSUS 3.0, and WSUS 3.0 SP1 do not support any Office 2000 components.
•	WSUS 2.0 SP1, WSUS 3.0, and WSUS 3.0 SP1 do not support any Macintosh products.
•	SUS 1.0 Service Pack 1 (SP1) is no longer supported. It will not receive security updates.

Specific exceptionsWSUS 2.0 SP1, WSUS 3.0, and WSUS 3.0 SP1 do not support the part of security update 933103 that involves the following products:

•	Visual Studio 2002
•	Visual Studio 2003
•	BizTalk Server 2000
•	BizTalk Server 2002
•	Commerce Server 2000
•	ISA Server 2000

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

Environments that detect and deploy security updates by using SMS 2.0, SMS 2003, or System Center Configuration Manager 2007

You can detect and deploy all security updates that were released on March 11, 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 2007

General Exceptions

•	SMS ITMU and System Center Configuration Manager do not support any Office 2000 components.
•	SMS together with the SUS Feature Pack does not support the following products: • The 2007 Office system • Windows Internet Explorer 7 • Windows Vista • Windows Server 2008 • Any x64-based versions of Windows • Any Itanium-based versions of Windows
•	The SMS SUS Feature Pack, SMS ITMU, and System Center Configuration Manager do not support any Macintosh products.

Specific exceptionsWSUS 2.0, WSUS 3.0, and WSUS 3.0 SP1 do not support the part of security update 933103 that involves the following products:

•	Visual Studio 2002
•	Visual Studio 2003
•	BizTalk Server 2000
•	BizTalk Server 2002
•	Commerce Server 2000
•	ISA Server 2000

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

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

Note To simplify this table, items that were listed under the General Exceptions heading for each detection and deployment technology are not included.

For example, the Microsoft Update column in this table may include a Yes. However, the security bulletin lists an Office 2000 component as affected. Previously, we would have stated in the table that Microsoft Update partially supported deployment of the security update. However, no Office 2000 components are supported by Microsoft Update. Therefore, we no longer account for that product in the table because it is always listed as a general exception.

Security update	Bulletin	Component	Office Update	Windows Update	Microsoft Update	MBSA 2.0.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
949029	MS08-014	Microsoft Excel	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
949031	MS08-015	Microsoft Outlook	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
949030	MS08-016	Office	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
933103	MS08-017	Microsoft Office Web Components	Partially. See Office Update section.	Not applicable	Partially. See Microsoft Update section.	Partially. See MBSA section.	Partially. See WSUS section.	Yes	Partially. See SMS section.	Partially. See System Center Configuration Manager section.

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 Thursday, March 13, 2008 12: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 does not detect, click the following article number to view the article in the Microsoft Knowledge Base:

If you installed a program that is listed in the Affected software section of a security bulletin, you may have to manually determine whether you must install the required security update. For more information about MBSA, visit the following Microsoft 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 informationabout 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 to 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

• On a Windows Vista or Windows Server 2008-based computer, you use Word 2003 or a later version of Word to create a Rich Text Format (.rtf) file.
• You develop an application that uses the RichEdit control (Riched20.dll).
• You use this application to open the .rtf file.
• You add a MergeField field to the document.
• You merge some data in the file by using the MergeField field.