| Previous | Next |
| ERROR_CANT_WAIT | ERROR_UNEXPECTED_MM_CREATE_ERR |
ERROR_CANT_TERMINATE_SELF
What this result means
ERROR_CANT_TERMINATE_SELF is a Windows system result. Windows rejected a termination request because the calling thread attempted a self-termination pattern that the relevant API or subsystem does not permit.
Why it can appear
- cleanup code targets the current thread through an API intended for another thread
- a debugger or compatibility layer issues termination in the wrong context
- thread identifiers were reused or resolved incorrectly
- shutdown logic confuses cooperative cancellation with forced termination
Diagnostic workflow
- log caller and target thread IDs, process IDs, handles, and access rights
- verify whether the target handle refers to the current thread
- inspect shutdown ordering and thread-ID reuse
- capture the API contract and whether termination is being requested from a callback or exception handler
Correct recovery and handling
Use cooperative cancellation: signal the worker, let it release resources, and return normally. Forced termination should be reserved for exceptional containment because it can leave locks, heap state, and application invariants damaged.
Administrator and support checklist
- confirm whether the condition is isolated to one machine, one user, one file, or one application build.
- Compare the host reporting this result with a known-good system using the same Windows edition and policy.
- Review updates, drivers, security-policy changes, restores, and infrastructure incidents that preceded this result.
- Preserve logs and dumps associated with this result before rebooting when the failure may be intermittent or destructive.
- Use vendor-supported repair or rollback steps for this Win32 error instead of copying system files or disabling protections ad hoc.
Developer guidance
When handling it, log the API or subsystem that returned it, the first lower-level failure, relevant object identifiers, process and thread context, and safe operation parameters. Preserve the original numeric Value rather than converting it to an unrelated HRESULT or NTSTATUS. Retry it only when the evidence shows a transient dependency; deterministic it cases involving policy, format, compatibility, or integrity should fail fast.
What to record in telemetry
- Windows build, architecture, and component version for the result event
- the first result timestamp and the operation then in progress
- process, thread, session, and target object associated with it
- warnings or lower-layer status values immediately preceding it
- whether retry, restart, rollback, or repair changed the result outcome
Example investigation pattern
Investigate it by reproducing the operation once with detailed logging, then correlate that timestamp with Windows events and lower-layer traces. Compare the affected object or process with a known-good one, change one variable at a time, and stop retrying When it is deterministic. That method keeps the first relevant failure from being hidden by secondary cleanup messages.
Related and easily confused conditions
This is not the same as access denied. Even a sufficiently privileged caller may be forbidden from using a particular self-termination route.
Operational note
Do not diagnose it from its text alone. The result can cross subsystem boundaries and may summarize an earlier, more specific event. The first failure in time is normally more useful than the last message printed during cleanup.
References
Looking for a different code? Search another status or error code.