This article provides technical guidance for diagnosing and resolving Microsoft Outlook Send/Receive Error 0x8404060C, typically accompanied by:
Error 0x8404060C
"The message store has reached its maximum size. To reduce the amount of data in this message store, select some items that you no longer need, and permanently (SHIFT + DEL) delete them."
The guidance applies to IT professionals, system administrators, and support engineers managing Outlook environments using PST/OST files.
Affected Product:
Microsoft Outlook (2010, 2013, 2016, 2019, Microsoft 365)
Affected Components:
| Component | Description |
|---|---|
| PST | Personal Storage Table (local data file) |
| OST | Offline Storage Table (cached Exchange / IMAP data) |
Outlook displays this error when the associated data file:
β Reaches the configured maximum file size limit
β Cannot expand further
β Blocks Send/Receive operations
| File Type | Default Limit (Modern Outlook) |
|---|---|
| Unicode PST/OST | ~50 GB |
| ANSI PST (Legacy) | ~2 GB |
Modern Outlook versions use Unicode format, but limits still apply.
Outlook enforces size thresholds via registry-controlled parameters:
β’ MaxLargeFileSize β Absolute limit
β’ WarnLargeFileSize β Warning threshold
Once exceeded:
β Mail flow stops
β Sync errors occur
β Performance degrades
This issue commonly appears in:
β High-mail-volume users
β Shared mailbox caching
β IMAP accounts with large archives
β Systems with disabled archiving policies
β Long-running Outlook profiles
Outlook β
File β Account Settings β Account Settings β Data Files
Check:
β File type (PST / OST)
β Current size
C:\Users\<username>\AppData\Local\Microsoft\Outlook\
Right-click β Properties β Size
If file size is near:
β 49β50 GB β Default Unicode limit
β ~2 GB β Legacy ANSI file
Proceed with remediation.
β Deleted Items
β Junk Email
β Sent Items
β Large Attachments
Use:
SHIFT + DELETE
Important:
β Normal delete = moves to Deleted Items
β SHIFT+DEL = actual removal
Outlook β
File β Tools β Mailbox Cleanup
Useful for:
β Finding large items
β Emptying folders
Reduces internal white space.
Outlook β
File β Account Settings β Data Files β Settings β Compact Now
β Safe operation
β May take time on large files
Use when cleanup is insufficient.
Win + R β regedit
| Outlook Version | Registry Path |
|---|---|
| 2016 / 2019 / 365 | 16.0 |
| 2013 | 15.0 |
| 2010 | 14.0 |
Example:
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\PST
Create:
MaxLargeFileSize
WarnLargeFileSize
MaxLargeFileSize = 102400
WarnLargeFileSize = 95000
β Select Decimal
β Value in MB
| Limit | Value (MB) |
|---|---|
| 75 GB | 76800 |
| 100 GB | 102400 |
| 150 GB | 153600 |
β Warning: Very large files degrade Outlook performance.
β Enable AutoArchive
β Create Secondary PST
β Move older mail
Outlook β
File β Tools β Clean Up Old Items
Useful when OST corruption contributes.
Close Outlook
Navigate:
C:\Users\<username>\AppData\Local\Microsoft\Outlook\
Rename OST file:
mailbox.ost β mailbox.old
Restart Outlook
β Outlook rebuilds cache
| Cause | Explanation |
|---|---|
| No archiving policy | Unlimited mail growth |
| Large attachments | Rapid file expansion |
| Shared mailbox caching | OST inflation |
| Long-lived profiles | Data accumulation |
| Disabled retention rules | Mail never purged |
| Symptom | Likely Cause | Fix |
|---|---|---|
| Send/Receive fails | File size limit | Cleanup / increase limit |
| Outlook slow | Oversized file | Archive / split PST |
| Sync errors | OST bloated | Rebuild OST |
| Frequent freezes | Large mailbox index | Compact / archive |
Increasing file size limits introduces risks:
β Larger PST = Higher corruption probability
β Longer backup times
β Slower search/indexing
β Increased disk I/O
β Keep PST/OST under 20β30 GB for stability
β Implement archiving policies
β Avoid storing large attachments locally
β Use Exchange retention rules
β Periodically compact data files
β Disable shared mailbox caching if unnecessary
Error 0x8404060C is fundamentally a storage limit condition, not a connectivity failure.
Most stable resolution:
β Reduce mailbox size
β Archive aggressively
β Avoid excessive registry expansion
Registry tuning should be considered secondary, not primary.