| Previous | Next |
| ERROR_IO_PRIVILEGE_FAILED | ERROR_MISSING_SYSTEMFILE |
ERROR_CONTROL_C_EXIT
What this result means
ERROR_CONTROL_C_EXIT is a Windows system result. The process ended because it received Ctrl+C or an equivalent console control event. In automation this commonly represents user cancellation, pipeline interruption, or a supervisor intentionally stopping a console program.
Why it can appear
- a user pressed Ctrl+C
- a parent process or console host generated CTRL_C_EVENT
- a build, script, or CI job propagated cancellation
- the program converted a control event into process termination without graceful cleanup
Diagnostic workflow
- record the console control event, parent process, session, timestamp, and exit code
- distinguish Ctrl+C from Ctrl+Break, service stop, kill, timeout, and crash
- inspect whether a control handler ran and whether cleanup completed
- in pipelines, identify which stage initiated cancellation
Correct recovery and handling
Treat it as cancellation when that matches the workflow. Save checkpoints, close files, and return a cancellation-specific status. Do not report it as an unexpected crash unless no control event was actually delivered.
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
Shells may display the numeric value as a signed or unsigned exit code. Preserve the symbolic meaning so operators do not misclassify intentional cancellation.
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.