| Previous | Next |
| WU_S_UPDATE_ERROR | WU_S_REBOOT_REQUIRED |
WU_S_MARKED_FOR_DISCONNECT
Windows Update callback was marked for later disconnection
WU_S_MARKED_FOR_DISCONNECT is HRESULT 2359300 (0x00240004) from Windows Update. AllStat describes it as “A callback was marked to be disconnected later because the request to disconnect the operation came while a callback was executing.” In the Windows Update Agent callback, handler, or server-initiated healing workflow, the value reports a nonfailure state that must not be collapsed into plain S_OK.
The high-level request that returned this result is complete only after the caller validates the represented condition.
What must be true before accepting it
Verify that the callback is currently executing and will be detached exactly once after it returns. Validation of this result keeps a success-severity result from becoming a broader promise than the API made.
Also confirm that returned outputs belong to the current operation generation and were not inherited from an earlier attempt.
Where the status is encountered
- This result can appear during Windows Update Agent callback registration and disconnection; capture the exact API, object, and phase because the same numeric success severity does not define the state by itself.
- This result can appear during update handler planning and download-size calculation;
- It can appear during server-initiated healing evaluation;
Keep it attached to the operation that returned it. Interpreting it outside that API contract can turn a normal continuation or partial result into an incorrect retry or false completion.
Correct handling and recovery
Do not free callback state during the active invocation. Mark it closing, wait for callback exit, and verify that no later notifications arrive.
A new attempt following it should be triggered by a meaningful transition, not merely by elapsed time.
Practical scenario
A service unregisters an update callback from inside that callback. The framework defers disconnection and the service releases context after return.
Difference from nearby results
Immediate disconnect occurs when no callback is active; this status reports safe deferred removal.
Using one generic success branch for it and its neighbor can lose output, repeat work, or misreport completion.
References
Looking for a different code? Search another status or error code.