This article describes the Microsoft Office Word 2007 issues that are fixed in the hotfix package that is dated February 15, 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 packages.
•	Whether you must make any registry changes.
•	The files that the hotfix package contains.

Back to the top

Issues that this hotfix package fixes

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

•	Consider the following scenario: • On an Office SharePoint site, you set a document library’s document template type to Microsoft Office Word 97-2003 document (.doc). • On a client computer that is running Office Word 2007, you create a new document from the document library. In this case, when you try to save the document in Office Word 2007, the default document type that appears in the Save as type box of the Save As dialog box is Word Document (*.docx). Additionally, if you do not notice that Word Document (*.docx) is wrong document type for the document library on the SharePoint site, and then click Save in the Save As dialog box, a dialog box states that states that you are saving the document in the wrong document type . If you click Cancel in this dialog box, you notice that the Save As dialog box reappears. However, the file name is changes to some random numbers together with .tmp file name extension. For example, the file name may appear as 6AF9E345.tmp.docx.
•	In Office Word 2007, you add a XML schema to the schema library. Then, when you open or close a document that has the XML schema applied, you may notice that a memory leak occurs in Performance Monitor.
•	In Office Word 2007, you insert an object that is from an Internet address. After that, when you try to change the source of the linked object to another Internet address, you receive the following error message: You cannot use an Internet address here. Enter a path that points to a location on your computer or on the network.
•	Office Word 2007 stops responding when you try to open WordPerfect 5.1 files.
•	You embed a Word document object in a 2007 Microsoft Office file. However, you cannot save a copy of the Word document object to a network location in the Word 2007 format (.docx).

Back to the top

Hotfix information

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

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

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

Prerequisites

To apply this hotfix package, you must have Word 2007 installed.

Restart information

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

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 issues that are listed in this article.The global 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.

Download information

File name	File version	File size	Date	Time	Platform
Office-kb941468-fullfile-x86-glb.exe	12.0.6300.5000	15,670,968	28-Jan-2008	17:55	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,064,704	28-Jan-2008	18:15	Not Applicable
Wordconv.msp	Not Applicable	6,239,232	28-Jan-2008	18:15	Not Applicable

After the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:

Contents of the Word.msp file

File name	File version	File size	Date	Time	Platform
Winword.exe	12.0.6300.5000	349,720	12-Dec-2007	15:54	x86
Wwlib.dll	12.0.6300.5000	17,485,848	12-Dec-2007	15:54	x86

Contents of the Wordconv.msp file

File name	File version	File size	Date	Time	Platform
Wrd12cnv.dll	12.0.6300.5000	4,272,664	12-Dec-2007	17:08	x86
Wrd12exe.exe	12.0.6300.5000	24,584	12-Dec-2007	17:08	x86

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

Back to the top

Consider the following scenario:

•	You are running the Czech (CS-CZ) version of Windows Server 2008.
•	You start the TS Gateway Manager component, and then you click the Server Farm tab.

However, when you try to locate the Add and Remove buttons on the Server Farm tab, they appear to be missing.

Back to the top

In the Czech version of Windows Server 2008, the UI for the Server Farm tab in the TS Gateway Manager component is poorly laid out for certain display resolutions. Therefore, the Add and Remove buttons may be partly obscured. However, the functionality of these buttons remains unaffected.

The Add button is located in the upper-right corner of the window, and the Remove button is located in the lower-right corner.

Back to the top

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

Method 1

Enter information in the appropriate text boxes, and then click the corresponding buttons even if the buttons are partly obscured.

Method 2

Use the following keyboard shortcuts to access the Add and Remove buttons:

•	Press ALT+P to access the Add button.
•	Press ALT+B to access the Remove button.

Back to the top

The TS Gateway Manager has known display problems when you use a display resolution of 120 dots per inch (DPI). If you experience additional display problems in the TS Gateway Manager, you can set the display resolution to 96 DPI. To do this, follow these steps:

1.	Right-click the desktop, and then click Personalize.
2.	Click Adjust font Size (DPI), and then click Default scale (96 DPI) – fit more information.
3.	When you are prompted to restart the computer, click OK.

Back to the top

You install the 2007 Microsoft Office suite Service Pack 2 (SP2). You try to use a subselect query that has calculated members in Microsoft Office Excel 2007 on a database. The database is on a server that is running Microsoft SQL Server 2008. The query returns an unexpected error.

The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. 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.

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about the list of builds that are available after the release of SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

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

On a Windows Vista-based computer, the Microsoft ISATAP adapter appears with a yellow exclamation mark (!) next to it in Device Manager. Additionally, when you open the properties dialog box for the device, you receive an error message that resembles the following:

Back to the top

You can safely ignore this error message. This error message does not indicate a problem with the adapter. The adapter will continue to work correctly.

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

The Microsoft ISATAP device Inter Site Automatic Tunneling Address Protocol is used to help enterprises transition to an IPv6 infrastructure. The ISATAP adapter encapsulates IPv6 packets by using an IPv4 header. This functionality enables the client to transport IPv6 traffic over an IPv4 infrastructure. This approach lets organizations slowly migrate to an IPv6 infrastructure without having to spend excessive time and financial resources to convert to the new infrastructure.

Back to the top

This article describes the User Account Control (UAC) feature in Windows Vista. This article also describes how to run a program as an administrator in Windows Vista.

Back to the top

User Account Control (UAC) is a new feature that helps prevent malicious programs, also known as malware, from damaging a system. UAC stops the automatic installation of unauthorized applications. UAC also prevents unintended changes to system settings.

You receive a UAC prompt when you do any of the following:

•	Install or uninstall a program.
•	Install a driver for a device. (For example, you install the driver for a digital camera.)
•	Use the Windows Update console to install updates.
•	Configure Parental Controls.
•	Install an ActiveX control. (ActiveX controls are used to view certain Web pages.)
•	Open or change the Windows Firewall control settings.
•	Change a user account type.
•	Modify your security settings with the Security Policy Editor (Secpol.msc) snap-in.
•	Browse another user’s directory.
•	Configure Automatic Updates.
•	Restore system files that were backed up.
•	Schedule Automated Tasks.
•	Copy or move files into the Program Files directory or the Windows directory.
•	Add or remove a user account.
•	Configure Remote Desktop access.

Back to the top

How to run a program as an administrator

When you run a program function or a system function, you may receive a UAC prompt. Most of these programs are legacy programs. Newer versions of the same programs do not trigger UAC. You cannot set UAC to automatically run a program as an administrator without the user being prompted.

In Windows Vista, some programs only run correctly if you run them as an administrator. You may be able to run newer versions of the same programs without having to run them as an administrator.

Note A security risk may result by using administrative credentials to run an unknown program. Only run programs that you trust as an administrator.

Important These steps may increase your security risk. These steps may also make the computer or the network more vulnerable to attack by malicious users or by malicious software such as viruses. We recommend the process that this article describes to enable programs to operate as they are designed to or to implement specific program capabilities. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this process in your particular environment. If you decide to implement this process, take any appropriate additional steps to help protect the system. We recommend that you use this process only if you really require this process.

To run a program as an administrator, follow these steps:

1.	Right-click the icon that you use to run the program, and then click Run as administrator.
2.	When you are prompted for an administrator password or for a confirmation, type the administrator password, or click Continue.

For some program icons, the Run as administrator option is not available on the shortcut menu. For these program icons, follow these steps:

1.	Right-click the icon that you use to run the program, and then click Properties. On the Shortcut tab, the Target box contains the location and the name of the program file.
2.	Open the folder that contains the program file.
3.	Right-click the program file, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Continue.

If you must run a program as an administrator, you may want to set up the program so that you automatically run it as an administrator. To do this, follow these steps:

1.	Right-click the icon that you use to run the program, and then click Properties.
2.	On the Compatibility tab, click to select the Run this program as an administrator check box, and then click OK.

The Compatibility tab is not available for some program icons. For these program icons, follow these steps:

1.	Right-click the icon that you use to run the program, and then click Properties. On the Shortcut tab, the Target box contains the location and the name of the program file.
2.	Open the folder that contains the program file.
3.	Right-click the program file, and then click Properties.
4.	On the Compatibility tab, click to select the Run this program as an administrator check box, and then click OK.

Back to the top

In Windows Vista, you cannot install a gadget if the gadget has international characters in the file name. For example, you cannot install a gadget that has Japanese or Chinese characters in the file name.

Back to the top

This problem occurs because Windows Vista cannot extract files from some cabinet (.cab) files that contain non-ANSI characters in the file name.

Back to the top

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

Back to the top

Consider the following scenario.

•	You have a Windows Server 2008-based computer that has Hyper-V installed.
•	You create a virtual machine on the Windows Server 2008-based computer.
•	You create the virtual machine from a virtual hard disk image (.vhd file) that was created by using Microsoft Virtual Server 2005 or Microsoft Virtual PC 2007.

In this scenario, the VMBus Integration Services device does not load. When you open Device Manager on the virtual machine, a yellow triangle that has an exclamation point on it appears next to VMBus. When you double-click VMBus, the VMBus Properties dialog box displays one of the following messages:

