Format:WiX Burn bundle
| Developer | .NET Foundation (WiX Toolset) |
|---|---|
| Magic | Section named .wixburn whose first dword is 0x00F14300 (00 43 F1 00) and second 2 |
| Extensions | .exe |
| Endianness | little |
| License | MS-RL |
| Website | https://wixtoolset.org |
| On this wiki | Facts · Code · Notes · Topics |
WiX Burn bootstrapper bundle (setup.exe of a WiX bundle): the .wixburn PE section with magic 0x00F14300, version 2, bundle GUID and container sizes, the cabinet-format UX container right after the stub and attached containers after the engine; as read in wixtoolset/wix src/burn.
A Burn bundle is a PE executable (the engine, built from src/burn/stub) with a data section that describes where its containers sit in the file. Everything below was read in wixtoolset/wix src/burn/engine/section.cpp, inc/engine.h, container.cpp, container.h, core.cpp and src/burn/stub/StubSection.cpp.
The .wixburn section
The engine finds the section by walking the PE section table (after the optional header) for an 8-byte name equal to .wixburn. The constants are BURN_SECTION_MAGIC 0x00F14300 and BURN_SECTION_VERSION 0x00000002; engine.h notes that they are mirrored in BurnCommon.cs of the WiX compiler. The engine checks only the version, not the magic. The section is at least 512 bytes, which gives room for 116 container sizes.
| Offset | Size | Field (BURN_SECTION_HEADER, little endian) |
|---|---|---|
| 0x00 | 4 | dwMagic 0x00F14300 |
| 0x04 | 4 | dwVersion = 2 |
| 0x08 | 16 | guidBundleCode |
| 0x18 | 4 | dwStubSize: size of the engine PE up to where the UX container begins |
| 0x1C | 4 | dwOriginalChecksum: PE checksum before signing |
| 0x20 | 4 | dwOriginalSignatureOffset |
| 0x24 | 4 | dwOriginalSignatureSize |
| 0x28 | 4 | dwFormat: container format; the stub default is 1 = cabinet (enum BURN_CONTAINER_TYPE: NONE 0, CABINET 1, SEVENZIP 2) |
| 0x2C | 4 | cContainers |
| 0x30 | 4 each | rgcbContainers[]: byte size of each container |
Where the containers are
- Container 0 is the UX (bootstrapper application) container and starts right after the stub: offset = dwStubSize.
- The engine size is the original signature offset plus size when the bundle was signed after build (dwOriginalSignatureOffset not zero), else the Authenticode certificate table end if the file is signed, else dwStubSize plus the size of container 0.
- Attached containers 1..n follow after the engine, back to back: offset of container k = engine size + sum of sizes of containers 1..k-1.
- A container may be absent from the file (the bundle is then a stub that downloads it): the engine sets it present only when offset plus size fits in the file.
Signing a bundle appends an Authenticode signature to the file and changes the PE checksum, so the engine keeps the pre-signing values in the section to locate the containers.
The UX container
Container 0 is a Microsoft cabinet (Format:Microsoft Cabinet); its first stream is the bundle manifest (XML), which the engine loads before anything else, then the bootstrapper application files. In container.cpp the type is hard coded to cabinet for the UX container and a comment says reading the type from the manifest is not yet implemented. Detect It Easy tests for an MSCF overlay and the section name; Tool:WiX Toolset and Tool:Detect It Easy describe that detection (not read here). Payloads (MSI, EXE packages) live in the attached containers or beside the setup.
Unverified: unpackers such as the dark.exe -x decompiler of the WiX toolset and 7-Zip can extract the containers; not tested here.
Code & repositories
- https://github.com/wixtoolset/wix @
77aa9818ad37637f961afe143be88bdc38a3f350· license: MS-RL (declared by the contributor; GitHub's detector did not recognize LICENSE.TXT)
WiX Toolset source; src/burn holds the Burn engine and stub: section.cpp reads the .wixburn section, container.cpp the cabinet containers.
Tested on: source read, not run: source read, not run (sparse checkout of src/burn) · checked 2026-10-19; last activity 2026-10-16; Note: the latest release ships binaries; the wiki links only the source, never the binaries
See also
Tool:WiX Toolset, Format:Windows Installer MSI, Format:Microsoft Cabinet, Format:PE (Portable Executable), Technique:Identifying the toolchain of a binary.