Consider the following scenario:

•	You configure the Corporate Error Reporting tool on a network.
•	On this network, you run a Windows Vista-based client computer that is configured to use Corporate Error Reporting.

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

This misleading error message is generated when one of the following conditions is true:

•	The client computer that is configured to use Corporate Error Reporting is not connected to the Corporate Error Reporting server.
•	The connection between the computer and the server is unstable. For example, a VPN connection to the corporate network is unstable.

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

Back to the top

A hotfix is available to resolve this problem. After you apply this hotfix, Windows Vista checks to determine whether the computer has network connectivity any time that the computer cannot connect to the Corporate Error Reporting server. If there are no network connectivity problems, you may receive the following error message:

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

File name	File version	File size	Date	Time	Platform
Package_for_kb951858_client_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	18,940	03-May-2008	15:40	Not Applicable
Package_for_kb951858_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	11,020	03-May-2008	15:40	Not Applicable
Package_for_kb951858_client~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,715	03-May-2008	15:40	Not Applicable
Package_for_kb951858_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	18,969	03-May-2008	15:40	Not Applicable
Package_for_kb951858_sc~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,424	03-May-2008	15:40	Not Applicable
Package_for_kb951858_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	19,181	03-May-2008	15:40	Not Applicable
Package_for_kb951858_server~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,432	03-May-2008	15:40	Not Applicable
Update.mum	Not Applicable	17,925	03-May-2008	15:40	Not Applicable
X86_0a7d9a72bd630f8c8b4bc3dd0fcb320e_31bf3856ad364e35_6.0.6001.22172_none_4bf7f04c882e2928.manifest	Not Applicable	717	03-May-2008	15:40	Not Applicable
X86_microsoft-windows-errorreportingconsole_31bf3856ad364e35_6.0.6000.20828_none_54a2f3fa3ee59635.manifest	Not Applicable	40,154	03-May-2008	03:43	Not Applicable
X86_microsoft-windows-errorreportingconsole_31bf3856ad364e35_6.0.6001.22172_none_564d1f623c3a1daa.manifest	Not Applicable	40,154	03-May-2008	04:02	Not Applicable
Wercon.exe	6.0.6000.20828	1,139,712	03-May-2008	00:57	x86
Wercplsupport.dll	6.0.6000.20828	63,488	03-May-2008	03:24	x86
Wercon.exe	6.0.6001.22172	1,142,784	03-May-2008	00:59	x86
Wercplsupport.dll	6.0.6001.22172	62,976	03-May-2008	03:25	x86

Windows Vista with SP2, x64-based versions

File name	File version	File size	Date	Time	Platform
Amd64_microsoft-windows-errorreportingconsole_31bf3856ad364e35_6.0.6000.20828_none_b0c18f7df743076b.manifest	Not Applicable	40,459	03-May-2008	03:56	Not Applicable
Package_for_kb951858_client_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	19,090	03-May-2008	15:40	Not Applicable
Package_for_kb951858_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	11,098	03-May-2008	15:40	Not Applicable
Package_for_kb951858_client~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,725	03-May-2008	15:40	Not Applicable
Package_for_kb951858_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	19,119	03-May-2008	15:40	Not Applicable
Package_for_kb951858_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,432	03-May-2008	15:40	Not Applicable
Package_for_kb951858_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	19,333	03-May-2008	15:40	Not Applicable
Package_for_kb951858_server~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,440	03-May-2008	15:40	Not Applicable
Update.mum	Not Applicable	18,085	03-May-2008	15:40	Not Applicable
Wercon.exe	6.0.6000.20828	1,389,056	03-May-2008	01:18	x64
Wercplsupport.dll	6.0.6000.20828	85,504	03-May-2008	03:35	x64
Wercon.exe	6.0.6001.22172	1,393,664	03-May-2008	01:31	x64
Wercplsupport.dll	6.0.6001.22172	85,504	03-May-2008	03:53	x64

Windows Vista with SP2, Itanium-based versions

