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.
- 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.
- 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^
- 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^
- 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.
- 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^
- 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
- Siloed provisioning packages
- DISM Provisioning Package (.ppkg) Command-Line Options
- PowerShell cmdlets for provisioning Windows client
- Export-ProvisioningPackage-Description
- UsmtUtils Syntax
- Extract app package contents (C++)
- Recovery components
- OEM Deployment of Windows 11 desktop editions