Is there a supported complete read-only F/R/A/C inventory API for ScanState app-recovery PPKG or SPP?

Jason Siebert 0 Reputation points
2026-11-18T16:32:56.96+00:00

We are designing a privacy-gated Windows 11 OEM recovery workflow for classic Win32 applications. Before publishing any ScanState-generated application provisioning package, we need to independently enumerate the actual captured payload, not only ScanState's self-reported diagnostic logs.

The required audit covers:

  • F — Files: Every captured file, stream and path.
  • R — Registry: Every captured registry key/value, type and data class.
  • A — Applications: Every installed-app/component identity and associated registration.
  • C — Container: Complete container and nested catalog traversal.

The audit also needs positive/negative synthetic fixture reconciliation, detection of opaque records and reliable identification of unexpected source data.

Current Microsoft Learn documentation for /listfiles describes migrated files only. DISM /Get-ProvisioningPackageInfo and PowerShell Get-ProvisioningPackage report package information, while UsmtUtils /verify addresses ordinary compressed migration stores, not demonstrably this specialized application package type.

Export-ProvisioningPackage can write extracted provisioning content to a folder, but we have not found an official statement that it supports ScanState-produced classic application PPKGs, siloed SPPs, or exposes all nested registry/app records.

Specific question: Is there an official Microsoft-supported read-only API/tool (or a documented isolated synthetic-only extraction workflow) that completely enumerates all F/R/A/C records of these ScanState application package formats, including nested or opaque payloads, without applying them to a Windows installation?

If not, what supported approach is recommended to independently establish package privacy and complete contents before OEM Push-button Reset publication?

We are seeking documentation and format support, not advice to apply or publish a package. No personal or proprietary packages have been attached.

Windows for business | Windows Client for IT Pros | Devices and deployment | Set up, install, or upgrade
0 comments No comments

2 answers

