Microsoft does not document /ppkg export driven solely by custom /i rules without /apps or /drivers; the documented PPKG workflows use the specialized application, settings, or driver capture modes, so exit code 0 and creation of the positional migration store do not establish that a PPKG was exported.
What is documented
The general ScanState grammar lists these elements together:
ScanState.exe [StorePath] [/apps] [/ppkg:FileName] [/i:FileName] ...
It also states that StorePath is mandatory except with /genconfig, that /i loads custom migration rules, and that /ppkg “exports to a specific file location.” It does not define /ppkg as a general conversion of the ordinary USMT store, nor does it say that /i alone activates provisioning-package output.^1^
The documented provisioning-package command families instead use:
-
/appswith an ADK-supplied settings/app configuration file; -
/drivers, where/ppkgis explicitly required; -
/appsplus/drivers; -
/apps:-appfileswithConfig_SettingsOnly.xmlfor settings-only capture.
For example, Microsoft documents settings-only package capture as:
ScanState.exe /apps:-appfiles /o /v:13 ^
/config:Config_SettingsOnly.xml ^
/ppkg %systemdrive%\Recovery\Customizations\systemsettings.spp
Those documented SPP commands intentionally have no positional StorePath; /ppkg is the output in that specialized command family.^2^
The OEM Push Button Reset example follows the same model: /apps, /ppkg, a custom /i file, and Config_AppsAndSettings.xml, without a positional store:
ScanState.exe /apps /ppkg C:\Recovery\Customizations\apps.ppkg ^
/i:c:\recovery\oem\regrecover.xml ^
/config:E:\scanstate\Config_AppsAndSettings.xml ^
/o /c /v:13 /l:C:\ScanState.log
Here the custom XML supplements the /apps capture; it is not the sole capture-mode selector.^3^
Interpretation of this run
For the exact command used:
- The first exit 11 is consistent with the documented general parser requirement that the store parameter be present.
- After adding
StorePath, ScanState accepted the command and created an ordinary compressed migration store from the/irules. - Code 0 is defined only as
USMT_SUCCESS/ “Successful run.” Microsoft recommends using the detailed messages in the log to interpret the operation; the return-code documentation does not state that code 0 guarantees creation of every separately named output artifact.^4^ - No first-party documentation supplied for ADK 10.1.26100.9457 identifies a condition that is expected to produce code 0 + ordinary StorePath file + missing requested PPKG.
- The compatibility table does not establish otherwise: it documents combinations involving
/i, StorePath, and several other options, but it does not provide a/ppkgcompatibility row or explicitly validate the/i-only PPKG scenario.^1^
Consequently, the preserved run demonstrates successful ordinary-store capture, but the available documentation does not support treating custom /i rules alone as a supported PPKG export workflow.
Privacy-preserving diagnosis of the preserved evidence
Because the run will not be repeated, inspect only the existing artifacts locally:
- Record the exact
scanstate.exefile version, command line, exit code, StorePath size, requested PPKG path, and the fact that the destination remained empty. - Search
ScanState.loglocally for only structural terms such as:-
ppkg -
package -
export -
store -
warning -
error - the custom component name
-
- Share only the matching message text after removing paths, user names, registry data, values, and captured filenames.
- Use
ListFiles.txtlocally to confirm whether the benign test file was selected. That file lists items gathered into the migration store, so its contents can reveal paths and should not be disclosed raw.^5^ - If the XML itself requires validation, validate it against the ADK’s
MigXML.xsd. Microsoft also notes that malformed helper-function behavior can still yield a success result while not collecting the expected content; the related warning should be located by component or helper name in the ScanState log.^6^
That XML condition can explain missing selected content, but the documentation does not say it explains creation of an ordinary store while silently omitting the separately requested PPKG. If the sanitized log contains no PPKG/export message, the appropriate escalation is a Microsoft support case with the version, normalized command shape, artifact manifest, and redacted matching log lines—not the captured store or raw migration logs.
References