| Previous | Next |
| ERROR_CLOUD_FILE_PROPERTY_BLOB_CHECKSUM_MISMATCH | ERROR_STORAGE_LOST_DATA_PERSISTENCE |
ERROR_CHILD_PROCESS_BLOCKED
The parent process is not allowed to launch this child
ERROR_CHILD_PROCESS_BLOCKED is a Win32 system result. Application control, browser or document sandboxing, exploit protection, endpoint security, or an explicit child-process mitigation can deny process creation even when the executable exists and credentials are valid.
What the result means
Policy or process-mitigation rules blocked creation of a child process. For ERROR_CHILD_PROCESS_BLOCKED, keep the symbolic name, numeric value, and failing operation together in diagnostics; that combination distinguishes the exact failure path from nearby system results.
What to check
- Record the parent image, child image, command line, token, and process-creation API.
- Review effective exploit-protection and application-control policy.
- Check endpoint-security logs for the rule that made the decision.
- Confirm whether the application has a documented broker or service for launching approved helpers.
Recommended handling
Use the product’s approved launch mechanism or request a policy review. Do not disable mitigation globally or copy the executable to another path to evade enforcement.
Developer notes
Treat this as a policy result, not as file-not-found. Avoid shelling out for core functionality when a library or brokered API is available, and provide a clear degraded mode. When a Win32 API reports ERROR_CHILD_PROCESS_BLOCKED, capture GetLastError() immediately; subsequent cleanup, formatting, or logging calls can replace the thread-local value.
References
Looking for a different code? Search another status or error code.