Independent technical referenceOfficial site
  • Software and digital services
  • Office suites

0x800CCC0E

Microsoft 365 0x800CCC0E in Outlook: IMAP sync fails to connect

Verified with sources2 sourcesReviewed Oct 18, 2026
Technician coming? See the 2 steps they must show you

Risk level

Low

Usually safe to check without specialist tools.

Urgency

Medium

Quick answer

Code 0x800CCC0E in classic Outlook means it cannot synchronize subscribed folders for your IMAP account, often alongside 0x800CCC0F when sending. Wait one hour after a password change for the OAuth token to expire, or remove the MicrosoftOffice16_Data:OAUTH2 entries in Credential Manager.

Safety first

Stop and check this first

  • Removing MicrosoftOffice16_Data:OAUTH2 items in Credential Manager does not delete your email account or messages from Outlook: it only forces a new sign-in prompt.
  • Each Gmail or Yahoo account creates two or four MicrosoftOffice16_Data:OAUTH2 entries in Credential Manager; leaving any of them behind can keep the sign-in prompt from appearing.

Safe checks you can perform

  • Wait one hour if you recently changed your email password
  • Remove MicrosoftOffice16_Data:OAUTH2 entries in Credential Manager
  • Match or delete the affected account subkey under Identities

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Targeted OAuth credential and registry identity cleanup by IT support
  • Do not attempt this professional task: Check for service-side IMAP sync issues with Microsoft Support

What a technician must be able to justify

Technician visit

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Targeted OAuth credential and registry identity cleanup by IT support

    What they doA technician maps the numeric prefix under HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity\Identities to the matching MicrosoftOffice16_Data:OAUTH2 entries in Credential Manager and removes only the broken Gmail or Yahoo identity.

    They must show youwhich Identities subkey matches the affected email address and the fresh sign-in prompt when Outlook reopens.

    In writingwhich MicrosoftOffice16_Data:OAUTH2 entries or registry subkey were removed and confirmation that subscribed folders sync.

  2. Check for service-side IMAP sync issues with Microsoft Support

    What they doIf 0x800CCC0E, 0x800CCC0F or 0x80070057 continues after refreshing OAuth credentials and restarting classic Outlook twice, check with Microsoft Support whether a Microsoft 365 service issue is affecting IMAP OAuth tokens.

    They must show youcurrent Outlook for Microsoft 365 known-issue status and a successful send/receive test after re-authentication.

    In writingthe Microsoft support ticket number, classic Outlook build number and exact error strings recorded.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Follow these steps

Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. Wait one hour if you recently changed your email password

    No special tools

    Who:
    you.
    How:
    if you just changed your Gmail or Yahoo password, wait one hour for the existing OAuth token to expire on its own and then check classic Outlook for a sign-in prompt.
    Result that matters:
    seeing whether Outlook prompts you to sign in automatically once the one-hour token window passes.
    If the sign-in prompt appears and you sign in:
    folder sync resumes without editing Windows credentials.
    If more than an hour passes, or you do not want to wait and 0x800CCC0E remains:
    move on to Credential Manager.
    Evidence to keep:
    screenshot of the send/receive error showing 0x800CCC0E or 0x800CCC0F and the time it occurred.

    Evidence: Users get errors 0x800CCC0E & 0x800CCC0F synchronizing Gmail and Yahoo accounts in classic Outlook

  2. Remove MicrosoftOffice16_Data:OAUTH2 entries in Credential Manager

    No special tools

    Who:
    you, with Outlook closed.
    How:
    close Outlook, open Credential Manager from the Windows Start menu (or Control Panel on Windows 10), select Windows Credentials, scroll to Generic credentials, expand each MicrosoftOffice16_Data:OAUTH2 entry, hover to confirm the full name includes tp_google_imap_Oauth2 or tp_yahoo_imap_Oauth2, and select Remove on all two or four entries for that account.
    Result that matters:
    forcing classic Outlook to prompt you to sign in again without removing or altering the mail account itself.
    If Outlook prompts you to sign in on launch:
    complete sign-in and restart Outlook a second time if sync does not start right away.
    If you have multiple Google or Yahoo IMAP accounts and want to keep the others untouched:
    match the identity number in Registry Editor first.
    Evidence to keep:
    note or screenshot of the MicrosoftOffice16_Data:OAUTH2 entries you removed.

    Evidence: Users get errors 0x800CCC0E & 0x800CCC0F synchronizing Gmail and Yahoo accounts in classic Outlook

  3. Match or delete the affected account subkey under Identities

    Tools required

    Who:
    you, carefully in Registry Editor.
    How:
    if the first workaround does not bring up the sign-in prompt, close Outlook, right-click Start > Run, type Regedit, and open Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity\Identities; inspect each subkey to find the Gmail or Yahoo address that is not syncing (its leading number matches Credential Manager) and delete only that identity subkey before restarting Outlook.
    Result that matters:
    making classic Outlook rebuild the identity entry for that mailbox and display the sign-in window.
    If Outlook asks you to sign in and subscribed folders sync again:
    the stale registry identity was the blocker.
    If 0x800CCC0E persists after signing back in:
    hand the screenshots and account details to support.
    Evidence to keep:
    name of the Identities subkey tied to the affected Gmail or Yahoo address before deletion.

    Deleting the wrong registry key can disrupt other Office sign-ins; delete only the specific Identities subkey that displays the affected Gmail or Yahoo address.

    Evidence: Users get errors 0x800CCC0E & 0x800CCC0F synchronizing Gmail and Yahoo accounts in classic Outlook

