Troubleshooting steps to fix ‘scanpst.exe fails with Fatal Error 80040818’

Outlook PST powers the smooth functioning of Outlook by acting as a safe-house for all emails, contacts, calendar entries, notes, etc. associated with user mailboxes. However, with time and continued usage, data keeps piling up within PST files pushing them towards size limit breach and eventual corruption. The ScanPST.exe utility offered by Microsoft comes handy to detect and fix errors and corruption within PST files. While it works in most situations, sometimes it can fail due to several reasons and throw cryptic errors like the ‘Fatal Error 80040818’ leaving users confused and clueless as to what should be done next.

Read on to find out everything there is to know about this error and how you can fix it without much trouble.

Causes that trigger ‘Fatal Error 80040818’

Outlook supports PST files of two formats – ANSI and Unicode. Outlook versions 2002 and earlier supported ANSI format PST files which were bound by a 2GB size limit. This limit was extended to 20GB for Unicode format PST files supported by Outlook versions 2003 and beyond. The amount of data that your Outlook PST can handle therefore depends on the format in which it is encoded. Whenever the size of the PST file approaches its limit, it starts facing the threat of corruption.

Other causes of PST file corruption include:

  • Accessing ANSI format PST file with Outlook 2003 or later versions
  • Over-stuffing PST files with data without cleaning or archiving them once a while
  • Abrupt system termination or Frequent Power surges
  • Virus infection to the files
  • Bad sectors on the hard drive where the PST is saved

If your Outlook PST file has been corrupted owing to any of the above mentioned reasons, you are bound to face problems. Resolving them at the earliest is the only way to get back to work.

Solutions to ‘ScanPST.exe fails with fatal error 80040818’

The Inbox Repair utility ScanPST.exe offered by Microsoft is the first method used by most Outlook users to detect and fix corruptions and other errors within PST files. However, in cases of severe PST corruption, this utility fails to perform its task and terminates throwing errors like ScanPST.exe fails with fatal error 80040818. In such cases, you can try out one of the below mentioned techniques to fix the issue:

  • Reinstall MS Outlook – this might fix any anomalies in PST file behavior
  • Use CHKDSK utility available in Windows OS– this will help repair disk permissions and other system errors
  • Split and Compress PST files – this will help in reducing PST file size which is the original cause of PST file corruption
  • Try moving the corrupted file to a system installed with earlier version of Outlook or convert the Outlook PST file from ANSI format to Unicode format

Though these tricks should help you fix the problem, if the error still doesn’t budge, read the next section to find out our pick for the best PST repair software which will empower you to defeat this error for sure.

Sure-shot remedy for PST file corruption

Extensive research across various popular technical forums point out that the best Outlook repair utility available online is Stellar Phoenix Outlook PST Repair. Powered by advanced scanning and repair algorithms, this software can easily detect and repair corruption within PST files and rid it off all nasty errors. The process is non-intrusive and non-destructive so the format of your PST file data isn’t modified in any way during the repair. A simple 3-step approach (Scan-Preview-Save), fully interactive GUI, and tons of other associated benefits make this software the ideal choice to fix problems like Fatal Error: 80040818.

Wrapping it up

Getting on top of PST file corruption is easy when you have inbuilt utilities like ScanPST.exe. However, such utilities fail when severe corruption strikes. Thus, keeping reliable professional software like Stellar Phoenix Outlook PST Repair handy is the best way to handle such errors.


PST Repair Tool to Recover All Outlook Mailbox Items – Free Trial


  • No Related Posts

Exchange OST to PST Converter

I do not need a solution (just sharing information)

