| Previous | Next |
| MK_E_CANTOPENFILE | MK_E_NOINVERSE |
MK_E_MUSTBOTHERUSER
User input required for operation to succeed
MK_E_MUSTBOTHERUSER has hexadecimal value 0x800401EB (unsigned 2147746283, signed -2147221013). Windows reports “User input required for operation to succeed”. The narrow interpretation is that Binding cannot continue without explicit user input. The failing stage is resolving a moniker that needs credentials, media selection, confirmation, or another interactive decision.
API stage
- Confirm that this result came from resolving a moniker that needs credentials, media selection, confirmation, or another interactive decision, rather than from cleanup or a wrapper that ran afterward.
Verification steps
- Identify the exact object, method, and lifecycle phase involved in resolving a moniker that needs credentials, media selection, confirmation, or another interactive decision.
- Record the nonsecret reason interaction is required and whether UI is available.
- Avoid logging credentials or sensitive display-name components.
- Separate headless-service behavior from interactive desktop behavior.
Interpretation limits
- It can result when authentication or consent cannot be obtained silently under policy.
- It can result when multiple targets match and the user must choose.
- It can result when required removable media, document location, or link repair needs user guidance.
Incident record
Recovery conditions
Correction. surface a bounded, contextual prompt or return control to an interactive caller; fail cleanly in unattended execution. Retry condition. Automatic retry without new user input is wrong; resume only after the requested decision is supplied and validated. Before repeating the operation, release partial monikers and bound interfaces, unregister only owned Running Object Table entries, and abandon a bind context whose deadline or parameters no longer match the retry.
Practical scenario
A link points to an offline protected share and no cached credentials are allowed; the desktop host prompts once, while a background service records a noninteractive failure.
Difference from related HRESULTs
MK_E_CONNECTMANUALLY can require programmatic setup; it explicitly says user involvement is necessary.
Developer and administrator guidance
References
Looking for a different code? Search another status or error code.