Still not solved

If the error persists, stop here. See what the technician must do and show you.

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and digital services
Brand
Microsoft 365
Product type
Office suites

Known code variants

  • 0x800CCC0E
  • 0x800ccc0e Outlook
  • 0x800CCC0F
  • 0x800ccc0f Outlook
  • 800CCC0E
  • error 0x800CCC0E Gmail Outlook
  • Outlook cannot synchronize subscribed folders
  • Outlook no puede sincronizar las carpetas suscritas
  • Sincronización de carpetas suscritas 0x800CCC0E
  • Synchronizing subscribed folders reported error 0x800CCC0E

What it means

On its Outlook for Microsoft 365 known-issues page, Microsoft documents 0x800CCC0E (plus 0x800CCC0F or 0x80070057 on send) when Gmail or Yahoo accounts stop syncing subscribed folders and classic Outlook stops prompting you to sign in. Although a service-side change fixed the February 2026 outage in March 2026, the same symptom still appears after a password change until the OAuth token expires (usually one hour). Other Outlook versions or mail servers may differ, and this code alone never proves your device, account or service is faulty.

Warnings and stop conditions

  • Loweditorial warning

    Removing MicrosoftOffice16_Data:OAUTH2 items in Credential Manager does not delete your email account or messages from Outlook: it only forces a new sign-in prompt.

    Evidence: Users get errors 0x800CCC0E & 0x800CCC0F synchronizing Gmail and Yahoo accounts in classic Outlook

  • Mediumeditorial warning

    Each Gmail or Yahoo account creates two or four MicrosoftOffice16_Data:OAUTH2 entries in Credential Manager; leaving any of them behind can keep the sign-in prompt from appearing.

    Evidence: Users get errors 0x800CCC0E & 0x800CCC0F synchronizing Gmail and Yahoo accounts in classic Outlook

Symptoms and causes

Probable causes · in order

  • Unexpired OAuth token after a password changeCommon

    After you change a Gmail or Yahoo password, the OAuth token cached by classic Outlook normally takes one hour to expire, so Outlook does not prompt for new credentials right away.

    Evidence: Users get errors 0x800CCC0E & 0x800CCC0F synchronizing Gmail and Yahoo accounts in classic Outlook

  • Stale OAUTH2 generic credentials in Windows Credential ManagerPossible

    Saved MicrosoftOffice16_Data:OAUTH2 entries (containing tp_google_imap_Oauth2 or tp_yahoo_imap_Oauth2) stop classic Outlook from asking you to sign in and refresh the account token.

    Evidence: Users get errors 0x800CCC0E & 0x800CCC0F synchronizing Gmail and Yahoo accounts in classic Outlook

  • Stuck account identity subkey in the Windows RegistryLess common

    When removing the generic credentials still does not trigger a sign-in prompt, the account subkey under HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity\Identities holds onto the old identity state.

    Evidence: Users get errors 0x800CCC0E & 0x800CCC0F synchronizing Gmail and Yahoo accounts in classic Outlook

Virtual technician

Does 0x800CCC0E still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Sources and technical references

Sources: Users get errors 0x800CCC0E & 0x800CCC0F synchronizing Gmail and Yahoo accounts in classic Outlook · Los usuarios reciben errores 0x800CCC0E & 0x800CCC0F sincronizar las cuentas de Gmail y Yahoo en la versión clásica de Outlookreviewed 2026-10-18 · verified

Was this entry useful?