Outlook error 0x80040600 typically means your outgoing mail is stuck because your local data file (PST/OST) is corrupted or full, and the fix usually involves repairing the file or recreating your email profile. This error appears most often when sending or receiving mail in the classic Outlook desktop app, and it can stop all mail activity until resolved. Below are the causes and step-by-step fixes you can try in order, from least to most disruptive.
What Error 0x80040600 Actually Means
The error code 0x80040600 is a MAPI (Messaging Application Programming Interface) error that Outlook uses when it cannot complete an operation on your local mail storage. In plain terms, Outlook cannot write to or read from the .pst (Personal Storage Table) or .ost (Offline Storage Table) file that holds your email, calendar, and contacts on your computer. This is different from a server-side error like 0x8004010F (which means a folder path is missing) or 0x8004060C (which is often a corrupted item). The 0x80040600 code is generic, but it almost always points to a problem with the local data file itself, not with your email server or password.
The most common triggers are:
- The data file has grown to the 2 GB limit (for older PST formats) or is otherwise damaged.
- The file is marked as read-only, or Windows permissions are blocking Outlook from writing to it.
- Antivirus software is scanning or locking the file while Outlook tries to use it.
- The file is stored on a network drive or cloud-synced folder (like OneDrive or Dropbox) that causes conflicts.
- Your Outlook profile (the set of settings that connects to your mail account) is corrupted.
Before You Start: Back Up and Close Outlook
Before making any changes, close Outlook completely. If it is not closing normally, use Task Manager (Ctrl+Shift+Esc) to end any processes named OUTLOOK.EXE. Then locate your data file. In Outlook, go to File > Account Settings > Account Settings, click the Data Files tab, and note the path shown for each entry. That path tells you where your .pst or .ost file lives. Copy that file to a USB drive or another folder as a backup—repair tools can sometimes make things worse, and having a copy lets you revert if needed.
Fix 1: Run the Inbox Repair Tool (ScanPST.exe)
Outlook includes a built-in repair utility for PST files. It is not the same as the “Repair” button in the account settings dialog; that only fixes the profile, not the file. The tool is called ScanPST.exe and is located in the Outlook installation folder. For typical 64-bit installations, the path is:
C:\Program Files\Microsoft Office\root\Office16\ScanPST.exe
For 32-bit Outlook on a 64-bit Windows, it is usually:
C:\Program Files (x86)\Microsoft Office\root\Office16\ScanPST.exe
If you do not find it there, search your C: drive for “ScanPST.exe”. Run the tool, click Browse to select your .pst file, then click Start. It will first check for errors; if it finds any, it will ask if you want to repair them. Click Repair. The tool may take several minutes for large files. After it finishes, open Outlook and try sending a test message. Note that ScanPST only works on PST files, not OST files. If your account is an IMAP or Exchange account (which uses OST), you cannot run ScanPST on it directly; you would need to recreate the profile instead (see Fix 3).
Fix 2: Reduce the Size of Your Data File
If the repair tool finds no errors, the file may simply be too large. Older PST files have a hard limit of 2 GB, and even newer ones can become unwieldy at 20–50 GB. A bloated file can cause write failures that surface as 0x80040600. To reduce size:
- Empty the Deleted Items folder, then right-click it and choose Empty Folder.
- Run File > Tools > Mailbox Cleanup to find large items and old mail.
- Archive old emails to a separate PST file (File > Options > Advanced > AutoArchive Settings).
- If you use a POP account, change the delivery location to a new, empty PST file: File > Account Settings > Account Settings, select the account, click Change Folder, and choose a new PST.
After reducing size, compact the file: File > Account Settings > Account Settings > Data Files tab, select the file, click Settings, then Compact Now. This physically shrinks the file and can clear internal corruption.
Fix 3: Recreate Your Outlook Profile
If the file is fine but the error persists, the profile itself may be corrupted. A profile stores your account settings, server names, and the connection to your data file. To recreate it:
- Open Control Panel (view by Large Icons) and click Mail.
- Click Show Profiles, select your profile, and click Remove. (This does not delete your emails, only the settings.)
- Click Add, give the new profile a name, and enter your email account details. Outlook will set up a new OST/PST file automatically.
- Open Outlook and confirm it uses the new profile (it will ask if you have multiple profiles).
If you had custom settings (like server addresses for a corporate account), you will need to re-enter them. For most users, Outlook will auto-detect the settings from your email address.
Fix 4: Check File Permissions and Antivirus Interference
Sometimes the issue is not the file content but the file’s permissions. Right-click the .pst/.ost file in File Explorer, choose Properties, go to the Security tab, and ensure your Windows user account has Full control. If not, click Edit and grant it. Also, if the file is in a folder that is synced to OneDrive or another cloud service, move it to a local folder like C:\Users\YourName\Documents\Outlook Files and update the profile to point to the new location. Cloud sync can lock the file and cause write errors.
Antivirus programs sometimes scan every file Outlook touches, causing timeouts. Add an exclusion for your Outlook data folder in your antivirus settings, or temporarily disable real-time scanning to test if the error goes away. If it does, keep the exclusion in place.
When to Use a Third-Party PST Repair Tool
If ScanPST fails to fix the file and you cannot recreate the profile (for example, you have a standalone PST that is not tied to an account), you may need a commercial PST repair tool. These tools often recover more data than ScanPST, but they are not free. Before paying, try the free options above. If you do use a third-party tool, run it on a copy of the PST file, not the original, and be aware that some tools can alter the file structure. Always keep your original backup.
Frequently Asked Questions
Will I lose my emails if I delete my Outlook profile?
No. Deleting a profile removes the connection settings, not the actual data. Your emails remain in the .pst or .ost file. When you create a new profile and add the same account, Outlook will either reconnect to the existing file or create a new one. If it creates a new one, you can attach the old file via File > Open & Export > Open Outlook Data File.
Why does this error happen only when sending, not receiving?
Because sending requires Outlook to write a copy to your Sent Items folder in the local data file. If that write fails, the send operation aborts with 0x80040600. Receiving may still work if the server can push new mail into a different folder that is not corrupted.
Does this error mean my email account is hacked or blocked?
No. The error is purely local—it has nothing to do with your server, password, or account status. If your account were blocked, you would see a different error like 0x800CCC0E or a login prompt.
Can I just delete the .ost file to fix this?
Yes, but only for IMAP or Exchange accounts. The .ost file is a cached copy; Outlook will recreate it from the server. Deleting it forces a fresh download. However, if you have offline folders that have not synced, you may lose local changes. For POP accounts, do not delete the .pst file—that is your only copy of your mail.
Will this error go away after a Windows update?
Sometimes. Microsoft has released fixes for specific Outlook bugs that caused 0x80040600. Running Windows Update and Office Update (File > Office Account > Update Options) can resolve a known issue. But if the cause is file corruption, an update will not help.
My error shows a different number, like 0x8004060C. Is that the same?
0x8004060C is a related MAPI error that specifically means “corrupt data” when reading an item. The fixes are the same: run ScanPST, reduce file size, and recreate the profile. The 0x80040600 code is more general, but the troubleshooting path is identical.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- How to Move Data to a New Samsung Galaxy Phone
- Pixel C vs Surface Pro: Key Differences
- iPhone X vs iPhone: Key Differences Explained
- Firefox Bookmark Management Tips & Tricks
- Chromebook Won’t Charge: How to Fix
- How to Delete Photos on Google Drive