File name	File version	File size	Date	Time	Platform
Ia64_12e379df96d564605945fd7695b737d7_31bf3856ad364e35_6.0.6001.22172_none_ee95fdc75aada023.manifest	Not Applicable	719	03-May-2008	15:40	Not Applicable
Ia64_3cd8c2dbd6923032eb7e3ed30d6b8415_31bf3856ad364e35_6.0.6001.22172_none_9a09b5af92897cae.manifest	Not Applicable	719	03-May-2008	15:40	Not Applicable
Ia64_8338535c266d8af080ac6f7967b8c020_31bf3856ad364e35_6.0.6001.22172_none_2055af64f0218c4f.manifest	Not Applicable	719	03-May-2008	15:40	Not Applicable
Ia64_9d4250f1861dbd0cb174104106830e1d_31bf3856ad364e35_6.0.6001.22172_none_e25e7535b225ad4e.manifest	Not Applicable	719	03-May-2008	15:40	Not Applicable
Ia64_acb2e499fd109c28f2ccd7d7ed44c77e_31bf3856ad364e35_6.0.6001.22172_none_4c6bb015564a920b.manifest	Not Applicable	719	03-May-2008	15:40	Not Applicable
Ia64_bac8b1f4dd0e019f9690ea5b31799765_31bf3856ad364e35_6.0.6001.22172_none_818e7c139e6d02d2.manifest	Not Applicable	719	03-May-2008	15:40	Not Applicable
Ia64_cc5ce035573aa48889e86497d69dab48_31bf3856ad364e35_6.0.6001.22172_none_619a2e1a3603a960.manifest	Not Applicable	711	03-May-2008	15:40	Not Applicable
Ia64_ecda2fca812628306475b7b5ebef50f1_31bf3856ad364e35_6.0.6001.22172_none_7ea1d1da213c8c1f.manifest	Not Applicable	719	03-May-2008	15:40	Not Applicable
Ia64_microsoft-windows-e..ngconsole.resources_31bf3856ad364e35_6.0.6001.22172_de-de_d3a3dd32cfd17c54.manifest	Not Applicable	3,624	03-May-2008	04:15	Not Applicable
Ia64_microsoft-windows-e..ngconsole.resources_31bf3856ad364e35_6.0.6001.22172_en-us_7c94b32bbeaf8819.manifest	Not Applicable	3,624	03-May-2008	04:14	Not Applicable
Ia64_microsoft-windows-e..ngconsole.resources_31bf3856ad364e35_6.0.6001.22172_fr-fr_1f17860eb1a89020.manifest	Not Applicable	3,624	03-May-2008	04:17	Not Applicable
Ia64_microsoft-windows-e..ngconsole.resources_31bf3856ad364e35_6.0.6001.22172_ja-jp_ab64fb627bf58779.manifest	Not Applicable	3,624	03-May-2008	04:34	Not Applicable
Ia64_microsoft-windows-e..ngconsole.resources_31bf3856ad364e35_6.0.6001.22172_ko-kr_4eced8176e664e8f.manifest	Not Applicable	3,624	03-May-2008	04:32	Not Applicable
Ia64_microsoft-windows-e..ngconsole.resources_31bf3856ad364e35_6.0.6001.22172_zh-cn_dc1b1d99a5d1622b.manifest	Not Applicable	3,624	03-May-2008	04:32	Not Applicable
Ia64_microsoft-windows-e..ngconsole.resources_31bf3856ad364e35_6.0.6001.22172_zh-tw_e0175aefa3423e9b.manifest	Not Applicable	3,624	03-May-2008	04:33	Not Applicable
Ia64_microsoft-windows-errorreportingconsole_31bf3856ad364e35_6.0.6001.22172_none_564ec3583c3826a6.manifest	Not Applicable	40,437	03-May-2008	04:22	Not Applicable
Package_10_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	2,690	03-May-2008	15:40	Not Applicable
Package_11_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,805	03-May-2008	15:40	Not Applicable
Package_12_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,805	03-May-2008	15:40	Not Applicable
Package_13_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,805	03-May-2008	15:40	Not Applicable
Package_14_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,805	03-May-2008	15:40	Not Applicable
Package_15_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,805	03-May-2008	15:40	Not Applicable
Package_16_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,805	03-May-2008	15:40	Not Applicable
Package_17_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,805	03-May-2008	15:40	Not Applicable
Package_1_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,803	03-May-2008	15:40	Not Applicable
Package_2_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,803	03-May-2008	15:40	Not Applicable
Package_3_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,803	03-May-2008	15:40	Not Applicable
Package_4_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,803	03-May-2008	15:40	Not Applicable
Package_5_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,803	03-May-2008	15:40	Not Applicable
Package_6_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,803	03-May-2008	15:40	Not Applicable
Package_7_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,803	03-May-2008	15:40	Not Applicable
Package_8_for_kb951858~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,799	03-May-2008	15:40	Not Applicable
Package_for_kb951858_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	4,664	03-May-2008	15:40	Not Applicable
Package_for_kb951858_sc~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,427	03-May-2008	15:40	Not Applicable
Package_for_kb951858_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	4,882	03-May-2008	15:40	Not Applicable
Package_for_kb951858_server~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,435	03-May-2008	15:40	Not Applicable
Update.mum	Not Applicable	3,222	03-May-2008	15:40	Not Applicable
Wercon.exe.mui	6.0.6001.22172	48,640	03-May-2008	03:47	Not Applicable
Wercplsupport.dll.mui	6.0.6001.22172	2,560	03-May-2008	03:47	Not Applicable
Wercon.exe.mui	6.0.6001.22172	45,056	03-May-2008	03:47	Not Applicable
Wercplsupport.dll.mui	6.0.6001.22172	2,560	03-May-2008	03:47	Not Applicable
Wercon.exe.mui	6.0.6001.22172	50,176	03-May-2008	03:47	Not Applicable
Wercplsupport.dll.mui	6.0.6001.22172	2,560	03-May-2008	03:47	Not Applicable
Wercon.exe.mui	6.0.6001.22172	37,376	03-May-2008	04:13	Not Applicable
Wercplsupport.dll.mui	6.0.6001.22172	2,560	03-May-2008	04:01	Not Applicable
Wercon.exe.mui	6.0.6001.22172	36,864	03-May-2008	04:04	Not Applicable
Wercplsupport.dll.mui	6.0.6001.22172	2,560	03-May-2008	04:04	Not Applicable
Wercon.exe.mui	6.0.6001.22172	33,792	03-May-2008	04:04	Not Applicable
Wercplsupport.dll.mui	6.0.6001.22172	2,048	03-May-2008	04:04	Not Applicable
Wercon.exe.mui	6.0.6001.22172	34,304	03-May-2008	04:04	Not Applicable
Wercplsupport.dll.mui	6.0.6001.22172	2,048	03-May-2008	04:04	Not Applicable
Wercon.exe	6.0.6001.22172	2,463,232	03-May-2008	01:17	IA-64
Wercplsupport.dll	6.0.6001.22172	196,096	03-May-2008	03:40	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 Corporate Error Reporting tool, visit the following Microsoft Web site:

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

