You're in the middle of sending a routine email, and Outlook throws a dialog box: 0x80040610. The send/receive fails, sometimes the whole client freezes for a few seconds. This usually happens when you're near your mailbox quota at work, but here's the kicker – it also appears when your local PST file (the one that stores your mail on disk) hits its own hard limit. I've seen it on Exchange accounts where the server quota was fine, but the local PST had ballooned to 45 GB. The trigger is almost always the same: you've been archiving years of mail into a single PST, or you never compacted it after mass-deleting old items.
What's Actually Happening Here
Outlook uses two storage systems. For Exchange or Microsoft 365 accounts, mail lives on the server, and Outlook syncs a cached copy. For POP3 or IMAP, everything sits in a PST file. The PST format has a built-in size cap – 20 GB for Outlook 2003 and earlier, 50 GB for Outlook 2007 through 2016 (unless you tweak the registry). When the PST file exceeds that limit, or when the server mailbox quota is exceeded, Outlook can't write new items to the store. That's when you get 0x80040610 – it's a write failure, not a connection issue.
The sneaky part: even if you delete a bunch of mail, the PST file doesn't shrink on its own. Deleted items leave behind empty spaces that the file still counts. The size on disk stays the same until you compact it. So you might have deleted 5 GB of old newsletters, but the PST is still 49.8 GB, and the error persists.
The Fix: Shrink the PST, Not Just the Mailbox
If your mailbox is over the server quota, the answer is blunt: delete mail or ask your admin for more space. But if the PST is the problem, here's the real fix. I'll give you the steps that actually work, in the order you should try them.
Step 1: Check the Actual PST Size
Don't guess. Open Outlook, go to File → Account Settings → Account Settings, then the Data Files tab. You'll see each PST file and its current size. If any PST is above 40 GB, that's your suspect. If you're below the limit but still getting the error, your mailbox quota is the issue – skip to Step 4.
Step 2: Compact the PST
Compaction is the surgical move. It's free and doesn't delete anything. In the same Data Files tab, select the PST, click Settings, then Compact Now. This forces Outlook to rewrite the file, packing the remaining data tightly and dropping the dead weight. On a 40 GB PST, it can take 10–20 minutes. Grab a coffee. Don't close Outlook mid-compaction – you'll corrupt the file.
Step 3: Archive Old Mail to a Fresh PST
If compaction doesn't drop the file below 40 GB, you're still too close to the ceiling. The real solution is moving old mail to a new, separate PST. Create a new PST via File → New → Outlook Data File, name it Archive2020.pst, and then drag-and-drop folders from your main mailbox to the new file. Start with the oldest years – 2010 to 2015. This splits the load. Your main PST drops below 30 GB, and the archive PST starts fresh at 1 GB. The error disappears because neither file is near the cap.
Step 4: If Your Server Mailbox Is Full
When the error is from a server-side quota (you'll usually see a different message like 0x8004060C too, but not always), you need to empty the Deleted Items folder, then run Purge Deleted Items from the folder's right-click menu. Also check the Recoverable Items folder – it's hidden but holds every deleted email for 14–30 days. In Outlook, go to the folder list, right-click Deleted Items, and choose Recover Deleted Items. Permanently delete anything you don't need. That frees up server space instantly.
Step 5: The Registry Tweak (Advanced)
If you absolutely must keep one massive PST, you can raise the limit to 100 GB. This is a registry edit, so only do it if you're comfortable. Close Outlook, open regedit, and navigate to:
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\PSTCreate a new DWORD value named MaxLargeFileSize and set it to 102400 (decimal). Also create WarnLargeFileSize and set it to 102400 to avoid the warning pop-up. The 16.0 is for Office 2016/2019/365 – adjust it to 15.0 for 2013. This works, but I'll be honest: running a 90 GB PST is slow and risky. A crash will cost you more time than archiving ever would.
Still Failing? Check These Three Things
If you've done all this and the error still pops up, you're looking at a different beast. Here's what to check next.
- ScanPST.exe – Outlook's built-in repair tool. Close Outlook, find
ScanPST.exeinC:\Program Files\Microsoft Office\root\Office16(or wherever Office lives), and run it against the PST. It fixes structural corruption that compaction can't touch. - Another PST file – Some users have multiple PSTs loaded, and one of them is the culprit. Check the Data Files tab again. If you've attached an old PST from a previous job, remove it.
- Antivirus interference – Real-time scanning of a 50 GB PST can cause write errors. If you're on Windows Defender, exclude the PST folder (usually
C:\Users\YourName\AppData\Local\Microsoft\Outlook) from scans. This is rare, but I've seen it lock the file mid-write.
The root cause is almost always a PST that's too big or a mailbox that's too full. The fix is to reduce the load, not fight the limit. Compact first, archive second, and only touch the registry if you're desperate.