Back to the top

This issue occurs because the hardware abstraction layer (HAL) is not automatically updated in Windows Server 2008. (This is also true in Windows Vista.)

When a virtual machine is created by using Virtual Server or Virtual PC, the Advanced Configuration and Power Interface (ACPI) HAL is used. The Integration Services require an Advanced Configuration and Power Interface (ACPI) HAL to load the VMBus device correctly.

Back to the top

To resolve this issue, follow these steps:

1.	Start the virtual machine.
2.	Click Start, click Run, type Msconfig.exe, and then click OK.
3.	In the System Configuration dialog box, click the Boot tab, and then click Advanced Options.
4.	In the BOOT Advanced Options dialog box, click to select the Detect HAL check box, and then click OK.
5.	Click Yes to restart the virtual machine.
6.	After the virtual machine is restarted, open Device Manager, and then verify that all Integration Services devices are installed.
7.	In Device Manager, expand Computer, and then verify that ACPI x86-based PC is listed as the HAL.

Note You can clear the Detect HAL check box that you selected in step 4. If the Detect HAL check box is selected, the virtual machine takes a slightly longer time to start.

Back to the top

For more information about Hyper-V technology, visit the following Microsoft Web site:

Back to the top

If a PS/2 keyboard or a PS/2 mouse is not connected to a Windows Server 2008-based computer when the computer starts, the following event is logged in the System log:

Event ID: 7026
The following boot-start or system-start driver(s) failed to load: i8042prt

Additionally, the remote console keyboard and mouse appear to the server as USB devices. In Device Manager, a black exclamation point (!) on a yellow field appears next to these devices.

Back to the top

This behavior occurs because Windows Server 2008 does not initialize the remote administration key to 1 if the emergency management console is enabled.

Back to the top

You can safely ignore the event.

Back to the top

When you run a Microsoft .NET Framework 2.0-based application, you receive a System.InvalidOperationException exception. This problem occurs if the following conditions are true:

•	You have installed security update MS 07-040 on the computer.
•	The .NET Framework 2.0-based application contains several enum types.
•	The enum types contain the XmlType attribute.
•	You set the AnonymousType field to True in the XmlType attribute.

If you have not installed security update MS 07-040 on the computer, you do not receive the exception.

If you change the AnonymousType field to False, you do not receive the exception even if you have installed security update MS 07-040.

Back to the top

Hotfix information

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

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

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

Prerequisites

To apply this hotfix, you must have the .NET Framework 2.0 SP1 installed.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.

File name	File version	File size	Date	Time	Platform
System.xml.dll	2.0.50727.1822	2,052,096	27-Mar-2008	03:36	x86

Back to the top

When this issue occurs, the call stack that is generated resembles the following:

System.InvalidOperationException was unhandledMessage=Unable to generate a temporary class (result=1). r nerror CS0266: Cannot implicitly convert type 'ConsoleApplication2.Color1?' to 'ConsoleApplication2.Color2?'. An explicit conversion exists (are you missing a cast?) r nSource=System.XmlStackTrace:at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, XmlSerializerCompilerParameters xmlParameters, Evidence evidence)at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, XmlSerializerCompilerParameters parameters, Assembly assembly, Hashtable assemblies)at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence)at System.Xml.Serialization.XmlSerializer.GenerateTempAssembly(XmlMapping xmlMapping, Type type, String defaultNamespace)at System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)at ConsoleApplication2.Program.Main(String[] args) in C: Users daroth Documents Visual Studio 2008 Projects DevDivBugs162210 ConsoleApplication2 Program.cs:line 48at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)at System.Threading.ThreadHelper.ThreadStart()InnerException: 

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

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

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

Back to the top

On a Windows Vista-based or Windows Server 2008-based computer, you have a printer on which some device fonts are installed. On the computer, you change some fonts in the font substitution table of the printer from TrueType fonts to the printer’s device fonts. However, you cannot change the settings back to the original TrueType fonts. Therefore, if you have a character that does not print correctly by using the device fonts, the correct output for that character cannot be obtained.

This problem occurs because in the printer’s Properties dialog box, a font can be removed from the font substitution table by using a null device font name. However, when the printer calls the IPrintCoreHelper::SetFontSubstitution method, the null device font name is identified as invalid. Therefore, you cannot change the settings back to the original TrueType fonts.

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.

Prerequisites

To apply this hotfix on Windows Vista-based computers, you must have Windows Vista SP1 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

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

Windows Vista and Windows Server 2008 file information notes

The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately . MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported 32-bit versions of Windows Server 2008 and of Windows Vista

