Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The /msixvc2 option in makepkg.exe enables the next evolution of PC packaging in the Microsoft Game Development Kit (GDK). Like earlier content update improvements, it builds on the existing packaging workflow: you prepare your game content, configure installation chunks, create a package, and upload it to Partner Center.
The option selects the MSIXVC2 package format, which uses content-based segmentation to reduce package overhead and the amount of data transferred for updates. Your existing MicrosoftGame.config, layout files, and game file-access APIs remain applicable. Both original MSIXVC and MSIXVC2 packages use the .msixvc file extension.
Important
The /msixvc2 option applies only to PC games. XBOX console games continue to use XVC. The same makepkg.exe tool supports XVC, MSIXVC, and MSIXVC2. The examples in this article describe the October 2026 GDK; see Scope and timeline for release-specific behavior.
What the option changes
Packaging has two distinct ways of dividing game content:
- A chunk is a logical group of files defined by your layout mapping file. Streaming installation and Intelligent Delivery use chunks to control what is installed and when.
- A segment is a unit of file data used to identify unchanged content during upload and content updates. With
/msixvc2, segment boundaries are derived from content rather than fixed block positions.
Changing a chunk layout doesn't change the contents of an unchanged file. Content-based segmentation lets the packaging system reuse that file's data instead of transferring it again.
Key improvements
Smaller content updates
With /msixvc2, content updates reuse unchanged segments rather than relying on fixed 4 KB block alignment. Moving an unchanged file between chunks or reordering files within a chunk doesn't require players to download that file's content again.
The benefit varies with your game's assets and build process. For example measurements and a comparison procedure, see Measure PC content updates.
Faster packaging
The following measurements illustrate packaging-time improvements when using /msixvc2. Times are approximate, not performance guarantees. Measure both configurations with the same game builds and build environment to evaluate the benefit for your pipeline.
| Title size | Original MSIXVC packaging time | Packaging time with /msixvc2 |
|---|---|---|
| About 1 GB | 5 seconds | 2 seconds |
| About 12 GB | 70 seconds | 12 seconds |
| About 130 GB | 14 minutes | 3 minutes |
| About 320 GB | 52 minutes | 7 minutes |
Benchmark hardware
The example measurements in this article and Measure PC content updates were collected on a PC with the following hardware:
| Component | Specification |
|---|---|
| CPU | Intel Core i7-13700K, 3.4 GHz, 24 logical processors |
| RAM | 64 GB |
| Storage | Samsung SSD 990 PRO 4 TB; SK hynix PC801 NVMe 2 TB |
Hardware is only part of the measurement environment. Packaging-tool versions, compression settings, and the placement of source and output files on the drives can also affect results.
Reduced package overhead
Original MSIXVC packages include a minimum hash tree whose size scales with game size. This metadata is downloaded in full with each update. In the 320 GB example documented in Measure PC content updates, /msixvc2 reduced this overhead by about 91%. It also allows partial downloads of the metadata.
Built-in compression
By default, /msixvc2 uses Brotli compression for transport and storage on the content distribution network (CDN). Transport compression doesn't change the installed file contents or require your game to decompress the package format.
One-command upload from loose files
The /msixvc2 option also enables packaging and uploading loose files in one command:
makepkg upload /d <your_build_folder> /msixvc2 /pc /branch <branch>
Replace angle-bracket placeholders with your values, including the intended Partner Center package branch for <branch>. Enclose paths that contain spaces in quotation marks.
If neither /branch nor /flight is specified, uploads go to main. Specify the destination explicitly so that each upload goes to the intended branch or flight.
You can also create a local package with makepkg pack and upload it separately, for example after testing it on a development PC.
Format differences
| Aspect | MSIXVC | MSIXVC2 |
|---|---|---|
| Segmentation | Fixed-size 4 KB aligned blocks | Variable-size content-based segments |
| Package overhead | Fixed minimum hash tree based on game size | Minimal overhead |
| Chunk layout impact | Reordering chunks or moving files can require redownloading unchanged content | Layout metadata can change without redownloading unchanged file content |
What stays the same
- Game file-access APIs. Your game continues to use Win32 reads and DirectStorage to read installed game data.
- Packaging configuration. You continue to use
MicrosoftGame.configand layout mapping files. Review format-specific options in the makepkg reference when updating scripts. - Intelligent Delivery. You define installation chunks and tags the same way. Reorganizing unchanged files doesn't require redownloading their content.
- Partner Center submission. You continue to use your normal upload, validation, and publishing workflow. Partner Center identifies MSIXVC2 packages with a tag in the UI.
- Console packaging. XBOX console games continue to use XVC.
Scope and timeline
The following table distinguishes preview behavior from the planned release changes.
| GDK release | PC packaging behavior |
|---|---|
| April 2026 (2604) | Public preview. Use makepkg2.exe with /msixvc2 for evaluation, not public release. |
| October 2026 (2610, planned) | General availability, including certification for public release. The managed tool is named makepkg.exe; it replaces the legacy tool and the temporary makepkg2.exe name. Original MSIXVC remains the default; /msixvc2 opts in to the improvements. |
| April 2027 (2704, planned) | MSIXVC2 becomes the default PC package format. Creating original MSIXVC packages requires explicit format selection. |
| October 2027 (2710, planned) | makepkg no longer creates original MSIXVC packages. |
The commands in these articles describe the October 2026 behavior. Before adapting them to a later GDK, consult that release's makepkg pack /? help for format-selection options. Don't assume that omitting /msixvc2 will continue to select original MSIXVC.
Important
Plan your build and release pipeline migration before adopting the October 2027 GDK. If you still need to create original MSIXVC packages, retain packaging tools from an earlier GDK that supports creating them. This tool change concerns package creation, not the installation of already-published games.
Publishing in Partner Center
Use your normal Partner Center submission workflow for packages created with /msixvc2. Partner Center displays a tag that identifies MSIXVC2 packages, so you don't need a separate branch to distinguish them from original MSIXVC packages.
A Partner Center branch is an upload destination for packages, not a source-control branch. A sandbox is the environment in which you test or release your game. A package flight lets you distribute packages to a selected audience. The makepkg upload options /branch and /flight select alternative upload destinations and can't be combined.
For controlled prerelease validation, consider Playtest. After uploading an MSIXVC2 package to Partner Center, you can assign it to a playtest and distribute it to a controlled audience of players on retail PCs. Playtest lets you test without publishing your main game or creating a separate Store product. You can update the package, schedule, and audience while preserving the playtest and tester access, and Playtest packages are encrypted and licensed independently of the main game. Playtest is currently in Preview and requires approved access.
Playtest publishing takes place in RETAIL, but it isn't a certified commercial retail release. Submission Validator warnings and some failures can be deferred for this testing workflow. Review every finding because it can still identify installation, launch, or runtime problems; other applicable publishing requirements still apply. Successful Playtest publication doesn't establish certification readiness. See Development sandbox publishing versus certification.
Test installations, updates, and Intelligent Delivery behavior as part of your normal release process. To measure the effect of the packaging option, see Compare MSIXVC2 with original MSIXVC.
After testing, follow the usual Partner Center publishing procedure. Uploading a package doesn't itself publish an update to players.
Padding and alignment considerations
With original MSIXVC, content update efficiency depends on careful 4 KB alignment of assets within game asset archives (often called pack files). The /msixvc2 option removes this packaging alignment requirement because segmentation identifies unchanged data by content. This doesn't remove any alignment requirements imposed by your engine or asset format.
If your title ships on both PC and console, you can use separate padding configurations or retain a shared configuration. Keep the alignment optimizations required for XVC console packages. Measure the effect of any asset-layout change on both platforms before changing a shared build pipeline.
Getting started
For the packaging and upload procedure, see Package and upload a PC game.
For the makepkg command-line reference, see Make package (makepkg.exe).
Related topics
Overview of packaging
Package and upload a PC game
Package a PC game in original MSIXVC
Measure PC content updates
PC package encryption and content protection
Make package (makepkg.exe)
Xbox Game Package Manager
Automating package uploading