Source: Microsoft Support

Back to the top

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.

Back to the top

You are using Visual SourceSafe 6.0 or 2005.  You attempt to edit a file from within Visual Studio that has not been checked out.

Back to the top

You are able to edit the file without being prompted and without the file being automatically checked out.

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

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.

Back to the top

This article describes how to move Microsoft Internet Explorer favorites from an earlier version of Microsoft Windows to the Internet Explorer Favorites folder in Windows Vista.

When you perform a custom installation of Windows Vista, Internet Explorer favorites that you used in the earlier version of Windows are stored in the Favorites folder. The Favorites folder is located in the Windows.old folder in Windows Vista. The Windows.old folder is generated when you perform a custom installation of Windows Vista.

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:

You use Internet Explorer on a Windows Vista-based computer to open a Microsoft Office file from a site that requires digital certification. When you do this, the Choose a digital certificate dialog box appears unexpectedly behind the Internet Explorer window.

This problem is fixed in the 2007 Office system hotfix package that was released on November 19, 2008.

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.

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

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

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.

Addresses that should be shown in the Do not use proxy server for addresses beginning with section under the Internet Options Advanced Proxy Settings page are not shown. The registry entries still exist and Internet Explorer will still bypass the Web sites.

This is caused by the configuration of different proxy servers by protocol, where one is the Gopher proxy server.

 

Note Internet Explorer 7 does not support the Gopher protocol. For this problem to occur, the Gopher protocol would have to have been set in older Group Policies or from an earlier version of Internet Explorer before Internet Explorer 7 was installed.

If the configuration was set through Group Policy

 

·         Remove the value for the Gopher proxy server specified in the Group Policy.

 

If the configuration was not set through Group Policy

 

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 modify the registry entry, follow these steps:

 

1.       Click Start, click Run, and in the Open box, type the following:

 regedit

 

2.       Locate the ProxyServer value under the following key in the registry:

HKEY_CURRENT_USER Software Microsoft Windows CurrentVersion Internet Settings

3.       On the Edit menu, click Edit, String.

4.       Remove the entry associated with Gopher (for example, remove gopher=proxyserver:80;), and then click OK . 

5.       Exit Registry Editor. 

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.

Back to the top

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

Back to the top

Detection and deployment

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

Security updates that were released on June 12, 2007 are available through the following Web sites. Any exceptions are in the following list. The products that are supported by each Web site are also listed.

•	Microsoft Windows Update http://update.microsoft.com/windowsupdate (http://update.microsoft.com/windowsupdate) • Windows 2000, Windows XP, and Windows Server 2003
•	Microsoft Update http://update.microsoft.com/microsoftupdate (http://update.microsoft.com/microsoftupdate) • Windows 2000, Windows XP, and Windows Server 2003 • Microsoft Office XP and Office 2003 • Microsoft Exchange 2000 Server and Exchange Server 2003 • Microsoft Internet Security and Acceleration Server 2004 • Microsoft SQL Server 2005
•	Office Update http://officeupdate.microsoft.com (http://officeupdate.microsoft.com) • Office 2000, Office XP, and Office 2003
•	Mactopia http://www.microsoft.com/mac (http://www.microsoft.com/mac/) • Office 2001 for Mac • Office X for Mac • Office 2004 for Mac

Note Not every update is available on every Web site that is listed.

