| Previous | Next |
| STATUS_SMI_PRIMITIVE_INSTALLER_FAILED | STATUS_SXS_FILE_HASH_MISSING |
STATUS_GENERIC_COMMAND_FAILED
The wrapper reports failure, but the child command explains why
Servicing manifests can invoke a command as one step in a larger installation or update transaction. This status means that step reported failure, but it does not say whether the cause was invalid arguments, missing input, access denial, timeout, dependency failure, or an application-defined exit code.
Capture the exact executable and command line from trusted servicing logs. Running a guessed command manually can change state outside the transaction and make rollback or retry less reliable.
What to inspect
- Collect the executable path, arguments, working directory, environment, exit code, and captured output.
- Find the package and servicing phase that launched the command.
- Check whether security software, policy, or architecture redirected or blocked the executable.
- Correct the underlying command failure before retrying the package transaction.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: system error codes 12000–15999
- Microsoft: DISM operating-system package servicing options
- Microsoft: repair a Windows image with DISM
Looking for a different code? Search another status or error code.