"0xC00E5201" error code occurs when you try to create an .msp file in Windows 7

S’applique à : Windows 7

Symptoms


Consider the following scenario:
  • You have a computer that is running Windows 7.
  • You use the Microsoft Windows Platform Software Development Kit (SDK) utility (Msimsp.exe) to generate a Windows Installer patch (.msp) file. The MSP file contains many files.
In this scenario, the Msimsp.exe utility does not generate the .msp file. Additionally, you receive the following error message:
Failed to create patch. Error code: 0xC00E5201

Cause


This issue occurs because Msimsp.exe reaches a size of 4 MB that is the maximum heap size limit for compound files. Therefore, Msimsp.exe cannot generate the path file.

Resolution


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, you must be running Windows 7.

Registry information

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

Restart requirement

You may 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 global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    0.16xxx
    Windows 7RTMGDR
    6.1.760
    0.20xxx
    Windows 7RTMLDR
  • GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Msi.dll5.0.7600.207982,341,37611-Sep-201007:22x86
Msimsg.dll5.0.7600.1638525,08814-Jul-200901:07x86
For all supported x64-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Msi.dll5.0.7600.207983,211,77611-Sep-201008:45x64
Msimsg.dll5.0.7600.1638525,08814-Jul-200901:29x64
Msi.dll5.0.7600.207982,341,37611-Sep-201007:22x86
Msimsg.dll5.0.7600.1638525,08814-Jul-200901:07x86

Status


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

More Information


For more information about Msimsp.exe, visit the following Microsoft website:For more information about Patchwiz.dll, visit the following Microsoft website: For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
917465 The Msimsp.exe utility may generate a stack error on a Windows Server 2003-based computer
936359 Error message when you try to use Msimsp.exe to generate an .msp file in Windows Server 2003: "File to create patch. Error code: 0x30."
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7

Additional files for all supported x86-based versions of Windows 7
File nameUpdate.mum
File versionNot applicable
File size1,648
Date (UTC)13-Sep-2010
Time (UTC)07:22
PlatformNot applicable
File nameX86_98614f2a982f3858d331ec6f353e3928_31bf3856ad364e35_6.1.7600.20798_none_e11d5099db7a72fe.manifest
File versionNot applicable
File size704
Date (UTC)13-Sep-2010
Time (UTC)07:22
PlatformNot applicable
File nameX86_microsoft-windows-installer-engine_31bf3856ad364e35_6.1.7600.20798_none_03d2a7be2dfb53a7.manifest
File versionNot applicable
File size182,169
Date (UTC)13-Sep-2010
Time (UTC)07:26
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7
File nameAmd64_bcc999b8367695926a96e8b6e81f806d_31bf3856ad364e35_6.1.7600.20798_none_332d8648fb65bce6.manifest
File versionNot applicable
File size708
Date (UTC)13-Sep-2010
Time (UTC)07:22
PlatformNot applicable
File nameAmd64_c5e692741e612f08d3b4aab95fbde85a_31bf3856ad364e35_6.1.7600.20798_none_8a91a14de58de4c1.manifest
File versionNot applicable
File size1,058
Date (UTC)13-Sep-2010
Time (UTC)07:22
PlatformNot applicable
File nameAmd64_fdfea70c75450d4a2d7527f841350627_31bf3856ad364e35_6.1.7600.20798_none_ba6f9216453c2cf8.manifest
File versionNot applicable
File size708
Date (UTC)13-Sep-2010
Time (UTC)07:22
PlatformNot applicable
File nameAmd64_microsoft-windows-installer-engine_31bf3856ad364e35_6.1.7600.20798_none_5ff14341e658c4dd.manifest
File versionNot applicable
File size182,173
Date (UTC)13-Sep-2010
Time (UTC)07:22
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,082
Date (UTC)13-Sep-2010
Time (UTC)07:22
PlatformNot applicable
File nameWow64_microsoft-windows-installer-engine_31bf3856ad364e35_6.1.7600.20798_none_6a45ed941ab986d8.manifest
File versionNot applicable
File size172,000
Date (UTC)13-Sep-2010
Time (UTC)07:22
PlatformNot applicable