| Previous | Next |
| ERROR_MISSING_SYSTEMFILE | ERROR_APP_INIT_FAILURE |
ERROR_UNHANDLED_EXCEPTION
What this result means
ERROR_UNHANDLED_EXCEPTION is a Windows system result. An exception reached the process top level without a valid handler. This result summarizes process failure; the original exception code and crash context determine the actual defect.
Why it can appear
- an access violation, stack overflow, arithmetic fault, or explicit exception was not handled
- memory corruption damaged exception state or handler metadata
- a language or plugin boundary allowed an exception to escape
- a top-level handler logged too little information and terminated
Diagnostic workflow
- capture a full crash dump, original exception code, faulting instruction, registers, thread stacks, and module versions
- identify first-chance exceptions preceding the final one
- enable symbols and relevant runtime diagnostics
- correlate with input, workload, and recent deployment changes
Correct recovery and handling
Fix the original exception rather than catching every failure at the top level. Use top-level handlers only to record diagnostics and terminate safely; continuing after unknown corruption is unsafe.
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 it 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
The wrapper code does not identify whether the fault was hardware, runtime, application logic, or injected code. Never diagnose from it alone.
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.