For all supported 64-bit versions of Windows Server 2008 and of Windows Vista

For all supported Itanium-based versions of Windows Server 2008

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

To configure the font substitution table of the printer, follow these steps:

1. Click Start, type Printers in the Start Search box, and then click Printers.
2. Right-click the printer, and then click Properties.
3. Click the Device Settings tab.
4. Expand Font Substitution Table, and then configure the fonts.

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

For more information about the IPrintCoreHelper::SetFontSubstitution method, visit the following Microsoft Web site:

Additional file information for Windows Server 2008 and Windows Vista

Additional files for all supported 32-bit versions of Windows Server 2008 and of Windows Vista

Additional files for all supported 64-bit versions of Windows Server 2008 and of Windows Vista

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

Microsoft has released Update Rollup 5 for Microsoft Exchange Server 2007 Service Pack 1 (SP1). This article describes the following information about the update rollup:

• The issues that the update rollup fixes
• How to obtain the update rollup
• The prerequisites to install the update rollup

Issues that the update rollup fixes

Update Rollup 5 for Exchange Server 2007 SP1 fixes the issues that are described in the following Microsoft Knowledge Base articles:

• 925371  (/Feedback.aspx?kbNumber=925371/ ) Domino users cannot find meeting request attachments that are sent from Exchange 2007 users
• 939037  (/Feedback.aspx?kbNumber=939037/ ) By default, managed content settings apply to the root folder and all subfolders in an Exchange 2007 environment
• 949722  (/Feedback.aspx?kbNumber=949722/ ) Event ID 800 does not include the user name of users who ran the Get-MessageTrackingLog command in an Exchange 2007 environment
• 949895  (/Feedback.aspx?kbNumber=949895/ ) Exchange Management Shell crashes (stops responding), and Event ID 1000 is logged when you perform a cross-forest migration from Exchange Server 2003 to Exchange Server 2007 S949895
• 949901  (/Feedback.aspx?kbNumber=949901/ ) Exchange 2007 users cannot send e-mail messages to a mail-enabled public folder in a mixed Exchange 2003 and Exchange 2007 environment
• 949968  (/Feedback.aspx?kbNumber=949968/ ) Unified Messaging does not handle the diversion header correctly in Exchange Server 2007 Service Pack 1
• 950272  (/Feedback.aspx?kbNumber=950272/ ) The formatting of a plain text message is incorrect when you print the plain text message by using Outlook Web Access in an Exchange Server 2007 environment
• 951267  (/Feedback.aspx?kbNumber=951267/ ) An exception occurs in Exchange Management Console when you preview AddressList in an Exchange Server 2007 environment
• 951273  (/Feedback.aspx?kbNumber=951273/ ) The received date and the received time of IMAP messages are changed to the time of migration after you migrate mailboxes to an Exchange 2007 Service Pack 1-based server
• 951505  (/Feedback.aspx?kbNumber=951505/ ) You may receive an error message when you run the Update-SafeList cmdlet in an Exchange 2003 and Exchange 2007 mixed environment
• 951564  (/Feedback.aspx?kbNumber=951564/ ) Exchange 2007 Service Pack 1 Update Rollup 5 supports the addition of new items to context menus in Outlook Web Access 2007
• 951710  (/Feedback.aspx?kbNumber=951710/ ) You receive error messages or warnings when you change an Active Directory schema so that the Company property supports more than 64 characters
• 952097  (/Feedback.aspx?kbNumber=952097/ ) Event ID 12800 is logged on an Exchange 2007-based server: Message processing failed because there is not enough available memory (8007000E-82000387)
• 952583  (/Feedback.aspx?kbNumber=952583/ ) Japanese DBCS characters are corrupt when you reply to a message or forward a message in an Exchange Server 2007 Service Pack 1 environment
• 953619  (/Feedback.aspx?kbNumber=953619/ ) A public folder conflict message cannot be delivered, and event error 1016 is logged, when the public folder name contains DBCS characters in an Exchange Server 2007 Service Pack 1 environment
• 953787  (/Feedback.aspx?kbNumber=953787/ ) You receive an error message when you try to move Exchange 2000 mailboxes or Exchange 2003 mailboxes from one forest to an Exchange 2007 server that is located in another forest by using the Move-Mailbox command
• 953840  (/Feedback.aspx?kbNumber=953840/ ) Event ID 5000 occurs, and the IMAP4 service may crash, on a server that is running Exchange Server 2007 with Service Pack 1 when you use a third-party application to migrate POP3 and IMAP4 users
• 954036  (/Feedback.aspx?kbNumber=954036/ ) Hidden folders or files are listed when you view a UNC file server by using OWA in an Exchange 2007 environment
• 954195  (/Feedback.aspx?kbNumber=954195/ ) The task originator is not notified of task changes and task progress in an Exchange Server 2007 environment
• 954197  (/Feedback.aspx?kbNumber=954197/ ) Exchange 2007 CAS cannot copy the OAB from the OAB share on Windows Server 2008-based Exchange 2007 CCR clusters
• 954270  (/Feedback.aspx?kbNumber=954270/ ) Message class changes during conversion when a digitally signed Message Disposition Notification is received by a server that is running Exchange Server 2007 Service Pack 1
• 954451  (/Feedback.aspx?kbNumber=954451/ ) An appointment item cannot be opened by a CDOEX-based application if the item is saved by Exchange Web Service together with the Culture property in Exchange Server 2007
• 954684  (/Feedback.aspx?kbNumber=954684/ ) You cannot use an Outlook 2007 client to display or download an attachment when you access a message that includes an inline attachment from Exchange Server 2007
• 954810  (/Feedback.aspx?kbNumber=954810/ ) An Exchange 2007 room mailbox stops processing requests after the resource booking assistant receives a delegated meeting request from an Exchange 2003 user
• 954887  (/Feedback.aspx?kbNumber=954887/ ) You cannot add a Mail User or a Mail Contact to the Safe Senders list in Exchange 2007 by using OWA Client
• 955001  (/Feedback.aspx?kbNumber=955001/ ) Error message when you use the IMAP protocol to send a SEARCH command that has the CHARSET argument on an Exchange 2007 server: BAD Command Argument Error
• 955196  (/Feedback.aspx?kbNumber=955196/ ) Log files are not copied to the target server in a standby continuous replication environment in Exchange Server 2007
• 955429  (/Feedback.aspx?kbNumber=955429/ ) A VSS backup application causes the Information Store service to crash repeatedly on an Exchange 2007 Service Pack 1-based server
• 955460  (/Feedback.aspx?kbNumber=955460/ ) The start time and the end time of a meeting request are incorrect when a delegate uses Exchange Web Service to send the request in an Exchange 2007 environment
• 955480  (/Feedback.aspx?kbNumber=955480/ ) Meeting requests from external senders are displayed as Busy instead of Tentative in an Exchange 2007 environment
• 955599  (/Feedback.aspx?kbNumber=955599/ ) Event ID 10 messages fill up the Application log on an Exchange 2007 CAS server if an Exchange Server 2003 mailbox owner makes an Exchange Web Service call
• 955619  (/Feedback.aspx?kbNumber=955619/ ) A user cannot access the mailbox by using a POP client or an IMAP client through Client Access Server in an Exchange 2007 environment
• 955741  (/Feedback.aspx?kbNumber=955741/ ) A message stays in the Outbox, and the message is resent until it is deleted manually on Windows Mobile 6.1-based devices in an Exchange 2007 Service Pack 1 CAS proxying scenario
• 955946  (/Feedback.aspx?kbNumber=955946/ ) A sender receives an NDR from the Exchange 2007 server when the sender submits a private message by using an SMTP server
• 955989  (/Feedback.aspx?kbNumber=955989/ ) The SPN registration of a cluster fails, and Error event IDs 1119 and 1034 are logged in an Exchange Server 2007 Service Pack 1 environment
• 956199  (/Feedback.aspx?kbNumber=956199/ ) The last character of a user’s Chinese display name is truncated in the Offline Address Book on an Exchange 2007 server
• 956319  (/Feedback.aspx?kbNumber=956319/ ) The W3wp.exe process may crash on an Exchange 2007 CAS server after you use Entourage to send a message that is larger than 48 KB
• 956573  (/Feedback.aspx?kbNumber=956573/ ) Event ID 1032 is not logged in the Application log when users send e-mail messages while they are logged on to Outlook Web Access as another user in Exchange 2007
• 956582  (/Feedback.aspx?kbNumber=956582/ ) Exchange Server 2007 Update Rollup 3 does not update the Outlook Web Access Logon.aspx file after you modify the file
• 956613  (/Feedback.aspx?kbNumber=956613/ ) The W3wp.exe process intermittently stops responding and Event ID 1000 is logged in Exchange Server 2007 Service Pack 1
• 956709  (/Feedback.aspx?kbNumber=956709/ ) Some recurring meetings may be missing when you view the meetings using Outlook Web Access in Exchange Server 2007
• 957002  (/Feedback.aspx?kbNumber=957002/ ) The Edgetransport.exe process may crash intermittently on a server that is running Exchange Server 2007 Service Pack 1
• 957813  (/Feedback.aspx?kbNumber=957813/ ) A Non-Delivery Report is generated when you try to send a high priority message that is larger than 250 KB in an Exchange Server 2007 Service Pack 1 environment
• 957978  (/Feedback.aspx?kbNumber=957978/ ) The OAB generation is unsuccessful and Event IDs 9328 and 9373 are logged in the Application log in a Windows Server 2008-based Exchange 2007 Single-Copy cluster environment
• 958855  (/Feedback.aspx?kbNumber=958855/ ) The Edge Transport service crashes repeatedly, and an event error 1000 is logged repeatedly on a server that is running Exchange Server 2007 Service Pack 1
• 958856  (/Feedback.aspx?kbNumber=958856/ ) Event ID: 7012 occurs when you search message tracking logs on an Exchange Server 2007-based server