Sort by: Most helpful
  1. Domic Vo 37,655 Reputation points Independent Advisor
    2026-11-18T17:05:50.28+00:00

    Hello,

    Based on Microsoft's currently published documentation, there is no documented Microsoft-supported read-only API or tool that guarantees complete enumeration of all Files, Registry, Applications, and Container (F/R/A/C) records in ScanState-generated classic application PPKGs or siloed provisioning packages (SPPs). Microsoft's /listfiles functionality is documented for migration file inventory, while DISM /Get-ProvisioningPackageInfo and Get-ProvisioningPackage expose package information rather than a complete payload inventory; similarly, Export-ProvisioningPackage documents content extraction but does not explicitly guarantee support for ScanState-generated application PPKGs, nested SPP catalogs, or complete registry and application record enumeration. I would not treat successful export, archive inspection, or UsmtUtils /verify as proof of complete payload visibility or privacy compliance for these specialized formats. The recommended supported approach is to use clean reference Windows installations, VM checkpoints, tightly controlled ScanState configuration files (Config_AppsOnly.xml or Config_AppsAndSettingsOnly.xml), and synthetic positive/negative fixtures to establish source-side capture boundaries and reconcile expected versus observed results. However, this provides evidence of capture behavior, not independently verified completeness of the serialized package; for that assurance, escalate to Microsoft OEM/Windows deployment support and request explicit confirmation of the supported package formats, extraction interfaces, nested catalog handling, and access to an official inspection mechanism or format specification. Until Microsoft confirms those capabilities, you should not claim complete F/R/A/C enumeration or treat the workflow as sufficient proof that no unexpected or opaque data exists in the published recovery package.

    If my answer is useful for you, please hit Accept the answer to support me.

    Thank you.

    Domic Vo.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-18T16:34:39.8633333+00:00

    No publicly documented Microsoft API or tool provides a completeness-guaranteed, read-only enumeration of every file, registry, application, container, nested, and opaque record in a ScanState-generated application PPKG or siloed SPP.

    Scope of the documented tools

    • ScanState diagnostics: /v:13 produces MigLog.xml, which indicates what ScanState captured, but it remains producer-generated evidence rather than an independent parser. /apps captures discovered desktop applications and associated registry settings; discovery rules determine the contents.^1^
    • DISM: /Get-ProvisioningPackageInfo returns package information. The documented payload operation is /Add-ProvisioningPackage, which applies applicable payload; no recursive inventory operation or completeness contract is documented.^2^
    • Provisioning PowerShell: Get-ProvisioningPackage returns package information. Export-ProvisioningPackage extracts provisioning-package contents on Windows 11, but its documentation does not state that it understands every ScanState reference-device-data record, traverses nested SPP structures, or produces a complete registry/application inventory.^3^^4^
    • UsmtUtils: /verify checks the integrity of a compressed migration store and its catalog, while /extract recovers files from that store. The documentation does not extend these operations to complete semantic inspection of ScanState application PPKGs or SPPs.^5^
    • APPX Packaging API: interfaces such as IAppxPackageReader enumerate APPX payload and footprint files. They document Windows app packages, not ScanState classic-application PPKGs or SPPs, so they are not a supported parser for these artifacts.^6^

    Consequently, successful export, metadata enumeration, catalog verification, or agreement with MigLog.xml cannot be represented as an independent F/R/A/C completeness attestation.

    Supported pre-publication control

    The documented approach is to control and audit the capture inputs, make capture reproducible, and treat available package inspection as corroborating—not completeness-proving—evidence.

    1. Start each capture from a clean, isolated Windows 11 reference VM.
      • Create a checkpoint before installing the positive fixtures.
      • Install only the intended Win32 applications and synthetic data.
      • Keep network access disabled unless an installer requires it.
      • Revert to the checkpoint for every repeated capture.
      Microsoft specifically recommends clean Windows installations to prevent unwanted settings from entering an SPP and recommends VMs with checkpoints.^1^
    2. Constrain the capture explicitly. For an application SPP, the documented narrow capture uses Config_AppsOnly.xml and /apps:-sysdrive:
    mkdir C:\AuditLogs
    ScanState.exe /apps:-sysdrive /o /v:13 ^
      /config:Config_AppsOnly.xml ^
      /ppkg E:\Repository\AppFixture.spp ^
      /l:C:\AuditLogs\ScanState.log ^
      /progress:C:\AuditLogs\Progress.log
    

    -sysdrive excludes folders outside the Windows namespace, while Config_AppsOnly.xml targets desktop applications and application settings. For a traditional PPKG intended to capture broader machine state, +sysdrive is the default and therefore has a materially larger privacy boundary.^1^

    Your custom /i-only rules can narrow provenance further, but they do not create a supported post-capture completeness API. ScanState permits additional migration XML rules to include or exclude files, folders, and registry settings.^7^

    1. Reconcile synthetic fixtures.
      • Positive fixtures: unique file names and contents, alternate streams, registry values of each required type, and uniquely named application registrations.
      • Negative fixtures: unique forbidden files, registry values, unrelated application registrations, and out-of-scope paths.
      • Repeat the capture from the same checkpoint and compare package hashes, MigLog.xml, ScanState/progress logs, and any exported representation.
      • Fail release if a negative marker appears, a positive marker is absent, captures are unexpectedly non-reproducible, or export reports an unrecognized/uninspectable object.
    2. Optionally export a PPKG as secondary evidence on Windows 11:
    Export-ProvisioningPackage `
      -PackagePath 'E:\Repository\AppFixture.ppkg' `
      -OutputFolder 'C:\Audit\Exported' `
      -LogsDirectoryPath 'C:\Audit\ExportLogs'
    

    Do not treat a successful export as proof that every nested registry, application, or opaque record was surfaced.^4^

    1. Block publication when complete package-only attestation is mandatory. The OEM workflow requires ScanState PPKGs under C:\Recovery\Customizations, but the OEM documentation does not add a pre-publication complete-content reader.^8^

    If policy requires proof of absence of undisclosed or opaque records—not merely controlled provenance and fixture-based evidence—request a written format/API support statement through the Microsoft OEM/support channel for the exact Windows ADK build and artifact type. That is the route for authoritative format support; it is not a guarantee that an additional public inspection interface exists.


    References

    1. Siloed provisioning packages
    2. DISM Provisioning Package (.ppkg) Command-Line Options
    3. PowerShell cmdlets for provisioning Windows client
    4. Export-ProvisioningPackage-Description
    5. UsmtUtils Syntax
    6. Extract app package contents (C++)
    7. Recovery components
    8. OEM Deployment of Windows 11 desktop editions
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.