| Previous | Next |
| ERROR_SMI_PRIMITIVE_INSTALLER_FAILED | ERROR_SXS_FILE_HASH_MISSING |
ERROR_GENERIC_COMMAND_FAILED
A generic command executable returned a result that indicates failure.
ERROR_GENERIC_COMMAND_FAILED is Win32 error 14109 (0x0000371D) in Windows side-by-side assembly, setup, localization, and servicing infrastructure.
Likely impact: HTTP or wrapper success does not override the child process exit status, and partial external effects may remain.
Typical causes
- the executable returns nonzero.
- the command line or working directory is wrong.
- required environment or privileges are absent.
- the process is terminated or times out.
Troubleshooting steps
- Verify that the process starts, completes within policy, and returns an exit status accepted by the caller.
- Collect resolved executable and command line and working directory and environment.
- Match the child process exit code or termination reason with its stdout and stderr, then compare that value with the success codes accepted by the caller.
Useful evidence
- Collect stdout and stderr.
- Collect servicing transaction and side effects.
Recovery and retry
Run the exact command in a controlled diagnostic context, fix its specific failure, and let the owning setup engine perform the retry.
Related errors
ERROR_CREATE_FAILED can mean process or object creation failed; this code means the command ran far enough to return a failing result
Example
A servicing command launches successfully but returns an application-defined exit code after failing to find an input file. Capturing stderr reveals the missing path.
References
Looking for a different code? Search another status or error code.