| Previous | Next |
| ONL_E_ACCOUNT_LOCKED | ONL_E_EMAIL_VERIFICATION_REQUIRED |
ONL_E_PARENTAL_CONSENT_REQUIRED
ONL_E_PARENTAL_CONSENT_REQUIRED is HRESULT 0x80860008 from Windows Online ID and interactive account authentication. It means that the account requires parental consent before the requested sign-in or data access. The practical shorthand Online ID parental consent required is useful because it points to account age classification, requested scope and consent state as the first evidence to preserve.
How to distinguish nearby failures
Do not merge neighboring statuses: Parental consent is an account policy boundary rather than ordinary application consent. The Online ID parental consent required diagnosis remains attributable only while the primary record and the affected identity stay fixed.
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 primary record supports the reported condition that the account requires parental consent before the requested sign-in or data access. Keep evidence tied to the failing operation.
Evidence that can change the diagnosis
| Record | Why it matters |
|---|---|
| Primary record | Account age classification, requested scope and consent state; this is the shortest evidence path to the decision. |
| Object correlation | Keep the product, account, package, device, key, or API identity associated with the recorded identifiers and values beside the first timestamped result. |
| Neighboring-state control | Use a controlled comparison that tests whether parental consent is an account policy boundary rather than ordinary application consent; this separates the named condition from a nearby status. |
| Before/after result | Retain the outcome before and after the corrective action “complete the official family or guardian consent process”; keep the same identifiers until the broker returns a fresh result. |
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 parental consent before the requested sign-in or data access, together with the code, UTC time, and the same identity fields.
- Change one prerequisite: Complete the official family or guardian consent process; 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-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.