Download Free Exchange OST to PST Conversion Software and easily recover corrupted OST data and convert into Outlook PST format with all Emails, Send Items, Contacts, calendar, Notes, entries, and journals. It has complete solution to import OST files into PST with all emails item. It gives you authority to see preview of their recovered OST files before conversion and convert them into new readable PST files without facing any problems. If you want to restore recover OST file in to Exchange Server and office 365. Download free version software and connect the Exchange server Or Office 365. With the help of this software users can smartly recover their corrupt OST file and successfully convert OST data into PST formats with other format like MSG, EML, EMLX, MBOX, HTML, vCard, and vCal file.
It extremely split large PST file form small PST and provides free demo facility in which you can repair 30 emails per folder into each formats. It can easily convert your lost, damaged or corrupt OST files data such as inbox, outbox, sent items, draft and deleted items etc.
The program is compatible with all versions of MS Outlook 2016, 2013, 2010, 2007, 2003, 2002, 2000, 98 and 97 and 8, 7, Vista, XP, Windows 2000 ( 32bit/ 64bit )

Get More info:      OST to PST    ||    EDB to PST    ||    NSF to PST



  • No Related Posts

Excel files reporting “someone else is working in file” when trying to save to network share

I need a solution

I’ve been encountering an issue with Windows 10 clients using Office 2016 Excel to open/edit/save Excel files to a network share.

We are running a mix of SEP 14.0.3752-14.0.3876 clients, managed by SEPM 14.0.3876. Our file server is Windows Server 2016. Our clients are Windows 10, builds 1607, 1703, and 1709.

What happens in that a user opens the Excel file, makes edits, goes to save, and gets an error that the file is being worked on by another user and cannot be saved (which is not the case). A ######.tmp files gets created on the share (which is normal when an Excel file is saved), but this file should disappear during a proper save. Instead, the ######.tmp file remains, so Excel thinks that the Excel file is in use and fails to save.

The real kicker here is that it happens randomly across various users having the issue, and from one day to the next, I might not see it on the same client working on Excel files on the same share. And I cannot duplicate the error when I try. It is maddening!

Why am I posting this in a Symantec Forum? Because I have tried various workarounds on the Windows side with no luck, but the constant in all this is that SEP is running on my Windows 10 clients (and Windows Server clients). I even removed SEP from the file server hosting the share, leaving only the Windows 10 clients running SEP, but I am still seeing the issue.

Any thoughts? Perhaps SEP is running some sort of scan that is causing the locking, but if that were the case, wouldn’t I see this on all my clients accessing the multiple shares on my servers?



  • No Related Posts

Server Blacklist Removal

I need a solution

I am trying to use but i keep getting an error. 

The IP that is causing problems is 

We cannot send to hotmail and we are not sure why it is on a blacklist. It is not on any other blacklists. 

We saw this message: Yes Blocked due to user complaints or other evidence of spamming

Is it possible to remove this and can you see why it is listed. 

Here is a  Mail Delivery users from that IP are getting with hotmail:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
    host []
    SMTP error from remote mail server after pipelined end of data:
    550 5.7.1 Unfortunately, messages from [] weren’t sent. Please contact your Internet service provider since part of their network is on our block list (AS3150). You can also refer your provider to []

Reporting-MTA: dns;

Action: failed
Final-Recipient: rfc822;
Status: 5.0.0
Remote-MTA: dns;
Diagnostic-Code: smtp; 550 5.7.1 Unfortunately, messages from [] weren’t sent. Please contact your Internet service provider since part of their network is on our block list (AS3150). You can also refer your provider to []



  • No Related Posts

After delete the email document from ICN, the “uploaded successfully” tab was still in Outlook.

The end User select the email message on outlook and add/upload to ICN repository with entry template. Added document can be found in the repository. Email message on outlook have a tag for “Uploaded successfully”.

User delete the email message in the repository. But when user checks back the MS Outlook message. The indicative tag is still showing on the message.

As shown below, those emails uploaded to DMS will have the orange toggle indicator whereas when the email was deleted in DMS, the indicator is not removed.

![alt text][1]

CPE and CEC version; ICN version 3.0.1; Navigator for office plugin 3.0.1

Could you please confirm if this is working as designed? Is the tag just described that the emails have ever been uploaded to ICN successfully? Even if after upload, the document was deleted.

[1]: /answers/storage/temp/19286-download.png


  • No Related Posts