| Previous | Next |
| STATUS_THREAD_ALREADY_IN_TASK | STATUS_UNDEFINED_SCOPE |
STATUS_CALLBACK_BYPASS
The callback requested a native-code bypass path
STATUS_CALLBACK_BYPASS identifies a specific Windows status in the job, task, callback, or isolation path. This internal callback result asks the surrounding framework not to execute the normal native path. It should be interpreted only by the component that defined the callback contract.
Log callback identity, operation phase and returned flags. Treating it as a generic failure can cause duplicate work or incorrect fallback.
What to preserve before changing the system
- The exact API, caller, target object, original NTSTATUS value, and any nested error or activity ID.
- For STATUS_CALLBACK_BYPASS, the relevant process token, package/job/enclave identity, lifecycle state, and policy or mitigation settings.
- For STATUS_CALLBACK_BYPASS, operational event logs and a timeline showing the first transition into the failing state.
References for STATUS_CALLBACK_BYPASS
Looking for a different code? Search another status or error code.