Windows ADK 10.1.26100.9457: Deployment Tools-only offline acquisition and servicing

The only Microsoft-documented acquisition procedure for ADK 10.1.26100.9457 is to download the complete offline layout first and select OptionId.DeploymentTools only during the later installation; Microsoft does not document a feature-restricted layout command or a package-only acquisition method.

Supported offline procedure

On an internet-connected acquisition system, run:

New-Item -ItemType Directory -Path C:\ADK\Layout -Force

.\adksetup.exe /quiet /layout C:\ADK\Layout

This downloads the offline ADK payload without installing it. Microsoft documents /layout for acquisition but applies /features only when running the downloaded setup on the offline destination system.^1^

After the layout has passed your authorization process, install only Deployment Tools from the copied layout:

C:\ADK\Layout\adksetup.exe /quiet `
    /installpath C:\ADK `
    /features OptionId.DeploymentTools

The expected result is an installation containing Deployment Tools and dependencies selected by ADK Setup. Oscdimg is part of the Deployment Tools; a separate Windows PE add-on is not required merely to obtain Oscdimg. Windows PE is distributed separately when WinPE itself is needed.^2^

Feature-restricted acquisition

There is no published, supported syntax in the current ADK offline-install documentation equivalent to:

adksetup.exe /layout <path> /features OptionId.DeploymentTools

The documented command sequences keep these operations separate:

• Acquisition: /quiet /layout <path>
• Installation: /quiet /installpath <path> /features OptionId.DeploymentTools

Consequently, combining /layout and /features should not be used as a controlled acquisition procedure unless the ADK product team supplies release-specific confirmation. Successful execution by the bootstrapper would not, by itself, establish that the combination is supported.

The public documentation also does not identify another supported Microsoft tool or endpoint for downloading only the underlying Deployment Tools MSI/CAB packages without either:

1. creating the complete ADK layout, or
2. allowing ADK Setup to install the selected feature.

Therefore, the stated requirement—minimal package acquisition without installation or downloading the full layout—does not currently have a documented public procedure.

Package manifest and verification boundary

The cited Microsoft documentation does not publish a release-specific external manifest for ADK 10.1.26100.9457 containing all of the following:

• Deployment Tools package filenames;
• dependency graph;
• individual package versions and sizes;
• stable package download URLs;
• package hashes.

Do not construct a package set by observing bootstrapper traffic or copying selected MSI/CAB files from another layout. That would rely on undocumented package composition and could omit installer-managed dependencies.

For a controlled workflow, retain and verify the complete layout as one release artifact:

1. Acquire it with the signed 10.1.26100.9457 bootstrapper.
2. Preserve the complete directory tree.
3. Record internal hashes after download, for example:

Get-ChildItem C:\ADK\Layout -File -Recurse |
    Get-FileHash -Algorithm SHA256 |
    Sort-Object Path |
    Export-Csv C:\ADK\ADK-10.1.26100.9457-hashes.csv `
        -NoTypeInformation

These are organization-generated inventory hashes, not Microsoft-published reference hashes. Microsoft’s current download page confirms that 10.1.26100.9457 replaces 10.1.26100.2454 and supports Windows 11 26H2.^2^

KB5101684 and servicing

Do not apply KB5101684 to ADK 10.1.26100.9457. Microsoft lists it specifically as:

Windows ADK 10.1.26100.2454 Update KB5101684 for ADK 10.1.26100.2454 (December 2024)

It is not listed as a patch for 10.1.26100.9457.^3^

The 10.1.26100.9457 release notes already list the relevant Oscdimg boot-binary update, DISM security fixes, WSIM fix, OA3 changes, and App-V changes.^4^ Microsoft also states that only Deployment Tools changed among the 10.1.26100.x releases; their WinPE binaries remain version 10.1.26100.1.^5^

Before a later installation is authorized, check the servicing page for a patch explicitly naming 10.1.26100.9457. ADK patches are applied to an existing installation, so they do not replace the initial offline-layout acquisition process.^3^

For an authoritative statement that no unpublished package manifest or feature-filtered acquisition interface exists, this needs escalation to Microsoft Support or the ADK product team; the public documentation establishes only the full-layout workflow above.

References

1. Install the Windows ADK offline
2. Download and install the Windows ADK
3. Download and Install the Windows ADK Patches
4. What's new in the ADK tools
5. Support for the Windows ADK in Configuration Manager