Environments that detect security updates by using MBSA version 1.2.1 or MBSA version 2.0.1

Microsoft Baseline Security Analyzer (MBSA) version 1.2.1 contains an integrated version of the Office Detection Tool (ODT). If you use MBSA 1.2.1 or MBSA version 2.0.1 to detect security updates, you can detect all the security updates that were released on June 12, 2007. Any exceptions are in the following list.

Note The ODT part of MBSA 1.2.1 is limited to local scans only.

Note MBSA 1.2.1 does not support Windows Vista, any x64-based versions of Windows, or any Itanium-based versions of Windows.

Note MBSA 2.0.1 is not supported on Windows Vista. However, MBSA 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:

•	Security update 931213 (security bulletin MS07-032) MBSA 1.2.1 does not support any part of this security update.
•	Security update 929123 (security bulletin MS07-034) MBSA 1.2.1 does not support any part of this security update. The June 12, 2007 Enterprise Scan Tool will detect the need for this update.

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

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

If you use SUS, WSUS 2.0, or WSUS 3.0 to detect and to deploy security updates, you can detect most security updates that were released on June 12, 2007. Any exceptions are in the following list.

Note SUS 1.0 SP1 does not support Windows Vista, any x64-based versions of Windows, or any Itanium-based versions of Windows.

•	Security update 927051 (security bulletin MS07-030) SUS does not support any part of this security update.
•	Security update 931213 (security bulletin MS07-032) SUS does not support any part of this security update.

Environments that detect and that deploy security updates by using SMS 2.0 together with the Security Update Inventory Tool (SUIT) or SMS 2003 together with the Inventory Tool for Microsoft Updates (ITMU)

If you use Microsoft Systems Management Server (SMS) 2.0 together with SUIT, SMS 2003 together with SUIT, or SMS 2003 together with ITMU to detect and to deploy security updates, you can detect and deploy all security updates that were released on June 12, 2007. Any exceptions are in the following list.

Note SMS together with SUIT does not support Windows Vista, any x64-based versions of Windows, or any Itanium-based versions of Windows.

•	Security update 931213 (security bulletin MS07-032) SMS SUIT does not support any part of this security update.
•	Security update 929123 (security bulletin MS07-034) SMS SUIT supports this update when you use the Extended Security Update Inventory Tool (ESUIT).

To obtain ESUIT, visit the following Microsoft Web site:

Back to the top

Summary of detection and deployment guidance

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

Security update

Bulletin

Component

Office Update

Windows Update

Microsoft Update

MBSA 1.2 and the Office Detection Tool

MBSA 2.0.1

SUS

WSUS 2.0 and WSUS 3.0

Enterprise Scan Tool

SMS Security Update Inventory Tool

SMS Inventory Tool for Microsoft Updates

Detect and deploy

Detect and deploy

Detect and deploy

Detect only

Detect only

Detect and deploy

Detect and deploy

Detect only

Detect and deploy

Detect and deploy

927051

MS07-030

Microsoft Visio

Yes

Not applicable

Yes

Yes

Yes

Not applicable

Yes

Not applicable

Yes

Yes

935840

MS07-031

Schannel

Not applicable

Yes

Yes

Yes

Yes

Yes

Yes

Not applicable

Yes

Yes

931213

MS07-032

Windows Vista

Not applicable

Yes

Yes

Not applicable

Yes

Not applicable

Yes

Not applicable

Not applicable

Yes

933566

MS07-033

Windows Internet Explorer

Not applicable

Yes

Yes

Yes

Yes

Yes

Yes

Not applicable

Yes

Yes

929123

MS07-034

Microsoft Outlook Express

Not applicable

Yes

Yes

No

Yes

Yes

Yes

Yes

Yes, with ESUIT

Yes

935839

MS07-035

Win32 API

Not applicable

Yes

Yes

Yes

Yes

Yes

Yes

Not applicable

Yes

Yes

Back to the top

Rereleased security updates

•

Security update 924667 (security bulletin MS07-012) was rereleased on June 12, 2007. For more information, see the updated security bulletin. To do this, visit the following Microsoft Web site: http://www.microsoft.com/technet/security/Bulletin/MS07-012.mspx (http://www.microsoft.com/technet/security/Bulletin/MS07-012.mspx) The information that is listed in the February 2007 detection and deployment guidance has not changed because of this security rerelease.For more information, click the following article number to view the article in the Microsoft Knowledge Base: 932703 (/Feedback.aspx?kbNumber=932703/) Detection and deployment guidance for the February 13, 2007 security release

•

