| Previous | Next |
| ONL_E_FORCESIGNIN | ONL_E_PARENTAL_CONSENT_REQUIRED |
ONL_E_ACCOUNT_LOCKED
0x80860007 is represented by ONL_E_ACCOUNT_LOCKED. In Windows Online ID and interactive account authentication the specific outcome is that the Online ID account is locked after excessive or risky sign-in attempts. The phrase Online ID account locked narrows the first diagnostic record to lockout time, preceding attempts and account recovery 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 Online ID account is locked after excessive or risky sign-in attempts. 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 Online ID account is locked after excessive or risky sign-in attempts, together with the code, UTC time, and the same identity fields.
- Change one prerequisite: Stop retries and complete official account unlock or recovery; 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.
Evidence that can change the diagnosis
- Primary record: lockout time, preceding attempts and account recovery result.
- Object correlation: keep the product, account, package, device, key, or API identity associated with lockout time, preceding attempts and account recovery result beside the first timestamped result.
- Neighboring-state control: use a controlled comparison that tests whether account lockout differs from request throttling and application invalidity; this separates the named condition from a nearby status.
- Before/after result: retain the outcome before and after the corrective action “stop retries and complete official account unlock or recovery”; keep the same identifiers until the broker returns a fresh result.
How to distinguish nearby failures
Do not merge neighboring statuses: Account lockout differs from request throttling and application invalidity. The Online ID account locked diagnosis remains attributable only while the primary record and the affected identity stay fixed.
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.