Microsoft introducing version-specific System Manifest delivery during Windows 11 OOBE

Today we are introducing a new Hardware Dev Center capability for ARM system makers that lets hardware partners request approval for a specific System Manifest version to be delivered during the Windows Out-of-Box Experience (OOBE).

With this capability, OOBE can bring a device to the minimum approved driver and firmware baseline needed for a reliable first-run experience. Newer System Manifest versions that are not required during setup can continue to be offered later through normal Windows Update servicing.

Delivering the right update at the right time​

System Manifests provide a coordinated set of driver and firmware updates for ARM devices. In some cases, a new device needs a critical fix before the user reaches the desktop. Windows provides a way to deliver that fix during OOBE.

Previously, once a system was approved for System Manifest delivery during OOBE, the latest applicable retail System Manifest could be offered during setup. That version might include updates beyond what was needed to address the first-run issue, adding download, installation, firmware update, or restart time to OOBE.

Version-specific delivery separates the OOBE baseline from the latest retail System Manifest. Partners can request that a specific version be approved as the OOBE-critical baseline. Devices below that baseline can receive it during setup. Devices already at or above the baseline do not install a System Manifest during OOBE. After setup, Windows Update can offer later applicable versions.

How it works​

Consider a device that ships from the factory with System Manifest version 1 installed. Version 2 resolves an OOBE-critical issue, while version 3 contains additional routine improvements.

• When version 2 is approved as the OOBE baseline, a device with version 1 can receive version 2 during OOBE.
  • Note: if version 2 is already installed at the factory, it will not be delivered during OOBE.
• Version 3 is not offered during OOBE, but after the device completes OOBE Windows Update will offer version 3 through the normal servicing path.

If a newer version is later approved as the OOBE baseline, it takes precedence over the previous baseline. If an approved version must be withdrawn, the partner can expire that System Manifest for all audiences.

Approval is limited to OOBE-critical issues​

Delivering driver and firmware updates during OOBE can extend setup and may require additional restart activity. For that reason, this capability is intended for issues with a severe effect on the first-run experience, such as preventing OOBE completion or creating a significant risk of device return.

Routine quality improvements, cosmetic fixes, and updates that can wait until after first sign-in should continue through normal Windows Update servicing. Partners are also expected to ship a stable factory image. OOBE is an additional path for approved critical fixes, not a replacement for factory quality.

Requesting OOBE delivery​

To request version-specific System Manifest delivery during OOBE:

1. Submit an OOBE-specific request through Microsoft Collaborate. Describe each OOBE-critical issue, its severity, the expected number of affected devices, the validation plan for the fixes, and the business impact.
2. Receive Design Change Request (DCR) ID through Microsoft Collaborate.
3. Submit the System Manifest through Hardware Dev Center. Include the DCR ID in the publishing business justification. The submission is held from publication while the OOBE request is reviewed.
   Important: The business justification field must include the following text to be considered for OOBE delivery: [OOBE-DCR: <id>], including the brackets, where <id> is the DCR ID.
4. Complete flighting and technical validation. Microsoft reviews the quality evidence and readiness signals for the proposed baseline.
5. Validate the published experience. After approval and quality signoff, confirm that the intended version installs during OOBE and that newer retail versions remain available after setup.

The publishing business justification cannot be edited after submission. If it contains an omission, typo, incorrect DCR ID, or reused DCR ID, submit the System Manifest again with the corrected information.

Test during DCR review​

Partners do not need to wait for DCR approval to test their System Manifest in OOBE scenarios. While creating the Hardware Dev Center submission, select Test Registry Key and indicate in the publishing business justification that you would like to test the System Manifest in OOBE scenarios. This makes the submission available for OOBE validation on systems configured to receive test-distributed content while the DCR is under review. Test distribution does not approve the System Manifest for production OOBE delivery. Production publication remains subject to DCR approval, technical validation, and quality signoff.

Availability and scope​

Version-specific System Manifest delivery during OOBE is available for ARM systems running Windows 11, version 24H2 and later. It applies to System Manifest driver and firmware servicing. Loose-leaf driver delivery is not included.

By default, System Manifests are not offered during OOBE unless a version has been approved for that purpose. Partners with existing OOBE-approved systems must republish the version they want to use as the OOBE baseline under the new audience model.

Get started​

Identify the System Manifest version that resolves the OOBE-critical issue, prepare the supporting business justification and validation plan, and start the request through Microsoft Collaborate. After receiving the DCR ID, submit the intended baseline through Hardware Dev Center and complete the required validation.

This capability helps deliver the critical update a new device needs during setup, while reserving routine and newer updates for the normal Windows Update experience after first sign-in.