Microsoft has released security bulletin MS08-026. The security bulletin contains all the relevant information about the security update for Microsoft Office 2004 for Mac. To view the complete security bulletin, visit the following Microsoft Web site:

Back to the top

Update details

The Office 2004 for Mac 11.4.2 Update contains several changes that improve security and stability. These changes include fixes for vulnerabilities that an attacker can use to overwrite the contents of a computer’s memory by using malicious code.

Back to the top

Prerequisites

Before you install the Office 2004 for Mac 11.4.2 Update, make sure that the computer is running Mac OS X 10.2.8 (Jaguar) or a later version of the Mac OS X operating system.

To verify that the computer meets this prerequisite, click About This Mac on the Apple menu.

Additionally, the Microsoft Office 2004 for Mac 11.4.1 Update must be installed on the computer before you install the Office 2004 for Mac 11.4.2 Update. To verify that the Office 2004 for Mac 11.4.1 Update is installed, follow these steps:

1.	On the Go menu, click Applications.
2.	Open the Microsoft Office 2004 folder, and then open the Office folder.
3.	Click the Microsoft Component Plugin file.
4.	On the File menu, click Get Info.
5.	Click General. The version information is displayed.

Back to the top

How to obtain the update

The following file is available for download from the Microsoft Download Center:

Download the Microsoft Office 2004 for Mac 11.4.2 Update package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=99F54471-CCF9-4D94-A882-A05ECD128ADC)

Release Date: May 13, 2008

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.

Notes

•

The Office 2004 for Mac 11.4.2 Update is also available from Microsoft AutoUpdate. AutoUpdate is a program that automatically keeps Microsoft software up-to-date. To use AutoUpdate, start a Microsoft Office program. Then, on the Help menu, click Check for Updates. For more information about resources for Office 2004 for Mac, visit the following Microsoft Web site: http://www.microsoft.com/mac (http://www.microsoft.com/mac)

•

The Read Me file that is included with the Office 2004 for Mac 11.4.2 Update includes the following important release information: • The minimum system requirements • Instructions for how to install the update • Information about how to troubleshoot problems that may occur when you install the update • Information about the updated files that this update adds or changes

Back to the top

Session Summary
Thursday, November 30, 2006

Windows Vista helps business users significantly increase productivity by helping them find and use information, empower mobility and collaboration, improve security, and increase overall efficiency while keeping IT costs low.

This session will discuss and demonstrate how 2007 Microsoft Office System users can leverage Windows Vista features to achieve an even greater competitive advantage. Features in Word, Excel, PowerPoint, and the other Office programs can use the search, mobility, security, and efficiency of Windows Vista to get a lot more done, much faster, and more easily.

For example, we will see how the new Ribbon in the main Office programs can quickly harness the search capability of Windows Vista online. This helps bring vital data into Word and Excel documents. We will see how this information can then be easily shared with others on mobile devices or though online collaboration tools.

