| Previous | Next |
| ERROR_PROFILING_AT_LIMIT | ERROR_CANT_TERMINATE_SELF |
ERROR_CANT_WAIT
What this result means
ERROR_CANT_WAIT is a Windows system result. The requested operation cannot complete immediately and would need to wait, but the current execution context is not allowed to block. This is common in kernel, asynchronous, loader, and callback-sensitive paths.
Why it can appear
- code performs pageable or blocking I/O at an elevated IRQL or nonblocking callback
- a lock, loader callback, or teardown path forbids waiting
- an asynchronous API was invoked as if it were synchronous
- a driver or runtime contract requires the work to be deferred
Diagnostic workflow
- record thread context, IRQL where applicable, held locks, callback type, and the exact API
- capture whether the resource was contended or I/O was pending
- inspect stack traces for loader lock, filesystem callbacks, completion routines, or dispatch paths
- verify documented waitability requirements for the API
Correct recovery and handling
Queue the operation to an appropriate worker context or redesign it as asynchronous. Do not busy-loop or sleep in a context that forbids waiting. Release locks before potentially blocking work when the contract permits.
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
The resource may be healthy; the problem is the calling context. A later retry from a normal worker thread can succeed, while an immediate retry from the same callback usually cannot.
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.