ScanState 10.0.26100: exit 0 creates Store file but no /ppkg output with custom /i-only rules

Jason Siebert 0 Reputation points
2026-11-18T16:28:15.02+00:00

On Windows 11 in a disposable, nonpersonal test environment, we are evaluating ScanState from the Windows ADK 10.1.26100.9457 for a synthetic-only recovery compatibility check.

We supplied one custom migration XML with precisely one benign file pattern and one benign HKCU registry-value pattern, with no broad wildcard selections.

The command used these exact option types (paths below are anonymized, not a verbatim executable reproduction):

ScanState.exe C:\Lab\Test02\Store /i:C:\Lab\Rules.xml /ppkg:C:\Lab\Test02\Output\SyntheticProbe.ppkg /listfiles:C:\Lab\Test02\Logs\ListFiles.txt /l:C:\Lab\Test02\Logs\ScanState.log /v:4

The earlier attempt without positional StorePath exited 11 with "store parameter is required".

The corrected attempt returned exit 0 and created a regular file at StorePath (19,006,971 bytes). ListFiles.txt and ScanState.log were created, but Output\SyntheticProbe.ppkg was absent and the Output directory had no files.

No /apps, /config, /o or /c was used. We have preserved this one-shot evidence and will not retry or expand capture.

Specific question: Does the ScanState build in this ADK support /ppkg export when capture is selected only through custom /i XML without /apps? If so, what documented condition can yield exit 0 and a Store file but no requested PPKG?

The general ScanState syntax documentation calls for StorePath, while the official OEM /apps /ppkg examples omit it. Which syntax and output/status semantics are supported for this exact command family?

Please refer to documented behavior or a supported diagnostic approach that does not require disclosing raw migration logs, personally identifying data, or captured contents.

References:

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. Hoang Le Huy 2,240 Reputation points Independent Advisor
    2026-11-18T17:02:32.41+00:00

    Hello Jason Siebert,

    Based on the Microsoft documentation, /ppkg is a valid ScanState parameter and appears in the supported ScanState syntax alongside both StorePath and /i migration XML files. However, the documentation does not state that /ppkg can generate a provisioning package from arbitrary user-state captures selected only through custom migration XML, nor does it document the output semantics for the exact scenario you tested.

    The key point is that Microsoft's provisioning-package documentation consistently describes the /ppkg workflow in the context of capturing desktop applications and customizations for recovery/OEM deployment scenarios, and those examples are tied to the provisioning-package capture process rather than general USMT state migration.

    From the evidence you provided, ScanState successfully completed its primary operation because it returned exit code 0 and created a migration store at StorePath. Microsoft documents ScanState as a tool that scans, collects files and settings, and creates a store; the creation of the store therefore demonstrates successful migration-store generation.

    I could not find Microsoft documentation stating that a .ppkg must be produced whenever /ppkg is specified, nor documentation that explicitly explains the combination of custom /i rules only, no /apps, exit 0, migration store present, but no PPKG output. The available documentation simply does not define that status combination.

    Because you have preserved the run and do not plan to recapture, the supported diagnostic approach is to review the existing ScanState.log at verbosity level 4 and the generated file list for messages specifically referencing provisioning-package generation rather than migration-store creation. Microsoft identifies the ScanState log as the authoritative diagnostic artifact for command processing and migration operations.

    My assessment is that the documented behavior clearly supports creation of the migration store in your command line, but the Microsoft sources I could verify do not explicitly document that /ppkg export is supported for a capture consisting solely of custom migration XML selections without the application-capture scenario that the provisioning-package guidance focuses on. If a definitive answer is required, this is one of the cases where Microsoft support would need to interpret the specific ScanState log because the published documentation does not define that exact output/status semantic.

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

    HL.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-18T16:29:32.6366667+00:00

    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:

    • /apps with an ADK-supplied settings/app configuration file;
    • /drivers, where /ppkg is explicitly required;
    • /apps plus /drivers;
    • /apps:-appfiles with Config_SettingsOnly.xml for 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 /i rules.
    • 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 /ppkg compatibility 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:

    1. Record the exact scanstate.exe file version, command line, exit code, StorePath size, requested PPKG path, and the fact that the destination remained empty.
    2. Search ScanState.log locally for only structural terms such as:
      • ppkg
      • package
      • export
      • store
      • warning
      • error
      • the custom component name
    3. Share only the matching message text after removing paths, user names, registry data, values, and captured filenames.
    4. Use ListFiles.txt locally 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^
    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

    1. ScanState syntax
    2. Siloed provisioning packages
    3. OEM Deployment of Windows 11 desktop editions
    4. User State Migration Tool (USMT) return codes
    5. USMT log files
    6. User State Migration Tool (USMT) common issues
    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.