Update rollup information

This update rollup does not apply to the Exchange Server 2007 release to manufacturing (RTM) version. The series of update rollup packages for Exchange Server 2007 SP1 is independent of the corresponding series of update rollups for Exchange Server 2007 RTM. For a list of update rollups that apply to the Exchange Server 2007 RTM, see the Update rollups for Exchange Server 2007 RTM section in the following Microsoft Knowledge Base article:

Download information

To download and install Update Rollup 5 for Exchange Server 2007 SP1, visit the following Microsoft Update Web site:

Note Microsoft Update does not detect update rollups for Exchange Server 2007 on clustered servers that are running Exchange Server 2007.

You may want to deploy Update Rollup 5 for Exchange Server 2007 SP1 to multiple computers that are running Exchange Server 2007. Or, you may want to deploy Update Rollup 5 for Exchange Server 2007 SP1 to clustered servers that are running Exchange 2007. The update rollup is also available from the Microsoft Download Center.

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

Download the Update Rollup 5 for Exchange Server 2007 Service Pack 1 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=652ED33A-11A1-459C-8FFE-90B9CBFE7903&displaylang=en)

Release Date: November 20, 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.

Note Certain Exchange 2007-managed code services may not start after you install this update rollup. This is true if the services cannot access the following Microsoft Web site:

For more information about how to resolve or work around this issue, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about the Exchange Server 2007 servicing model, click the following article number to view the article in the Microsoft Knowledge Base:

Update replacement information

Update Rollup 5 for Exchange Server 2007 SP1 is a cumulative update. This update replaces the updates that are mentioned in the following Microsoft Knowledge Base articles:

• 945684  (/Feedback.aspx?kbNumber=945684/ ) Description of Update Rollup 1 for Exchange Server 2007 Service Pack 1
• 948016  (/Feedback.aspx?kbNumber=948016/ ) Description of Update Rollup 2 for Exchange Server 2007 Service Pack 1
• 949870  (/Feedback.aspx?kbNumber=949870/ ) Description of Update Rollup 3 for Exchange Server 2007 Service Pack 1
• 952580  (/Feedback.aspx?kbNumber=952580/ ) Description of Update Rollup 4 for Exchange Server 2007 Service Pack 1

Prerequisites

The following list contains prerequisites for the Update Rollup 5 for Exchange Server 2007 Service Pack 1:

• Install Exchange Server 2007 SP1 on the computer before you apply this update rollup.
• Remove all interim updates for Exchange Server 2007 before you apply this update rollup.

Restart requirement

The required services are automatically stopped and then restarted when you apply this update rollup.

Removal information

To remove Update Rollup 5 for Exchange Server 2007 SP1, use Add or Remove Programs in Control Panel to remove update 953467.

Important information for Outlook Web Access users about Outlook Web Access customization

When you apply an update rollup package, the update process will copy over the Outlook web access files if needed. If you have modified the logon.aspx file or other Outlook Web Access files, the customizations will be overwritten in order to ensure that Outlook Web Access is updated correctly. After you apply the update rollup package, you must re-create Outlook Web Access customization in logon.aspx.

We recommend that you always make a backup copy of any customized Outlook Web Access files before you apply the update rollup. For more information about Outlook Web Access customization details, visit the following Microsoft Web site:

If you are a CAS Proxy Deployment Guidance customer, and if you have deployed CAS-CAS proxying, apply the update rollup to the Internet-facing Client Access servers before you apply the update rollup to the non-Internet-facing Client Access servers. For other Exchange Server 2007 configurations, the order in which you apply the update rollup to the servers is not important.

For more information about CAS-CAS proxying, visit the following Microsoft Web site:

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

This article describes updates to APIs that enable Windows-based applications to retrieve historically accurate time stamps.

What time functions are updated?

The following time functions are updated by this update:

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

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