Security update 925939 (security bulletin MS07-018) was rereleased on June 12, 2007. For more information, see the updated security bulletin. To do this, visit the following Microsoft Web site: http://www.microsoft.com/technet/security/Bulletin/MS07-018.mspx (http://www.microsoft.com/technet/security/Bulletin/MS07-018.mspx) The information that is listed in the April 2007 detection and deployment guidance has not changed because of this security rerelease.For more information, click the following article number to view the article in the Microsoft Knowledge Base: 935824 (/Feedback.aspx?kbNumber=935824/) Detection and deployment guidance for the April 10, 2007 security release

Back to the top

Frequently asked questions

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

A1: Microsoft encourages system administrators to join the monthly technical webcast to learn more about security updates. The webcast for this security update airs on June 13, 2007 at 11:00 A.M. (Pacific Time). To register, visit the following Microsoft Web site:

Q2: Is the Enterprise Scan Tool (EST) cumulative for SMS like ESUIT is cumulative for SMS?

A2: No, the EST is not cumulative. There are no plans to make the EST cumulative.

Q3: Can I use MBSA to determine whether these updates are required?

A3: Yes, you can use MBSA 1.2.1 and MBSA 2.0.1 to fully detect the need for the following security updates that were released on June 12, 2007.

Microsoft Knowledge Base article number	Bulletin ID	Component	Detection note
931213	MS07-032	Windows Vista	See the MBSA section
929123	MS07-034	Outlook Express	See the MBSA section

For more information about the programs that MBSA currently does not detect, click the following article numbers to view the articles in the Microsoft Knowledge Base:

You may have installed a program that is listed in the Affected software section of a security bulletin that is mentioned in the related article. In this case, 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:

Q4: Which security updates require that I use the EST together with MBSA 1.2.1 to determine which systems on my network are vulnerable?

A4: The following security update requires that you use the EST together with MBSA to determine which systems on the network are vulnerable.

Microsoft Knowledge Base article number	Bulletin ID	Component
929123	MS07-034	Outlook Express

Q5: Can I use SMS to determine whether the updates are required?

A5: Yes, SMS helps detect and deploy these security updates. SMS 2.0 and SMS 2003 together with SUIT use MBSA 1.2.1 technology for detection. Therefore, SMS 2.0 and SMS 2003 together with SUIT have limitations that resemble the limitations of MBSA 1.2.1. For more information about SMS, visit the following Microsoft Web site:

SUIT together with ESUIT are required for detection of all the security updates on Microsoft Windows and on other affected Microsoft products. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

SMS 2.0 and SMS 2003 together with SUIT 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 Web site:

Back to the top

This article describes an update that is available for Microsoft Office Outlook 2007. This update improves Internet Calendar functionality, and it improves compatibility with Internet Message Access Protocol (IMAP) servers.

Back to the top

This update for Outlook 2007 adds support for the following Internet Calendar features:

•	Users can now respond to a meeting invitation that is received in iCalendar format with a proposal for a new meeting time.
•	Extended yearly recurrence patterns are now supported for appointments or meetings that recur every year or every several years.

This update also improves the compatibility between Outlook 2007 and some IMAP e-mail servers.

Back to the top

Update information

How to obtain and to install the update

This update is available from the Microsoft Download Center. To download this update and to obtain installation instructions and deployment strategies, visit the following Microsoft Web site:

Previously released security updates and hotfixes that are contained in this update

Back to the top

How to determine whether the update is installed

This update contains files that have the versions that are listed in the following table.

File name	File version	File size	Date	Time
Contab32.dll	12.0.6300.5000	136,232	13-Dec-2007	06:56
Dlgsetp.dll	12.0.6308.5000	90,656	23-Mar-2008	02:14
Emsmdb32.dll	12.0.6307.5000	1,477,224	16-Mar-2008	08:29
Exsec32.dll	12.0.6300.5000	394,752	13-Dec-2007	06:56
Mimedir.dll	12.0.6309.5000	343,568	28-Mar-2008	03:24
Mspst32.dll	12.0.6308.5000	1,107,040	23-Mar-2008	02:14
Olmapi32.dll	12.0.6309.5000	2,953,776	28-Mar-2008	03:24
Omsmain.dll	12.0.6300.5000	663,088	13-Dec-2007	08:40
Omsxp32.dll	12.0.6300.5000	195,136	13-Dec-2007	08:40
Outlmime.dll	12.0.6309.5000	601,160	28-Mar-2008	03:24
Outlook.exe	12.0.6309.5000	12,840,480	28-Mar-2008	03:25
Outlph.dll	12.0.6300.5000	180,800	13-Dec-2007	06:56
Outlrpc.dll	12.0.6302.5000	47,624	07-Feb-2008	03:57
Outlvbs.dll	12.0.6300.5000	60,448	07-Dec-2007	07:05
Pstprx32.dll	12.0.6309.5000	416,280	28-Mar-2008	03:25
Scanpst.exe	12.0.6300.5000	40,520	07-Dec-2007	07:05
Scnpst32.dll	12.0.6308.5000	265,816	23-Mar-2008	02:14
Scnpst64.dll	12.0.6308.5000	275,552	23-Mar-2008	02:14

