Outlook 0x800CCC0A Message Download Incomplete: Clear the Stuck Oversized Email

Fix it now

A message did not finish downloading. POP3 works through the mailbox in order, so a single item that never completes stops everything queued behind it. The mail is not lost – it is sitting on the server at the front of the queue, and every cycle restarts the same download and fails at the same place.

1. Sign in to webmail and find the oldest message that has not reached Outlook. Very large attachments and messages with damaged encoding are the usual culprits.
2. Before deleting anything, save what you need from that message. Outlook never received a copy, so the one in webmail is the only copy.
3. Raise the server timeout first and retry – More Settings, Advanced, Server Timeouts – because some downloads fail only because they run out of time, and that costs you nothing to test.
4. Turn off the security product’s email scanning component for one cycle. A scanner that stalls part way through a large message produces the same block.
5. If it still will not download, delete it in webmail, empty the deleted items folder, and run a send and receive so the queue moves past it.

If the mailbox is collected by more than one device, stop the others while you work. Two clients collecting the same POP mailbox on overlapping schedules produce a repeating fault that neither of them can clear.

If the queue moves and later messages arrive, you are done. If it stops again at the next item, the next section explains why POP does this and what changes it permanently.

Why it happens

Microsoft does not publish meanings for 0x800CCC0A, 0x800CCC19, 0x800CCC0B or 0x800CCC17. The usual readings – download incomplete, wait expired, mailbox busy, operation cancelled – are inference. What is not inference is how POP3 works, and that is enough to diagnose this without decoding anything.

POP3 is deliberately simple and strictly sequential. The client asks for a list of messages, retrieves them one at a time, and optionally deletes them. Outlook works from the top of that list. If the retrieval of message three never completes, messages four onwards are never even requested, and the next cycle begins again at message three. Nothing behind it will ever arrive until that item is dealt with.

A download fails to complete for a small number of reasons. The message may be genuinely enormous. The connection may be dropping part way through. A local mail scanner may be buffering the whole thing and running past the timeout. Or the message itself may be malformed, so the server never sends the sequence that marks the end of it and the client waits for something that is not coming.

The companion codes describe the same jam from different angles rather than different problems. A busy or locked response usually means another session still holds the mailbox – which happens when Outlook was closed abruptly, or when a second device polls the same POP mailbox. A cancelled operation is what you get when somebody presses Cancel or closes Outlook part way through a slow download, and it leaves a partial state that makes the next attempt look worse.

Full reference

Reading the pattern

Deleting the blocking message on the server deletes it permanently, because Outlook never received a copy. Open it in webmail and save the attachments and the text first. Where the mailbox is the only place that mail exists, take that step seriously rather than treating the message as disposable.

The order that does not lose anything

1. Stop other devices collecting the same mailbox, so you are the only session.
2. Open webmail and identify the message that has not arrived.
3. Save its attachments and text out of webmail, whether or not you think you need them.
4. Raise the server timeout and retry – this is free and sometimes sufficient.
5. Disable the mail scanning component and retry.
6. Only then delete the message on the server and empty the deleted items folder.
7. Run one manual cycle and let it finish without cancelling.

The durable fix

Everything above clears one jam. The reason this article exists at all is that POP retrieves through a single ordered queue, so one oversized or malformed item stops the mailbox. A protocol that synchronises folders does not have that property: a message that will not download is one message that will not download, and everything else carries on. If this is the second or third time, the useful change is the protocol rather than the message.

For a Microsoft 365 mailbox that means adding it as a Microsoft 365 or Exchange account, which also gives you calendar and contacts and uses modern authentication. For another host it means IMAP. Either is a design decision with consequences for where mail is stored and how it behaves across devices, so treat it as a change to plan rather than an emergency fix – but plan it, because otherwise you will be back.

Why the phone collects it and the desktop does not

• Mobile clients usually fetch headers and small previews first, downloading the body and attachments only when the message is opened.
• That means the huge item is never pulled in full, so it never blocks anything behind it.
• It also means the phone is not proof that the message is fine – it is proof that the phone never tried.
• A phone configured for the same POP mailbox may also be the thing holding the session that Outlook cannot get.
• If the phone is the only device that has ever seen the message body, save it from there before you delete anything.

Every code this article covers

Confirm the fix worked

1. A full send and receive completes and the message count in Outlook matches what webmail shows.
2. Messages newer than the blocked one have arrived.
3. A message with a large attachment downloads successfully.
4. The queue is still moving a day later rather than silently stuck again.
5. Only one device is collecting the mailbox, or the schedules no longer overlap.

Questions people ask about this