When to use these functions in an application

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

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

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

How to use these functions in an application

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

SystemTimeToTzSpecificLocalTime Function

TzSpecificLocalTimeToSystemTime Function

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

This update applies to the following Windows operating systems:

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

Hotfix information for Windows XP

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

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

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

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

Prerequisites

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

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

Restart requirement

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

Hotfix replacement information

This hotfix replaces the following hotfix:

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

File information

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

Windows XP with Service Pack 3, x86-based versions

Hotfix information for Windows Server 2003

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

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

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

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

Prerequisites

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

• Windows Server 2003 SP2

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

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

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

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

Restart requirement

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

Hotfix replacement information

This hotfix replaces the following hotfix:

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

File information

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

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

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

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

Hotfix information for Windows Vista and for Windows Server 2008

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

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

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

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

Prerequisites

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

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

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

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

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

Windows Vista and Windows Server 2008 file information notes

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

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

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

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

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

Additional file information for Windows Server 2008 and Windows Vista

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

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

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

After a resource updates a task in Project Web Access and submits the update, the task update is submitted to a project manager other than the designated status manager.

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

Microsoft has released security bulletin MS07-017. The security bulletin contains all the relevant information about the security update. This information includes file manifest information and deployment options. To view the complete security bulletin, visit one of the following Microsoft Web sites:

•	Home users: http://www.microsoft.com/athome/security/update/bulletins/200704oob.mspx (http://www.microsoft.com/athome/security/update/bulletins/200704oob.mspx)
•	IT professionals: http://www.microsoft.com/technet/security/bulletin/ms07-017.mspx (http://www.microsoft.com/technet/security/bulletin/ms07-017.mspx)

Back to the top

Known issues

•

Microsoft is aware of an issue that affects a limited number of printer drivers. When you try to print by using one of these drivers, you may experience the following symptoms: • Your computer automatically restarts. • After you log on, you receive the following error message: Microsoft Windows The system has recovered from a serious error.A log of this error has been created. Please tell Microsoft about this problem.We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. When you click the link at the bottom of the message box, you see error signature information that resembles the following: BCCode : 0×0000007f (0×00000000, 0×00000000, 0×00000000, 0×00000000) OSVer : 5_1_2600 SP : 0_0 Product : 256_1 • You receive the following Stop error message: A problem has been detected and Windows has been shut down to prevent damage to your computer… Technical information: *** Stop 0×0000007f (0×00000000, 0×00000000, 0×00000000, 0×00000000) UNEXPECTED_KERNEL_MODE_TRAP For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: 935843 (/Feedback.aspx?kbNumber=935843/) Stop 0×0000007F error when you print from Windows XP or Windows 2000 with GDI security update 925902 installed

•

After you install this security update on a computer that is running Windows XP with Service Pack 2, certain third-party applications may not start. Additionally, you receive an error message that resembles the following: application_executable_name – Illegal System DLL Relocation The system DLL user32.dll was relocated in memory. The application will not run properly. The relocation occurred because the DLL C: Windows System32 Hhctrl.ocx occupied an address range reserved for Windows system DLLs. The vendor supplying the DLL should be contacted for a new DLL. For more information about this issue, and to see a list of third-party programs that Microsoft has confirmed are affected by this problem, click the following article number to view the article in the Microsoft Knowledge Base: 935448 (/Feedback.aspx?kbNumber=935448/) Certain programs may not start, and you receive an error message on a computer that is running Windows XP Service Pack 2: Illegal System DLL Relocation If you receive a similar message when you use other programs, install update 935448. If we confirm that other programs are affected by this problem, we will update Microsoft Knowledge Base article 935448 with more information.

Back to the top

The revision number and the review dates for this article may reflect minor editorial revisions or structural revisions to this content. The major technical revisions to this content are listed in this table.

Date	Revisions
April 17, 2007	Updated the Known issues section to include information about a Stop error that you may receive after you install this security update. Added this table.

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

Back to the top

When a program stops responding in Windows Vista, top-level windows that are owned by the program are supposed to be replaced by a ghost window until the program resumes. When the program resumes, the ghost windows are replaced by the program windows. However, in some cases, the program windows may appear corrupted when the program resumes. This problem may occur if the following conditions are true:

•	The program window is transparent and uses the WS_EX_LAYERED extended window style.
•	The program window was replaced with a ghost window when the program stopped responding.

For example, when this problem occurs, the program window is not correctly repainted, and instead contains information that previously appeared in the ghost window.

Back to the top

To resolve this problem, make sure that threads that own top-level windows consistently process windows messages.

