| Previous | Next |
| ERROR_REQUEST_PAUSED | ERROR_APPEXEC_HANDLE_INVALIDATED |
ERROR_APPEXEC_CONDITION_NOT_SATISFIED
The app execution condition was not satisfied.
ERROR_APPEXEC_CONDITION_NOT_SATISFIED is Win32 error 3060 (0xBF4). AllStat describes it as an app-execution request whose supplied condition was not satisfied. Public Win32 documentation does not expose one general AppExec API contract for this family, so diagnosis must begin with the Windows component or product API that produced the status rather than inventing a universal condition list.
Kinds of condition to look for
- a host, package, user session, policy, capability, or lifecycle prerequisite is not in the required state
- the request contains a generation, identity, or predicate that no longer matches current host state
- execution is gated on availability of another process, resource, registration, or activation context
- a race changes the condition after the caller checks it but before the host evaluates the request
- client code treats a conditional no-op as an infrastructure crash and retries without refreshing state
Evidence from the returning component
Log the exact API or IPC operation, request and host IDs, package/application identity, user/session, supplied condition or predicate name, observed host state, generation, policy/capability results, correlation IDs, and the component’s own event channel. Do not record tokens or private package data.
Diagnostic sequence
Identify the owner and retrieve the current state through its supported query path. Compare every request precondition with the state at the moment of execution, not only with an earlier client-side check. Correlate host restarts, user changes, package updates, and policy refreshes.
Recreate the request only after refreshing handles and generations. If the condition is intentionally false, treat the result as a controlled nonexecution outcome and surface the unmet prerequisite rather than masking it with generic retry.
Recovery and robust callers
Satisfy the documented prerequisite or abandon the request. Retry with newly queried state when the operation is safe and the owner indicates the condition can change. Do not alter security policy merely to force execution.
Callers should include correlation and generation data, distinguish conditional rejection from host failure, and cap retries. Product telemetry should preserve the named condition so future Windows changes do not require guessing from 3060 alone.
Difference from invalid host state
ERROR_APPEXEC_INVALID_HOST_STATE says the host itself is not in a state that supports the request. Error 3060 emphasizes a supplied condition or prerequisite that evaluated false, which may be narrower than overall host validity.
Example
An activation broker receives a request tied to an interactive-session condition after the user has signed out. It returns 3060. The caller waits for a new eligible session and builds a fresh request instead of repeatedly sending the stale one.
References
Looking for a different code? Search another status or error code.