.PCP

PCP File

Windows Installer Patch Creation Properties file
Ask a question
QUICK ANSWER

A PCP file is a Windows Installer "Patch Creation Properties" database - a developer build-input that tells Msimsp.exe how to compare an old and new MSI and generate an .msp patch. Open it with Orca from the Windows SDK. End users never install a PCP; it is a build recipe, not a patch.

Developer: Microsoft Category: Developer Files MIME: application/octet-stream
OPENS ON Windows
Related: .DO · .MD · .HEX · .XSD

On this page

19k+ extensions indexed
Last reviewed Aug 31, 2026

Not sure what your file is?

Drop any file into our identifier - we read just the first bytes to name the format.

Identify a file

What is the PCP file format?

A .pcp file (Windows Installer Patch Creation Properties file) is a developer build-input file used by Windows Installer for generating software patches. .pcp files contain global settings for update packages and serve as the basis for generating MSP patch files. Such files are consumed by the patch-build toolchain - they are not end-user installer files.

.pcp is a binary file stored as an OLE2 Compound File Binary (the same container as MSI databases) and can be opened and edited using the Orca program included in the Windows SDK. Patches are generated from .pcp files by Msimsp.exe, which calls PatchWiz.dll to diff a target MSI against an upgraded MSI and emit the final .msp patch. All these tools ship as part of the Windows Software Development Kit (Windows SDK). Generating patches requires specialized knowledge; however, installing the resulting patch is a simple process.

Modern build pipelines often use the WiX Toolset (via Pyro.exe and .wixmsp descriptor files) as an alternative authoring approach, though Msimsp.exe with a .pcp file remains supported across Windows Installer 3.x-5.x. Developers typically start from a blank template.pcp shipped with the SDK.

Security & safety

RISK: LOW

A PCP is a developer build-input database, not an installer or executable - opening one in Orca to inspect it does nothing to your system. It does not install software and end users never need to run it. The only real caution is the usual one for build inputs: only build/run patch tooling on .pcp files from sources you trust, since the resulting .msp will modify an installed product. There is no auto-run or macro behavior in the PCP itself.

Format details

in a nutshell
FULL NAMEWindows Installer Patch Creation Properties fileaka Patch Creation Properties, PCP file
DEVELOPERMicrosoftsince circa 2000 (Windows Installer 1.x patch tooling - PatchWiz.dll)
MIME TYPEapplication/octet-stream
TYPEWindows Installer database (OLE2 / Compound File Binary) describing how to build an MSP patch
MAGIC BYTES · FILE SIGNATURE
OFFSET
0001020304050607
HEX
D0CF11E0A1B11AE1
ASCII
········
A PCP is a Windows Installer database, so it carries the same 8-byte OLE2/CFBF signature (D0 CF 11 E0 A1 B1 1A E1) as .msi and .msp files. It is distinguished by its internal MSI tables (Properties, ImageFamilies, UpgradedImages, TargetImages, PatchMetadata), not by a unique header.

Programs that open PCP files

Windows4 apps
Orca (Windows SDK) Free Install Orca from the Windows SDK 'Windows Installer Developer Tools', then open the .pcp to view/edit its MSI tables. The standard PCP editor.
Msimsp.exe (Windows SDK) Free Command line: 'Msimsp.exe -s patch.pcp -p patch.msp -l log.txt' - calls PatchWiz.dll to build the .msp from the .pcp.
WiX Toolset Open-source Modern alternative: author patches with WiX patch projects instead of a hand-edited .pcp; WiX can drive the same patch-building logic.
InstEd (MSI editor) Freemium An alternative MSI/PCP database editor; open the .pcp to inspect or edit its Windows Installer tables.

Technical details