This is a Level 200 (http://support.microsoft.com/default.aspx?scid=gp;en-us;webcastlevels&sd=gn) session presented by Tom Bunzel.

Tom Bunzel specializes in knowing what presenters need and how to make technology work. He has appeared on Tech TV’s Call for Help, formerly as “Professor PowerPoint” and has been a featured speaker at InfoComm and PowerPoint LIVE. Tom also works as a “technology coach” for corporations, including the Neuroscience Education Institute. He teaches regularly at West LA College Extension and privately around Southern California.

Tom has written several books, the latest being Solving the PowerPoint Predicament: Using Digital Media for Effective Communication, Sams Teach Yourself PowerPoint 2003 in 24 Hours, and Easy Digital Music for QUE Publishing. Tom Bunzel’s other books are Easy Creating CDs and DVDs, How to Use Ulead DVD Workshop, Digital Video on the PC: Video Production on Your Multimedia PC, and the update to Peachpit Press’s PowerPoint 2002/2001 for Windows & Macintosh (Visual QuickStart Guide). He is Contributing Editor to “Presentations” magazine, and also writes a weekly column as the Office Reference Guide for InformIT.com.

He can be reached through his Web site http://www.professorppt.com/ (http://www.professorppt.com/).

Viewing the Presentation

To view, click this link: View this On-demand Recording (https://www118.livemeeting.com/cc/msevents/view?id=WV113006) (Length: 1 hour 9 minutes)

Provide Feedback on this Broadcast (http://support.microsoft.com/common/survey.aspx?scid=sw;en;1326&p0=WV&p1=en-us&p2=113006)

Support WebCasts Home (http://support.microsoft.com/webcasts)

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

This article describes the 2007 Microsoft Office system issue that is fixed in the hotfix package that is dated December 16, 2008.

Issue that this hotfix package fixes

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

How to apply this hotfix

1. Download the hotfix package.
2. Extract the following file from the hotfix package:

   Office2007-kb960404-fullfile-x86-glb.exe

3. Double-click the file that you extracted in step 2 to add or replace the following files in the root of the Office installation source:
   • . Admin Oct.dll
   • . Admin Patchca.dll
   • . Admin fr-fr Octres.dll
4. Use these new files to save the Office Customization Tool updates.

Prerequisites

There are no prerequisites for installing 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 a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issue that is listed in this article.

The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.

Download information

Hotfix information

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

Consider the following scenario:

•	You have a shared folder that is available offline.
•	On a Windows Vista-based computer, in an Office application or in WordPad, you use the Open File dialog box to open an offline file that is in the shared folder.

In this scenario, the shared folder goes offline. After the shared folder goes offline, you cannot make the shared folder go online from Windows Explorer.

Back to the top

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

Back to the top

Method 1

Wait awhile. The shared folder will come online again by itself.

Back to the top

Method 2

Do not open the file by using the Open File dialog box in an Office application or in WordPad. Instead, double-click the file to open it.

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, visit the following Microsoft TechNet Web site:

Back to the top

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

You open a Microsoft Office Word 97-2003 document (*.doc) file from a shared network location. Then, you convert this file to the Word 2007 document (*.docx) file format. When you try to save the file, the Save As dialog box appears. Additionally, the original file is not removed from the shared network location when the file is closed.

This behavior is by design.

The cumulative update packages for August 2008 contain the latest hotfixes for the 2007 Office core suite applications and servers.

We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous 2007 Office suites fix release. We recommend that you consider applying the most recent fix release that contains the hotfix that you need.

Back to the top

How to obtain the August 2008 cumulative update packages

A set of supported cumulative update packages are now available from Microsoft. However, each package is intended to correct only the applications that are listed in this article. Apply the packages only to systems that are experiencing these specific problems. If you are not severely affected by any of these problems, we recommend that you wait for the next 2007 Office suites service pack that contains the hotfixes in these cumulative update packages.

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 a specific cumulative update package. To create a separate service request, visit the following Microsoft Web site:

Back to the top

Packages that are included in the August 2008 cumulative update

A link to a Microsoft Knowledge Base article that discusses each hotfix will be released as the article becomes available. To obtain a specific hotfix, please contact support and ask for the hotfix by referencing the Knowledge Base article number.

For more information about the 2007 Office suite bugs, click the following article numbers to view the articles in the Microsoft Knowledge Base.

Hotfix package name	Knowledge Base article number	Product
Access.msp	956054 (/Feedback.aspx?kbNumber=956054/) Description of the Access 2007 hotfix package (Access.msp): August 26, 2008	Access
Ace.msp	956838 (/Feedback.aspx?kbNumber=956838/) Description of the Access 2007 hotfix package (Ace.msp): August 26, 2008	Access
Excel.msp, Oart.msp	956798 (/Feedback.aspx?kbNumber=956798/) Description of the Excel 2007 hotfix package (Excel.msp, Oart.msp): August 26, 2008	Excel
Excel.msp, Xlconv.msp	956836 (/Feedback.aspx?kbNumber=956836/) Description of the Excel 2007 hotfix package (Excel.msp, Xlconv.msp): August 26, 2008	Excel Converter
Excel.msp, Xlconv.msp, Graph.msp	956511 (/Feedback.aspx?kbNumber=956511/) Description of the Excel 2007 hotfix package (Excel.msp, Xlconv.msp, Graph.msp): August 26, 2008	Excel Converter
Excel-xx-xx.msp (Localized – All Languages) Not Global	956510 (/Feedback.aspx?kbNumber=956510/) Description of the Excel 2007 hotfix package (Excel-xx-xx.msp): August 26, 2008	Excel Localized
Ifswfe.msp	956315 (/Feedback.aspx?kbNumber=956315/) Description of the Forms Server 2007 hotfix package (Ifswfe.msp): August 26, 2008	Forms Server
Ipeditor.msp;infopath.msp	956314 (/Feedback.aspx?kbNumber=956314/) Description of the InfoPath 2007 hotfix package (Ipeditor.msp, Infopath.msp): August 26, 2008	InfoPath
Coreserver.msp	956056	SharePoint Server
Gfonts.msp	956514 (/Feedback.aspx?kbNumber=956514/) Description of the 2007 Office hotfix package (Gfonts.msp): August 26, 2008	Fonts
Ime32.msp	956793 (/Feedback.aspx?kbNumber=956793/) Description of the Input Method Editor (Japanese) 2007 hotfix package (Ime32.msp): August 26, 2008	English Assist
Msdaipp.msp	956790 (/Feedback.aspx?kbNumber=956790/) Description of the 2007 Office system hotfix package (Msdaipp.msp): August 26, 2008	Internet Publishing Provider
Mso.msp	956506 (/Feedback.aspx?kbNumber=956506/) Description of the 2007 Office system hotfix package (Mso.msp): August 26, 2008	Office Core
Graph.msp, Excel.msp, Xlconv.msp, Xlview.msp	956796 (/Feedback.aspx?kbNumber=956796/) Description of the 2007 Office system hotfix package (Graph.msp, Excel.msp, Xlconv.msp, Xlview,msp): August 26, 2008	Excel Converter, Excel Viewer
Oart.msp; OartConv.msp	956058 (/Feedback.aspx?kbNumber=956058/) Description of the 2007 Office hotfix package (Oart.msp, OartConv.msp): August 26, 2008	Office Art
Outlook.msp	956059	Outlook
PowerPoint.msp	956316 (/Feedback.aspx?kbNumber=956316/) Description of the PowerPoint 2007 hotfix package (PowerPoint.msp): August 26, 2008	PowerPoint
RichEd20.msp	956801 (/Feedback.aspx?kbNumber=956801/) Description of the PowerPoint 2007 hotfix package (RichEd20.msp): August 26, 2008	Rich Edit
Project.msp	956060 (/Feedback.aspx?kbNumber=956060/) Description of the Project 2007 hotfix package (Project.msp): August 26, 2008	Project
Pjsrvapp.msp, Pjsrvwfe.msp	956061	Project Server
Visio.msp	956063 (/Feedback.aspx?kbNumber=956063/) Description of the Visio 2007 hotfix package (Visio.msp): August 26, 2008	Visio
Visio.msp (ru-ru) Localized	956837	Visio Localized (Russian)
Visio.msp, Vviewer.msp	956791 (/Feedback.aspx?kbNumber=956791/) Description of the Office Visio 2007 hotfix package (Visio.msp, Vviewer.msp): August 26, 2008	Visio Viewer
Word.msp	956064	Word
Word.msp, Wordconv.msp	956795 (/Feedback.aspx?kbNumber=956795/) Description of the Word 2007 hotfix package (Word.msp, Wordconv.msp): August 26, 2008	Word Converter
Sts.msp	956057	Windows SharePoint Services
Wssmui.msp {All languages}	957109 (/Feedback.aspx?kbNumber=957109/) Description of the Windows SharePoint Services 3.0 hotfix package (Wssmui.msp): August 26, 2008	Windows SharePoint Services

Back to the top

Prerequisites

Prerequisites are listed in the KB articles for the individual packages.

Back to the top

This article describes the Microsoft Office Project 2007 issues that are fixed in the Project 2007 hotfix package that is dated December 16, 2008.

• The issues that the hotfix package fixes.
• The prerequisites for installing the hotfix package.
• Whether you must restart the computer after you install the hotfix package.
• Whether the hotfix package is replaced by any other hotfix package.
• Whether you must make any registry changes.
• The files that the hotfix package contains.

Issues that this hotfix package fixes

This hotfix fixes the following issue:

• 959381  (/Feedback.aspx?kbNumber=959381/ ) Description of the Project 2007 hotfix package: November 12, 2008

This hotfix fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

• After you modify a lookup table, the enterprise custom fields that are based on the lookup table are not displayed correctly in Project 2007.
• When you print a project, the three-dimensional (3-D) bar shapes are not printed. Additionally, if you use the Print Preview option to preview the project, the 3-D bar shapes are not displayed.
• Project 2007 still displays a plan as checked out after the Program Manager checks in the plan. Additionally, the plan is listed as checked in on the server.
• You select the Restrict updates to Project Web Access check box on the Task Settings and Display page in Project Web Access (PWA). However, if you change the end date of a task, the actual work is changed in Project 2007.
• The cost variance for cost resources is not calculated at the resource level in either the Resource Usage view or the Task Usage view.

  Note The cost variance is calculated correctly at the task level.

• When Project 2007 connects to Project Server, the Graphs dialog box may not reflect the work or availability of the enterprise resources.

  Note To open the Graphs dialog box, click Build Team from Enterprise on the Tools menu, and then click Graphs in the Build Team for <ProjectName> dialog box.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problems that are described in this article. Apply this hotfix only to systems that are experiencing the problems 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

If you want to connect to Project Server, you must install hotfix 952000 or a later Project Server 2007 hotfix.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issue that is listed in this article.

The Global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.

Download information

Microsoft Windows Installer .msp file information

Project.msp information

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

When you click a folder in the pending approval report in Office SharePoint Server 2007 site to manually approve or reject it, you receive an http 400 error.

To resolve this problem, apply hotfix 957693. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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

Back to the top

Issue that the hotfix package fixes

This hotfix package fixes the following issue that is not previously documented in a Microsoft Knowledge Base article:

Consider the following scenario. On a computer that has the East Asian languages enabled, you have a Microsoft Office Word 2003 document. The document contains numbers that are enclosed in parentheses. Some numbers are used to number a list. You open the document in Microsoft Office Word 2007. In this scenario, you may experience a delay of 1 second to 5 seconds after you type a character in the last line of the numbered list.

Note You do not experience a delay when you type successive characters.

Back to the top

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

There are no prerequisites for installing this hotfix package.

Restart information

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

Hotfix package replacement information

This hotfix package does not replace a previously released hotfix package.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix package may not contain all the files that you must have to fully update a product to the latest build. This hotfix package contains only the files that you must have to correct the issues that are listed in this article.

The global version of this hotfix package 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.

Download information

File name	File version	File size	Date	Time	Platform
Office-kb953139-fullfile-x86-glb.exe	12.0.6300.5000	11,972,416	21-May-2008	16:27	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,243,392	21-May-2008	23:05	Not Applicable

Contents of Word.msp

File name	File version	File size	Date	Time	Platform
Msword.olb	12.0.6300.5000	768,024	07-Dec-2007	01:05	x86
Winword.exe	12.0.6315.5000	349,720	09-May-2008	20:00	x86
Wwlib.dll	12.0.6316.5000	17,494,552	21-May-2008	05:23	x86

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

Consider the following scenario:

•	You use the out of the box approval workflow with the Microsoft Office SharePoint Server 2007 picture library or with another library, such as the document library.
•	You use the Start this workflow when new item is created rule.
•	You use the Cancel this workflow when the: Document is changed rule.
•	You upload a new image file by browsing to the file and clicking OK.
•	When you are automatically redirected to the metadata screen for the file, you provide the metadata and then click OK.

In this scenario, the workflow displays the following message:

Back to the top

This problem occurs when you are redirected to the /Forms/EditForm.aspx metadata page while you are uploading to a picture library.

Note This metadata page problem is not exclusive to a picture library. This problem may also occur if you allow for management of content types on any other library, regardless of what content types are enabled. Additionally, adding certain columns to other library types, such as a document library, can cause this problem to occur.

When you click OK on the metadata entry page, the workflow sees this action as a change to the item. This unintended change to the item causes the workflow rule to cancel the workflow when the Cancel this workflow when the: Document is changed rule is enabled.

Back to the top

To work around this problem, follow these steps:

1.	From the picture library or another library, click Settings, and then click Picture Library Settings.
2.	Click Versioning Settings.
3.	Click Yes for the Require documents to be checked out before they can be edited? setting, and then click OK.

After you change these settings, a CheckIn button appears instead of an OK button on the metadata entry page when a picture item is uploaded. The CheckIn button does not cause the workflow to be canceled upon upload. This button still allows for successive change to the picture item to cancel the workflow as intended.

You can also work around this problem by clicking Cancel on the metadata page. By clicking Cancel, you receive the effect that you want on the workflow. However, this is not intuitive to the upload process and does not let the user add metadata during upload.

Another way to work around this problem is to click Upload or Upload Multiple Pictures. When you click one of these buttons, the metadata does not appear during the upload process.

Back to the top

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

Back to the top

Consider the following scenario. In a Microsoft Office Word 2007 document, you type some Hebrew text and format the text as Justified. Then you save the document in the PDF file format or in the XPS file format.

In this scenario, when you open the PDF file or the XPS file, the text is right-aligned. Additionally, if a dash appears in the text, the text that appears before the dash is right-aligned. However, the text after the dash is left-aligned. Therefore, a large blank space appears in the text.

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

To resolve this problem, follow these steps:

1. Apply hotfix 956064.

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

   956064  (/Feedback.aspx?kbNumber=956064/ ) Description of the Word 2007 hotfix package (Word.msp): August 26, 2008
2. Set the value of the UseGlyphsForExport registry entry. To do this, follow these steps:
   1. Click Start, click Run, type regedit, and then click OK.
   2. Locate and then click the following registry subkey:
      HKEY_CURRENT_USER Software Microsoft Office 12.0 Word Options
   3. On the Edit menu, point to New, and then click DWORD Value.
   4. Type UseGlyphsForExport, and then press ENTER.
   5. Right-click UseGlyphsForExport, and then click Modify.
   6. In the Value data box, type 1, and then click OK.
   7. Exit Registry Editor.

When you try to upgrade a local, non-virtualized installation of Microsoft Office 2003 to a 2007 Microsoft Office system, the installation stops responding or reports inaccurate installation information. This problem occurs if you have the Microsoft Application Virtualization 4.5 Desktop Client installed.

To work around this problem, uninstall the Application Virtualization 4.5 Desktop client before you upgrade Office 2003 to a 2007 Office system.

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

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

While running on a 64-bit version of Microsoft Windows, you build a Visual Studio 2005 or Visual Studio 2008 project with the “Register for COM Interop” option selected, and the Target CPU type is set to “Any CPU” or x64.

Back to the top

Based on the Target CPU type, one of the following conditions may occur:

1. If the Target CPU is “Any CPU”, the registry information is added to the 32-bit section of the registry. This may cause problems if you are writing extra information to the registry expect the information to be in the 64-bit section of the registry. For example, the  ComRegisterFunctionAttribute class can be used to write custom information to the registry.

 

 2. If the Target CPU is “x64” the build fails with the following error File <path to assembly> is not a valid assembly.

Back to the top

Visual Studio internally uses the 32-bit version of the assembly registration tool (Regasm.exe).

Back to the top

To work around the problem, add a post build command to call the 64-bit version of RegAsm.exe using the following steps.

1. In the project properties, select “Build Events…” from the Compile page.

 

2. Add the following post build command line

%Windir% Microsoft.NET Framework64 v2.0.50727 regasm $(TargetPath)

 

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

When you try to void a supplier prepayment in the UK version of Microsoft Office Accounting 2008, you receive the following error message:

This problem occurs if the following conditions are true:

• You used a bank account to create the supplier prepayment.
• The currency that the bank account uses differs from the currency that the supplier uses.

To resolve this problem, follow these steps:

1. On the Suppliers menu, point to Supplier Lists, and then click Purchase Invoices and Goods Received Notes.
2. On the Current View menu, click All.
3. Double-click the purchase invoice that you want to process.
4. On the Actions menu, click Transaction History.
5. Double-click the supplier payment type that you want to use.
6. On the Actions menu, click Void.

When you open a Microsoft Office Word 2007 document that is protected by a password on a network share, the document is opened as read-only. You expect to be prompted for a password when you open the document.

To resolve this issue, apply hotfix 956795 on the computers that have the document opened. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

After you apply hotfix 955572, you may receive an error message when you open an appointment in a shared calendar:

This issue may occur if the following conditions are true:

• You are the delegate in a delegate and manager scenario.
• You enable caching of shared folders.

  For more information about how to enable caching of shared folders, click the following article number to view the article in the Microsoft Knowledge Base:

  955572  (/Feedback.aspx?kbNumber=955572/ ) You cannot cache shared mail folders in Outlook 2007

To resolve this issue, apply hotfix 957692. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

This article lists the following aspects of Microsoft Visual Studio 2008 Service Pack 1 (SP1) Beta for the Visual Studio Tools for Office System (VSTO) 3.0 Runtime:

•	The known issues in this service pack and how to work around the known issues
•	The issues that may occur when you uninstall this service pack and how to roll back to the release version of Visual Studio 2008
•	The hotfixes that are included in this service pack
•	The features and the functionalities that are new, changed, or improved

Back to the top

Known issues in this service pack and how to work around the known issues

•	For multiple editions of Visual Studio 2008, Microsoft only supports a configuration in which all editions are at the same service pack level. If a computer has multiple languages, multiple editions, or both of Visual Studio 2008 installed, all editions must be at the release level or at the SP1 level to be supported by Microsoft.
•	This beta release is not applied if you have Microsoft Silverlight Beta installed in the operating system.

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

Back to the top

Issues that may occur when you uninstall this service pack and how to roll back to the release version of Visual Studio 2008

For more information about the issues that may occur when you uninstall this service pack and about how to roll back to the release version of Visual Studio 2008, see the Removal issues for all platforms section in Microsoft Knowledge Base article 945140. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Hotfixes that are included in this service pack

No hotfixes which are included in this service pack.

Back to the top

Features and functionalities that are new, changed, or improved

New features or functionalities

Document-level features are enabled for VSTO add-ins. For example, the ListObject control and managed controls are enabled.

Back to the top

Fixed issues for which hotfixes were not released

The following table lists some issues that this service pack fixes. No hotfixes were released for these issues.

Connect ID	Description
301392	The VSTO and Visual Basic for Applications Interop does not work. This behavior causes the EnableVBACallers property to force a VBA error in Visual Studio 2008.
306900	You add a TextBox control in a Microsoft Outlook Form region. Then, you try to copy, cut, or paste from the control by using the keyboard. When you do this, the TextBox control does not work.
311397	The release version of VSTO 3.0 does not release the allocated memory by itself.
328329	The data cache is corrupted when protected word customizations exist.

Back to the top

For more information about Visual Studio 2008 Service Pack 1 Beta, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

You install the 2007 Microsoft Office suite Service Pack 1 (SP1), or you install post-SP1 updates for the 2007 Office suite. Then, you run one of the following tools:

•	Microsoft Baseline Security Analyzer (MBSA) 1.2.1
•	The Office Scan Tool in Microsoft Systems Management Server (SMS) 2.0
•	The Office Update Inventory Tool 2.2

When you do this, the service pack or the updates are not detected.

Back to the top

This issue occurs because MBSA 1.2.1, the Office Scan Tool in SMS 2.0, and the Office Update Inventory Tool 2.2 are not designed to detect the 2007 Office suite SP1 or post-SP1 updates for the 2007 Office suite.

Back to the top

To resolve this issue, use one of the following tools instead of the tools that are mentioned in the Symptoms section:

•	MBSA 2.0.1 or a later version of MBSA For more information about MBSA 2.0.1, visit the following Microsoft Web site: http://www.microsoft.com/technet/security/tools/mbsahome.mspx (http://www.microsoft.com/technet/security/tools/mbsahome.mspx)
•	SMS 2003 Inventory Tool for Microsoft Updates (ITMU) For more information about ITMU, visit the following Microsoft Web site: http://technet.microsoft.com/en-us/sms/bb676783.aspx (http://technet.microsoft.com/en-us/sms/bb676783.aspx)
•	Microsoft Update To use Microsoft Update, visit the following Web site: http://update.microsoft.com/microsoftupdate/v6/default.aspx (http://update.microsoft.com/microsoftupdate/v6/default.aspx)
•	Windows Server Update Services (WSUS) For more information about WSUS, visit the following Microsoft Web site: http://technet.microsoft.com/wsus/default.aspx (http://technet.microsoft.com/wsus/default.aspx)
•	Office Update To use Office Update, visit the following Microsoft Web site: http://office.microsoft.com/officeupdate/ (http://office.microsoft.com/officeupdate) Note Office Update is not available for users who are running Windows Vista.

For more information about the supported versions of MBSA, 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

This is a sample native console application which will query the registry to verify if a specific version of the .NET Framework is installed. It will then use the CorBindToRuntimeEx API to load a specific version of the Common Language Runtime (CLR). Finally, it uses the Interfaces and methods exposed in mscorlib.tlb to load an assembly and type and execute methods.

Create a new C++ Console application named CheckCLR and replace the code in CheckCLR.cpp with the following code:

/*
    CheckCLR.cpp – A Native Code CLR Host Sample

    CheckCLR is a native console application which queries the registry to
    determine if a specific version of the .NET runtime is installed on the
    machine. It then loads the specific CLR required.

    It will then load a managed console app and execute the Main method.
    It then loads a managed assembly and executes a method.
*/
#include stdafx.h
#include <windows.h>
#include <mscoree.h>
#include <assert.h>
#include <stdio.h>
#include <tchar.h>

// Import mscorlib typelib. Using 1.0 for maximum backwards compatibility
#import C: windows Microsoft.NET Framework v1.0.3705 mscorlib.tlb auto_rename
// Link with mscoree.dll import lib.
#pragma comment(lib,mscoree.lib)

using namespace mscorlib;

int _tmain(int argc, _TCHAR* argv[])
{
    //
    // Query ‘HKEY_LOCAL_MACHINE SOFTWARE Microsoft NET Framework Setup NDP v3.5 Install’ DWORD value
    // See /Feedback.aspx?kbNumber=318785/ (/Feedback.aspx?kbNumber=318785/) for more information on .NET runtime versioning information
    //
    HKEY key = NULL;
    DWORD lastError = 0;
    lastError = RegOpenKeyEx(HKEY_LOCAL_MACHINE,TEXT(SOFTWARE Microsoft NET Framework Setup NDP v3.5),0,KEY_QUERY_VALUE,&key);
    if(lastError!=ERROR_SUCCESS) {
        _putts(TEXT(Error opening HKEY_LOCAL_MACHINE SOFTWARE Microsoft NET Framework Setup NDP v3.5));
        return 1;
    }

    DWORD type;
    BYTE data[4];
    DWORD len = sizeof(data);
    lastError = RegQueryValueEx(key,TEXT(Install),NULL,&type,data,&len);
 
    if(lastError!=ERROR_SUCCESS) {
        RegCloseKey(key);
        _putts(TEXT(Error querying HKEY_LOCAL_MACHINE SOFTWARE Microsoft NET Framework Setup NDP v3.5 Install));
        return 2;
    }

    RegCloseKey(key);

    // Was Install DWORD key value == 1 ??
    if(data[0]==1)
        _putts(TEXT(.NET Framework 3.5 is installed));
    else {
        _putts(TEXT(.NET Framework 3.5 is NOT installed));
        return 3;
    }

    // 
    // Load the runtime the 3.5 Runtime (CLR version 2.0)
    //
    LPWSTR pszVer = Lv2.0.50727;  // .NET Fx 3.5 needs CLR 2.0
    LPWSTR pszFlavor = Lwks;
    ICorRuntimeHost *pHost = NULL;

    HRESULT hr = CorBindToRuntimeEx( pszVer,       
                                                       pszFlavor,    
                                                       STARTUP_LOADER_OPTIMIZATION_SINGLE_DOMAIN | STARTUP_CONCURRENT_GC, 
                                                       CLSID_CorRuntimeHost, 
                                                       IID_ICorRuntimeHost,
                                                       (void **)&pHost);

    if (!SUCCEEDED(hr)) {
        _tprintf(TEXT(CorBindToRuntimeEx failed 0x%x n),hr);
        return 1;
    }
 
    _putts(TEXT(Loaded version 2.0.50727 of the CLR n));
 
    pHost->Start(); // Start the CLR

    //
    // Get a pointer to the default domain in the CLR
    //
    _AppDomainPtr pDefaultDomain = NULL;
    IUnknownPtr   pAppDomainPunk = NULL;

    hr = pHost->GetDefaultDomain(&pAppDomainPunk);
    assert(pAppDomainPunk); 
 
    hr = pAppDomainPunk->QueryInterface(__uuidof(_AppDomain),(void**) &pDefaultDomain);
    assert(pDefaultDomain);

    //
    // Load an Exe Assembly and call Main()
    //
    _bstr_t bstrExeName = LConsoleApplication1.exe;
    try {
        hr = pDefaultDomain->ExecuteAssembly_2(bstrExeName);
    }
    catch(_com_error& error) {
        _tprintf(TEXT(ERROR: %s n),(_TCHAR*)error.Description());
        goto exit;
    }

    /*
        Load a type from a DLL Assembly and call it

        Doing the same thing from native code as this C# code:

            System.Runtime.Remoting.ObjectHandle objptr;
            objptr = AppDomain.CurrentDomain.CreateInstanceFrom(ClassLibrary1.dll,
                                                                                           ClassLibrary1.Class1);
            object obj = objptr.Unwrap();
            Type t = obj.GetType();
            t.InvokeMember(Test,
                                   BindingFlags.InvokeMethod,
                                   null,
                                   obj,
                                   new object[0]);
    */
    try {
        _ObjectHandlePtr pObjectHandle; 
        _ObjectPtr pObject; 
        _TypePtr pType;
        SAFEARRAY* psa;

        // Create an instance of a type from an assembly
        pObjectHandle = pDefaultDomain->CreateInstanceFrom(LClassLibrary1.dll,     // no path — local directory
                                                                                      LClassLibrary1.Class1);
  
        variant_t vtobj = pObjectHandle->Unwrap();                                     // Get an _Object (as variant) from the _ObjectHandle
        vtobj.pdispVal->QueryInterface(__uuidof(_Object),(void**)&pObject);  // QI the variant for the Object iface
        pType = pObject->GetType();                                                         // Get the _Type iface
        psa = SafeArrayCreateVector(VT_VARIANT,0,0);                                // Create a safearray (0 length)
        pType->InvokeMember_3(Test,                                                     // Invoke Test method on pType
                                            BindingFlags_InvokeMethod,
                                            NULL,
                                            vtobj,
                                            psa );
        SafeArrayDestroy(psa);                                                                   // Destroy safearray
    }
    catch(_com_error& error) {
        _tprintf(TEXT(ERROR: %s n),(_TCHAR*)error.Description());
        goto exit;
    }

exit:
    pHost->Stop();
    pHost->Release();

    return 0;
}

/*** End of file CheckCLR.cpp ***/

Create a C# Console Application named ConsoleApplication1. Add a Console.WriteLine call in the Main method and output a simple string message. Build ConsoleApplication1. Copy the ConsoleApplication1.exe build target to the ouput directory where CheckCLR.exe is built. Alternatively, you can change the code above to have the full path name to where ConsoleApplication1.exe is built.

Create a C# Class Library named ClassLibrary1. In the Class1 class, add a public method named Test. In Test, add a Console.WriteLine call and output a simple string message. Build ClassLibrary1.dll. Copy the ClassLibrary1.dll build target to the outut directory where CheckCLR.exe is built. Alternatively, you can change the code above to have the full path name to where ClassLibrary1.dll is built.

After building CheckCLR, you should should be able to run CheckCLR.exe from a command prompt and see the output of the Console.WriteLine calls:

    .NET Framework 3.5 is installed
    Loaded version 2.0.50727 of the CLR

    Hello World from ConsoleApplication1.Main
    Hello World from ClassLibrary1.Class1

If running CheckCLR.exe under the debugger from your Visual C++ project, you may get could not load file or assembly error messages. In that case, copy ConsoleApplication1.exe and ClassLibrary1.dll to the folder containing the CheckCLR.sln solution file. The debugger uses that folder as the application default directory.

 

 

 

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