Alternatively, you can call the DisableProcessWindowsGhosting function to disable window ghosting for the affected application. You can also use the NoGhost compatibility fix in the Application Compatibility Toolkit.

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

If a top-level window stops responding to messages for more than several seconds, the system considers the window to be unresponsive. In this case, the system hides the window. The system replaces the window with a ghost window that has the same Z order, location, size, and visual attributes. This behavior lets users do the following:

•	Move the window
•	Resize the window
•	Close the window

However, these are the only actions that are available because the application is actually not responding.

Back to the top

You are running a Microsoft Exchange Server environment that includes Exchange Server 2007. You are using Microsoft Office Outlook 2007 or Microsoft Office Outlook 2003 in cached mode on a client computer. You send an e-mail message from Outlook on the client computer to a non-Simple Mail Transfer Protocol (SMTP) address. For example, you address the e-mail message to an address, such as FAX. In this scenario, you receive a non-deliverable report (NDR) message that resembles the following message:

This problem can occur in several circumstances. Outlook generates an NDR message when one of the following conditions is true:

• If you do not have an SMTP connector that includes the required address space type.
• If you have an address space that is scoped to the whole Exchange organization in a custom connector, and the custom connector is configured on a computer that is running Exchange 2000 Server or an Exchange Server 2003.

To resolve this problem, follow these steps:

1. Create a new Send connector on the Exchange Server 2007 computer. Make sure that this connector includes the required custom address space type and that the connector points to a smart host. For more information about how to create a Send connector in Exchange Server 2007, visit the following Microsoft Web site:
   http://technet.microsoft.com/en-us/library/aa998814.aspx (http://technet.microsoft.com/en-us/library/aa998814.aspx)
2. Restart the Microsoft Exchange Information Store service in the Services snap-in. This updates the registry entry on the client.
3. Restart Outlook.
4. Send e-mail to the custom address.

Outlook 2007 and Outlook 2003 maintain a list of allowed address types in the registry. Outlook hands over messages that are addressed to an allowed address type to Exchange Server for further processing. When messages are addressed to an address type that is not included in the allowed list, Outlook does not reference Exchange Server but immediately returns an NDR message.

This list in the registry is refreshed every time that Outlook starts a MAPI session in cached mode. This list is stored in the 01026687 registry entry under the following registry subkey:

For more information about address spaces and connector scope, visit the following Microsoft Web site, and see the Address Spaces and Connector Scope section:

You perform one of the following operations on a Windows Vista-based computer:

•	Connect to a shared printer on the network, and then run the Common Scenario Stress with IO test in Driver Test Manager (DTM).
•	Print to a shared printer on the network.
•	Perform a power management operation. For example, you put the computer to sleep or into hibernation. Or, you wake the computer from sleep or from hibernation.

In this scenario, you receive a Stop error message that resembles the following:

Back to the top

This problem occurs if the I/O queue of the Storport.sys driver is blocked. In this scenario, certain I/O requests cannot be sent.

Note Not all Stop 0×0000009F error messages have the same symptoms and cause as those that are discussed in this article.

Back to the top

Hotfix information

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

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

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

File information

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

Windows Vista, x86-based versions

File name	File version	File size	Date	Time	Platform
Update.mum	Not Applicable	1,995	18-May-2007	11:12	Not Applicable
X86_2d93f1d2517e3c90ded3a286c93b9b1d_31bf3856ad364e35_6.0.6000.20601_none_3b9537712a7aa424.manifest	Not Applicable	696	18-May-2007	11:12	Not Applicable
X86_microsoft-windows-storport_31bf3856ad364e35_6.0.6000.20601_none_2620ab324c2510dc.manifest	Not Applicable	2,992	18-May-2007	11:14	Not Applicable
Storport.sys	6.0.6000.20601	120,504	18-May-2007	02:43	x86

Windows Vista, 64-bit versions

File name	File version	File size	Date	Time	Platform
Amd64_d14d4191791ee3b7c854f38ab5f34b32_31bf3856ad364e35_6.0.6000.20601_none_7866df545b219236.manifest	Not Applicable	700	18-May-2007	11:12	Not Applicable
Amd64_microsoft-windows-storport_31bf3856ad364e35_6.0.6000.20601_none_823f46b604828212.manifest	Not Applicable	3,247	18-May-2007	11:18	Not Applicable
Update.mum	Not Applicable	2,007	18-May-2007	11:12	Not Applicable
Storport.sys	6.0.6000.20601	135,864	18-May-2007	03:26	x64

Back to the top

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

Back to the top

The symptoms of a Stop error message may vary depending on the failure options that are configured in Windows. For more information about how to configure system failure options, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

For more information about terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top