| Previous | Next |
| ONL_E_INVALID_APPLICATION | ONL_E_ACCOUNT_UPDATE_REQUIRED |
ONL_E_PASSWORD_UPDATE_REQUIRED
0x80860004 is represented by ONL_E_PASSWORD_UPDATE_REQUIRED. In Windows Online ID and interactive account authentication the specific outcome is that the account requires a password update before authentication can continue. The phrase Online ID password update required narrows the first diagnostic record to account remediation status and interactive sign-in result.
Why this HRESULT is specific
The broker can return this HRESULT before a service ticket is issued. Keep the asynchronous operation, requested scopes or tickets, application identity, UI context and account remediation result together; a wrapper message such as “sign-in failed” discards the distinction.
The decisive question is whether the recorded evidence supports the reported condition that the account requires a password update before authentication can continue. Keep evidence tied to the failing operation.
Controlled troubleshooting sequence
- Locate the exact object: Use the primary record to identify the transaction or licensed object that actually returned this result.
- Preserve the first decision: Record the earliest event stating that the account requires a password update before authentication can continue, together with the code, UTC time, and the same identity fields.
- Change one prerequisite: Complete the password update in trusted microsoft account ui; do not combine this with a store reset, key replacement, account removal, package reinstall, or unrelated repair.
- Repeat the user operation: Re-run the original operation and require that the broker returns a fresh result; if another HRESULT appears, diagnose it as a new boundary.
How to distinguish nearby failures
Do not merge neighboring statuses: This is a user-account prerequisite rather than an application token-cache failure. The Online ID password update required diagnosis remains attributable only while the primary record and the affected identity stay fixed.
Evidence that can change the diagnosis
- Primary record: account remediation status and interactive sign-in result.
- Object correlation: keep the product, account, package, device, key, or API identity associated with account remediation status and interactive sign-in result beside the first timestamped result.
- Neighboring-state control: use a controlled comparison that tests whether this is a user-account prerequisite rather than an application token-cache failure; this separates the named condition from a nearby status.
- Before/after result: retain the outcome before and after the corrective action “complete the password update in trusted microsoft account ui”; keep the same identifiers until the broker returns a fresh result.
Evidence-preserving cautions
While investigating this result, do not collect passwords or tokens in diagnostic logs, and do not bypass broker UI with embedded credential forms. That shortcut can replace or invalidate that evidence before the original decision is understood.
Verification
The incident is resolved only when the broker returns a fresh result. Confirm the result by repeating the exact operation that produced this result; maintenance success alone is insufficient.
Technical references
- Microsoft Win32 metadata: winerror.h — status definition reference.
- Microsoft: Errors associated with Web Account Manager — owning service/API reference.
- Microsoft: OnlineIdAuthenticator class — diagnostic/remediation API reference.
- Microsoft: OnlineIdAuthenticator.AuthenticateUserAsync — lifecycle reference.
Looking for a different code? Search another status or error code.