Windows error 1631 (ERROR_CREATE_FAILED): meaning and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: Windows Installer could not create or start the service-side installation operation.

Previous	Next
ERROR_UNSUPPORTED_TYPE	ERROR_INSTALL_TEMP_UNWRITABLE

ERROR_CREATE_FAILED

The Windows Installer service failed to start the requested operation.

ERROR_CREATE_FAILED is Win32 error 1631 (0x65F). In the Windows Installer error table, it means the Installer service failed to start. It is an initialization failure before normal package execution can proceed. The service may be disabled, damaged, inaccessible in the current environment, or unable to create required internal state. Package-level repair actions are unlikely to help until the installer engine itself can operate.

Likely causes

the Windows Installer service is disabled, missing, or fails during startup
service registration or required system files are damaged
a restricted boot, recovery, or container environment does not support the service
security software or policy blocks service creation or activation
the caller’s session, token, or RPC path cannot reach the installer service

Evidence to gather

Capture the full msiexec command or MSI API, service state and start type, Service Control Manager error, operating-system build, caller identity and elevation, package hash, and any system servicing or security events around the failure. Distinguish error 1631 from 1601, whose message says the service could not be accessed; both need service-side evidence rather than only package logs.

Diagnostic order

Verify that the Windows Installer service is present and can be started through supported service-management tools. Check system-file and servicing health if startup fails independently of the package. Reproduce with a known-good simple MSI only after preserving the original evidence; success with another package narrows the issue but does not erase the initial service error.

Inspect policy, application-control, endpoint-security, and restricted-environment settings. Avoid downloading replacement system DLLs or manually registering random components from another Windows version. If the machine is mid-update, complete or roll back servicing before repeated installer attempts.

Recovery

Restore the Windows Installer service using supported Windows repair and servicing procedures, then rerun the installation from a verified source. Administrators should correct service startup and system integrity first. Deployment software should detect 1631 as an infrastructure failure, stop retry storms, and report the host as needing remediation.

Difference from package creation errors

Despite its generic constant name, error 1631 is defined in the Windows Installer table as failure to start the Installer service. It should not be interpreted as an MSI authoring tool being unable to create a package file.

Example

An enterprise deployment reaches one workstation where the Windows Installer service immediately exits because system servicing is incomplete. Every package reports 1631. Repairing the operating-system servicing state and successfully starting the service resolves all deployments; rebuilding each MSI would not.

References

Looking for a different code? Search another status or error code.