For information about how to distribute product updates for the 2007 Microsoft Office system, visit the following Microsoft Web site:

The Office System TechCenter contains the latest administrative updates and strategic deployment resources for all versions of Office. For more information about the Office System TechCenter, visit the following Microsoft Web site:

Back to the top

After you upgrade from Microsoft Windows XP to Windows Vista, you cannot play any of the following games in Windows Vista after you double-click the program file:

•	Internet Backgammon
•	Internet Checkers
•	Internet Hearts
•	Internet Reversi
•	Internet Spades

For example, if you locate the %SystemRoot%: Program Files MSN Gaming Zone Windows folder, and then double-click one of the following program files, the game cannot connect to the MSN Gaming Zone server:

•	Bckgzm.exe
•	Chkrzm.exe
•	Hrtzzm.exe
•	Rvsezm.exe
•	Shvlzm.exe
•	ZClientm.exe

Note These program files are present in Windows Vista if you upgraded the computer from Windows XP to Windows Vista.

Back to the top

This issue occurs because Windows Vista does not support the MSN Gaming Zone games that are listed in the Symptoms section. These games are a component of Windows XP. Additionally, these games have been removed from the Start menu and from the Games Explorer in Windows Vista. However, these programs still exist in the folder in which they were installed in Windows XP after you upgrade to Windows Vista.

Back to the top

To play the games that are listed in the Symptoms section, visit the following MSN Games Web site. Then, search for the game that you want to play.

Back to the top

For more information, see the What happened to the Internet games that used to be in Windows? topic in the Windows Vista Help file.

Back to the top

When you use the Certificates snap-in to copy a certificate together with a private key from a local user store to the local computer store, the private key is not copied.

Back to the top

This problem occurs because of a limitation of the Certificates snap-in.

Back to the top

To work around this problem, export the certificate together with the private key from the local user store to a .pfx file. Then, import the certificate from the .pfx file to the local computer store. To do this, follow these steps:

1.	Open the Certificates snap-in. To do this, follow these steps: a. Click Start, click Run, type mmc, and then click OK. b. On the File menu, click Add/Remove Snap-in. c. On the Standalone tab, click Add. d. Click Certificates, and then click Add. e. Click My user account, and then click Finish. f. Click Add, click Computer account, click Next, and then click Finish. g. Click Close, and then click OK.
2.	Export the certificate together with the private key from the local user store to a .pfx file. To do this, follow these steps: a. Expand Certificates – Current User, expand Personal, and then click Certificates. b. Right-click the certificate, click All Tasks, click Export, and then click Next. c. Click to select the Yes, export the private key check box, and then click Next two times. d. In the Password box and in the Confirm Password box, type the password, and then click Next. e. In the File name box, type the name that you want to use, click Next, and then click Finish. f. In the Certificate Export Wizard dialog box, click OK.
3.	Import the certificate from the .pfx file to the local computer store. To do this, follow these steps: a. Expand Certificates (Local Computer), and then expand Personal. b. Right-click Certificates, click All Tasks, click Import, and then click Next. c. In the File name box, type the file name that you specified in step 2e, and then click Next. d. In the Password box, type the password that you specified in step 2d, and then click Next two times. e. Click Finish, and then click OK.

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

Steps to reproduce the problem

1.	Obtain a certificate that meets the following requirements: • The certificate is issued for server authentication. • The private key is marked as exportable.
2.	Download the certificate to a local user store.
3.	Click Start, click Run, type mmc, and then click OK.
4.	On the File menu, click Add/Remove Snap-in.
5.	On the Standalone tab, click Add.
6.	Click Certificates, and then click Add.
7.	Click My user account, and then click Finish.
8.	Click Add, click Computer account, click Next, and then click Finish.
9.	Click Close, and then click OK.
10.	Export the certificate from the local user store.
11.	Copy the certificate to the local computer store.
12.	Add the certificate to Internet Information Services (IIS).

The following event may be logged in the Application log:

Event Type: Error
Event Source: Schannel
Event Category: None
Event ID: 36870
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
A fatal error occurred when attempting to access the SSL server credential private key. The error code returned from the cryptographic module is 0×80090016.

Back to the top

When you use Windows Explorer to try to remove the drive: $WINDOWS.OLD folder from a computer that has been upgraded from an earlier version of Windows to Windows Vista, Windows Explorer crashes. In this scenario, you receive the following error message:

Note The $WINDOWS.OLD folder is a hidden system folder. Sometimes, this folder has a name other than $WINDOWS.OLD. For example, this folder may be named $WINDOWS.~Q. For information about how to view this folder, see the More Information section.

Back to the top

This issue occurs if at least one of the files that Windows Vista tries to delete from the $WINDOWS.OLD folder is corrupted.