deep spec
File structureWindows Installer relational database stored inside an OLE2 Compound File Binary (CFBF) - same container format as `.msi` and `.msp` files
Magic bytes (hex)`D0 CF 11 E0 A1 B1 1A E1` at offset 0 - the OLE2/CFBF signature shared with `.msi` and `.msp`; the file is distinguished by its internal PatchWiz table schema, not a unique header
EncodingBinary (little-endian)
CompressionNone in the database itself; referenced source MSI packages may contain CAB-compressed file payloads
Internal tables`Properties`, `ImageFamilies`, `UpgradedImages`, `TargetImages`, `ExternalFiles`, `PatchMetadata` - these tell PatchWiz how to diff two MSI images
Primary build tool`Msimsp.exe` (Windows SDK) - reads the `.pcp` and invokes `PatchWiz.dll` to produce the output `.msp` patch package
Editing tools**Orca** (Windows SDK MSI database editor); InstEd; any OLE2-aware MSI table editor
Output artifactAn `.msp` Windows Installer patch package ready for distribution and silent end-user installation
Typical file sizeA few KB to a few hundred KB - stores build instructions and file references, not payload data
MIME type`application/octet-stream` (no format-specific MIME type registered)
Associated OSWindows (Windows Installer 1.x through 5.x)
Modern alternativeWiX Toolset patch authoring via `Pyro.exe` and `.wixmsp` descriptor files, which largely supersedes the `.pcp` + `Msimsp.exe` workflow in current build pipelines
Releasedcirca 2000 (Windows Installer 1.x patch tooling - PatchWiz.dll)
Latest versionStable across Windows Installer 3.x-5.x; tooling shipped in the Windows SDK
Specificationlearn.microsoft.com

PCP conversions

Community Q&A

asked by users
Ask a quick question
Get help from people who work with PCP files. Be specific - include your system and software version.
No account needed · answers usually within a day

No questions yet - be the first to ask about PCP files.

Frequently asked questions

What is a PCP file?
It's a Windows Installer 'Patch Creation Properties' file - a developer database that tells Microsoft's patch tool (Msimsp.exe/PatchWiz.dll) how to compare an old and new MSI and build an .msp patch. It's a recipe for a patch, not the patch itself.
How do I open a PCP file?
Open it in Orca, the free MSI database editor from the Windows SDK, to view and edit its Windows Installer tables. InstEd is an alternative editor.
Do I install a PCP file?
No. A PCP is a build input, not an installer - end users never install it. Developers run it through Msimsp.exe to produce an .msp patch, and that .msp is what gets installed.
How do I turn a PCP into an MSP patch?
Run Msimsp.exe (which calls PatchWiz.dll) with the .pcp as input: 'Msimsp.exe -s patch.pcp -p patch.msp -l log.txt'. Both tools come with the Windows SDK.
What's the difference between a PCP and an MSP?
A PCP describes how to build a patch; an MSP is the actual patch package customers install. The PCP is the source recipe, the MSP is the deliverable produced from it.
Is there a modern alternative to hand-editing a PCP?
Yes - the WiX Toolset lets you author Windows Installer patches in a project/source form instead of editing a .pcp database directly, then builds the .msp from that.

References

1Microsoft - Creating a Patch Creation Properties Filelearn.microsoft.com
2Microsoft - Msimsp.exelearn.microsoft.com

Keep exploring

across the database

Top extensions this week

1.AQQAQQ Instant Messenger File
2.CRDOWNLOADChrome Partial Download File
3.JPGJPEG Image
4.EXEWindows Executable (Portable Executable)
5.DATProgram Data File (generic)
6.DBSQLite Database File
7.RPMSGRestricted Permission Message
8.BINCD/DVD Disc Image (BIN/CUE)
9.PARTPartial Download File
10.JSONJavaScript Object Notation file

Related extensions

.DOStata Do-File
.MDMarkdown Document
.HEXIntel HEX File
.XSDXML Schema Definition
.MAPSource Map (JavaScript / CSS)
.CONFIGConfiguration File

Free file tools

An in-browser file identifier and image converter - everything runs on your device.

Open the toolbox

Browse file extensions A-Z