0X8004016D

CS_E_ADMIN_LIMIT_EXCEEDED (0X8004016D) – File too big for Outlook

This error means Outlook or Windows blocked a file because an admin set a size limit. The fix is quick – tweak a registry value or Group Policy.

Yeah, this error is a pain – but it's usually an easy fix

You're trying to send an email or save a file in Outlook, and you get that dreaded CS_E_ADMIN_LIMIT_EXCEEDED (0x8004016D) message. The system tells you the object exceeds the maximum size set by the administrator. I've seen this in Outlook 2016, 365, and even Exchange public folders. The good news? It's rarely a broken install – it's a size cap someone set.

The real fix: adjust the attachment size limit

Most of the time, this error comes from Outlook's attachment size limit. By default, Outlook caps attachments at 20MB for many versions. But some admins drop that lower, or you're hitting a mailbox size limit. Here's what I do first:

  1. Check the mailbox size limit – If you're on Exchange, the server might limit total mailbox size. Right-click your mailbox in Outlook, choose Data File Properties, then General tab. Look at the size. If it's near the limit (often 50GB), you need to archive or delete.
  2. Bump the attachment limit via registry – This is the most common fix. Close Outlook completely.
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Preferences]
"MaximumAttachmentSize"=dword:00019000

That sets the limit to 100MB (in kilobytes: 100*1024 = 102400 = 0x19000 in hex). If you're using Office 2013, replace 16.0 with 15.0. For 2010, it's 14.0. Restart Outlook and try again.

Still not working? The limit might be set via Group Policy. If you're on a work network, your IT team probably pushed a policy. Run gpedit.msc and check:

User Configuration > Administrative Templates > Microsoft Outlook 2016 > Outlook Options > Preferences > E-mail Options > Maximum attachment size

If it's enabled, you'll see the limit. Change it or ask your admin to do it.

Why does this happen?

Admins set size limits to keep mailboxes healthy – no one wants a 500MB email clogging up the server. But sometimes the limit is too aggressive. I had a client last month whose entire print queue died because of a 10MB attachment cap on a shared mailbox. The registry tweak above fixed it in 30 seconds.

Less common variations of the same issue

Public folder size limits

If you're getting this error when posting to a public folder, the folder itself has a size limit. In Outlook, right-click the public folder, choose Properties, then the General tab. Under Folder size, click Folder Size to see the limit. You can't change it from Outlook – the Exchange admin needs to adjust the quota in the Exchange Admin Center under Public Folders > Mailbox > Quotas.

OneDrive or SharePoint file sync

This error can also pop up if you're syncing large files to OneDrive or SharePoint through Outlook. The fix there is different – you need to increase the file size limit in SharePoint Admin Center under Settings > File size limit. I've seen this with 15GB video files that people try to email – the system just says no.

Windows clipboard limit

Rarely, the error appears when copying a huge chunk of data (like a 200MB email) to the clipboard. The COM+ component that handles clipboard data has a default size limit. You can increase it via registry but honestly, it's almost never the issue. Check the file you're trying to copy – if it's over 100MB, just don't.

How to prevent this from coming back

  • Monitor your mailbox size – Keep it under 90% of the limit. Use Outlook's Mailbox Cleanup tool (File > Info > Tools) to archive old emails.
  • Adjust attachment limits proactively – If you're an admin, set a reasonable limit like 50MB. Don't use the default 20MB unless you have to.
  • Use links instead of attachments – For files over 10MB, upload to OneDrive or SharePoint and share a link. Outlook can auto-do this if you enable it.
  • Check Group Policy changes – If your IT team pushes a new policy, test it on a pilot group before rolling out. I've seen policies drop the limit to 5MB without warning – chaos.

Bottom line: 0x8004016D is almost always a limit, not a bug. Bump the limit, and you're back in business.

Related Errors in Windows Errors
0X80110423 COMADMIN_E_REGISTRARFAILED 0X80110423: Real Fixes That Work 0XC00A000E Busy signal error 0xC00A000E on callback fix 0XC00D10A3 NS_E_WMPCORE_PLAYLIST_ITEM_ALTERNATE_INIT_FAILED (0XC00D10A3) Fix 0XC0000467 STATUS_FILE_NOT_AVAILABLE (0XC0000467) Fix

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.