Back to the top

To resolve this issue, use one of the following methods to remove the $WINDOWS.OLD folder.

Important Make sure that you back up any important data that is located in the $WINDOWS.OLD folder before you follow these steps.

Back to the top

Method 1: Use the Disk Cleanup tool

The Disk Cleanup tool (Cleanmgr.exe) is included with Windows Vista. You can use this tool to remove the $WINDOWS.OLD folder together with its contents. To do this, follow these steps:

1.	Click Start, and then click Computer.
2.	Right-click the hard disk from which you want to remove the $WINDOWS.OLD folder, and then click Properties.
3.	Click the General tab, and then click Disk Cleanup.
4.	Click Files from all users on this computer. If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
5.	In the File to delete list, click to select the File discarded by Windows upgrade check box. Note Click to clear other check boxes, depending on the other files that you want to remove.
6.	Click OK, and then click Delete Files to confirm that you want to permanently remove the $WINDOWS.OLD folder together with its subfolders and files.

Back to the top

Method 2: Use the RD command

You can use the RD (Remove Directory) command-line command to remove the $WINDOWS.OLD folder together with its contents. To do this, follow these steps:

1.	Click Start, type cmd in the Start Search box, right-click cmd.exe in the Programs list, and then click Run as administrator. If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
2.	Type cd , and then press ENTER to change to the root directory of the current drive. Generally, this is drive C.
3.	Type drive:, and then press ENTER to change to the drive from which you want to remove the $WINDOWS.OLD folder. For example, if the $WINDOWS.OLD folder is on drive D, type d:, and then press ENTER. Note If the command prompt is already at the correct drive, skip this step.
4.	Type rd $windows.old /s, and then press ENTER to remove the $WINDOWS.OLD folder together with its subfolders.
5.	When you are prompted to confirm the removal of the $WINDOWS.OLD folder, type y, and then press ENTER.

For more information about how to use the RD command, type rd /? at a command prompt, and then press ENTER. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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

When you upgrade an earlier version of Windows to Windows Vista, the Windows Vista Setup program moves the files and the folders from the original Windows installation to a $WINDOWS.OLD folder. You can access the data in the $WINDOWS.OLD folder after the Windows Vista Setup program is finished. For more information about how the Setup program works, visit the following Microsoft Web site:

Back to the top

How to view the $WINDOWS.OLD folder

1.	Click Start, type folder options in the Start Search box, and then click Folder Options in the Programs list. If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
2.	Click the View tab, click Show hidden files and folders, and then click to clear the following two check boxes: Hide extensions for known file types Hide protected operating system files (Recommended)
3.	Click Yes to confirm that you want to display operating system files, and then click OK.

Back to the top

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

• Home users:
  http://www.microsoft.com/protect/computer/updates/bulletins/200902.mspx (http://www.microsoft.com/protect/computer/updates/bulletins/200902.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/MS09-002.msp (http://www.microsoft.com/technet/security/bulletin/MS09-002.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.

Known issues with this security update

• After you install this security update on a computer that is running Windows Vista or Windows Server 2008, you may experience issues visiting some Web pages that are in mixed Internet Zones. This problem occurs if the navigation causes Protected Mode settings to change from On to Off. For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
  967941  (/Feedback.aspx?kbNumber=967941/ ) Navigation is canceled when you browse to Web pages that are in different Internet Explorer security zones

Non-security-related fixes that are included in this security update

General distribution release (GDR) fixes

Individual updates may not be installed, depending on the version of Windows and the version of the affected application. Please view the individual articles to determine your update status.

Hotfixes

Security update 958215 packages for Windows XP and for Windows Server 2003 include Internet Explorer hotfix files and general distribution release (GDR) files. If no existing Internet Explorer files are from the hotfix environment, security update 958215 installs the GDR files.

Hotfixes are intended to correct only the problems that are described in the Microsoft Knowledge Base articles that are associated with the hotfixes. Apply hotfixes only to systems that are experiencing these specific problems.

These hotfixes may 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 these hotfixes.For more information about how to install the hotfixes that are included in security update 958215, click the following article number to view the article in the Microsoft Knowledge Base:

NoteIn addition to installing hotfix files, review the Microsoft Knowledge Base article that is associated with the specific hotfix that you have to install to determine the registry modification that is required to enable that specific hotfix.

For more information about how to determine whether your existing Internet Explorer files are from the hotfix or from the GDR environment, click the following article number to view the article in the Microsoft Knowledge Base:

Update versions for Beta products

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

Security Update for Internet Explorer 8 Beta 2 for Windows XP (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=d3442a97-3804-4f7c-9286-878aa0f00443)

Security Update for Internet Explorer 8 Beta 2 for Windows XP x64 Edition (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=ddcbaf1f-0edc-43a3-a148-f9f9b8c0df11)

