| Previous | Next |
| ERROR_APPEXEC_HANDLE_INVALIDATED | ERROR_APPEXEC_UNEXPECTED_PROCESS_REGISTRATION |
ERROR_APPEXEC_INVALID_HOST_GENERATION
The AppExec host generation has been invalidated.
ERROR_APPEXEC_INVALID_HOST_GENERATION is Win32 error 3062 (0xBF6). A generation distinguishes successive lifetimes or configurations of an execution host. The status prevents a request prepared for an older host instance from being applied to a newer one that may have different registrations, identity, or resources.
Events that advance host generation
- the host process or broker restarts after a crash, update, shutdown, or recovery
- the host is recreated for another user, package, container, or activation context
- configuration or registration changes invalidate requests prepared under previous state
- a reconnect obtains a new host instance while queued work retains the old generation
- client caches are restored from persistence even though host generations are session-local
Generation evidence
Capture requested and current generation values, host ID, process/service start time, package/app and user/session identity, request creation time, reconnect count, registration state, and correlation IDs. Treat generation numbers as opaque comparison tokens; do not infer chronology beyond equality unless the owner documents it.
Diagnostic sequence
Query or reconnect to the authoritative host and obtain its current generation. Invalidate all handles and queued requests tied to the previous value. Correlate the transition with host logs to understand whether restart was expected or a stability problem.
Rebuild the request from current registration and capability state rather than editing only the generation field. The old request may contain other assumptions that changed with the host instance.
Recovery and concurrency control
Acquire current host state, create new handles, and resubmit only operations safe to replay. Drop stale completions from the previous generation so they cannot overwrite current state.
Attach generation tokens to every asynchronous request and verify them at dispatch and completion. A host restart should atomically invalidate caches, timers, callbacks, and donor/resource references.
Difference from handle invalidation
ERROR_APPEXEC_HANDLE_INVALIDATED directly rejects an opaque handle. Error 3062 identifies the broader host-generation mismatch and can require rebuilding several related objects, not only one handle.
Example
A host updates and restarts while the client has queued activations tagged with generation 41. The new host reports generation 42 and rejects them with 3062. The client discards the queue, refreshes registrations, and submits new requests.
References
Looking for a different code? Search another status or error code.