Security Update for Internet Explorer 8 Beta 2 for Windows Server 2003 (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=94eb30c2-8929-4b73-ba0d-88edccaacf89)

Security Update for Internet Explorer 8 Beta 2 for Windows Server 2003 x64 Edition (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=6026fb18-5c10-4521-b673-18356eb4e8b8)

Security Update for Internet Explorer 8 Beta 2 in Windows Vista (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=db355c76-8ebd-41f7-a959-b469c4a9c831)

Security Update for Internet Explorer 8 Beta 2 in Windows Vista x64 Edition (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=0246d041-61ad-42b4-bc77-9e607ca4c41e)

Security Update for Internet Explorer 8 Beta 2 in Windows Server 2008 (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=4201774d-4bec-48eb-9c8e-dcb8fb70e9db)

Security Update for Internet Explorer 8 Beta 2 for Windows Server 2008 x64 Edition (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=de51da2d-9ec5-4f7f-a2dd-1abdff9423f8)

Security Update for Internet Explorer 8 in Windows 7 Client Pre-Beta (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=ac779505-3e59-43a7-9252-ccefec93bf89)

Security Update for Internet Explorer 8 in Windows 7 Server Pre-Beta 64-bit Itanium Edition (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=9ad094a3-ad57-40af-8106-d77600ee9075)

Security Update for Internet Explorer 8 in Windows 7 Client Pre-Beta for x64-based Systems (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=008cf3aa-2bc2-4451-a525-a04991005eb0)

Security Update for Internet Explorer 8 in Windows 7 Server Pre-Beta for x64-based Systems (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=9a1feeaf-d114-48c7-aa65-e4100075af7d)

Security Update for Internet Explorer 7 in Windows Server 2008 64-bit Itanium Edition (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=d4b4a1ac-9897-4c8a-8573-bd747a5fe490)

Security Update for Internet Explorer 7 in Windows Server 2008 Service Pack 2 (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=24d219ec-cd50-4905-8bee-dba8900de973)

Security Update for Internet Explorer 7 in Windows Server 2008 Service Pack 2 x64 Edition (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=8f05be09-a4c0-483c-a662-d9d5c03e6b6e)

Security Update for Internet Explorer 7 in Windows Vista Service Pack 2 (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=e204253e-ff7c-4410-9c34-cae2115ab48d)

Security Update for Internet Explorer 7 in Windows Vista Service Pack 2 x64 Edition (KB961260)

Download the KB961260 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=7a3c7e43-1387-42ba-bd22-a764fbcc09da)

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.

Release Date: Tuesday, February 10, 2009

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.

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). Note that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.

Windows XP and Windows Server 2003 file information

• 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 fixes that are broadly released to address widespread, critical issues. QFE service branches contain hotfixes in addition to broadly 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.

Internet Explorer 7

Internet Explorer 7 on all supported 32-bit versions of Windows XP

Internet Explorer 7 on all supported 32-bit versions of Windows Server 2003

Internet Explorer 7 on all supported Itanium-based versions of Windows Server 2003

Internet Explorer 7 on all supported x64-based versions of Windows Server 2003 and Windows XP Professional

Internet Explorer 8

Internet Explorer 8 on all supported 32-bit versions of Windows XP

Internet Explorer 8 on all supported 32-bit versions of Windows Server 2003

Internet Explorer 8 on all supported x64-based versions of Windows Server 2003 and Windows XP Professional

Windows Vista and Windows Server 2008 file information

• 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.
• GDR service branches contain only fixes that are broadly released to address widespread, critical issues. LDR service branches contain hotfixes in addition to broadly released fixes.

Internet Explorer 7

Internet Explorer 7 on all supported 32-bit versions of Windows Vista and Windows Server 2008

Internet Explorer 7 on all supported Itanium-based versions of Windows Server 2008

Internet Explorer 7 on all supported x64-based versions of Windows Vista and Windows Server 2008

Internet Explorer 8

Internet Explorer 8 on all supported 32-bit versions of Windows Vista and Windows Server 2008

Internet Explorer 8 on all supported x64-based versions of Windows Vista and Windows Server 2008

How to determine whether you are running a 32-bit or a 64-bit edition of Windows

If you are not sure which version of Windows that you are running or whether it is a 32-bit version or 64-bit version, open System Information (Msinfo32.exe), and review the value that is listed for System Type.To do this, follow these steps:

1. Click Start, and then click Run, or click Start Search.
2. Type msinfo32.exe and then press ENTER.
3. In System Information, review the value for System Type.
   • For 32-bit editions of Windows, the System Type value is x86-based PC.
   • For 64-bit editions of Windows, the System Type value is x64-based PC.

For more information about how to determine whether you are running a 32-bit or 64-bit edition of Windows, click the following article number to view the article in the Microsoft Knowledge Base: