none
Outlook 2016 Constantly Crashing - Microsoft Outlook Has Stopped Working RRS feed

  • Question

  • Tried all the recommended solutions for this but none have resolved the problem. Here is the event log entry...

    Faulting application name: OUTLOOK.EXE, version: 16.0.8201.2075, time stamp: 0x592b575c
    Faulting module name: OUTLMIME.DLL, version: 16.0.8201.2025, time stamp: 0x5918d8e4
    Exception code: 0xc0000005
    Fault offset: 0x0003dfbd
    Faulting process id: 0x610
    Faulting application start time: 0x01d2e187d131f910
    Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE
    Faulting module path: C:\Program Files (x86)\Microsoft Office\Root\Office16\OUTLMIME.DLL
    Report Id: 145e7d19-4d7b-11e7-9bf6-2016d8a0ea32
    Faulting package full name:
    Faulting package-relative application ID:

    Saturday, June 10, 2017 1:31 AM

All replies

  • Tried all the recommended solutions for this but none have resolved the problem.

    Could you please share more details on what exact steps you've tried so far? At which exact point will you experience this issue?

    Try to perform a repair of your Office installation (assuming that you haven't tried it yet) via Control Panel, and see if it works:

    https://support.office.com/en-us/article/Repair-an-Office-application-7821d4b6-7c1d-4205-aa0e-a6b40c5bb88b

    Regards,

    Ethan Hua


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, June 12, 2017 9:17 AM
    Moderator
  • Hi @0MattEllis0,
    Sorry to hear that your Outlook has stopped working but let me know what's the result after repairing office installation. Can you please make an attempt to start Outlook in safe mode and see the result.
    If the problem continues in safe mode, You should repair your Outlook data file using Inbox repair tool or using any Free OST Repair tool as sometimes Outlook gets stuck in processing when there exist corruption issue in Outlook data file. 
    Still facing issue?
    There might issue caused by add-ins. Sometimes installed add-in creates issues, make sure to start Outlook without add-ins. 
    I would like to suggest you a blog which will fix your issue - How to Fix Outlook Not responding !!

    Good luck with your fixing issue. 

    • Edited by aliceaggie Tuesday, June 13, 2017 5:59 AM
    Tuesday, June 13, 2017 5:53 AM
  • In Control Panel, choose Programs and Features.

    In the list of installed programs, right-click Microsoft Office 2016 or Microsoft Office 2013, and then choose Change.

    If repairing your Office programs didn't resolve your issue, then you can also download free OST to PST Converter, which helps you to repair corrupt/orphaned Outlook data file.

    PS: Make sure to Quit any Office programs that are running while using manual solution.

    Wednesday, June 14, 2017 6:53 AM
  • Hi,

    How is it going? Are you unblocked on this?

    Please feel free to let us know if you need any further assistance.

    Regards,

    Ethan Hua


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, June 15, 2017 6:38 AM
    Moderator
  • I've been experiencing exactly the same problem as 0MattEllis0, but it only started a few days ago and nothing on the PC had changed; not installed any new s/w or carried out any h/w changes.

    However I might have discovered the cause.  By disabling all the add-ins and re-enabling them one by one, it appears that the "Kaspersky Outlook Anti-Spam Addin" is the culprit.  If I leave this disabled everything seems to be fine, but the moment it's enabled, Outlook crashes.

    Don't really understand this as I've used Kaspersky for years without any problems and I'm not aware of any update/upgrade that's been applied in recent times.

    Hope this helps anyone else who's experiencing this frustrating problem.

    Note to MS: More meaningful error messages/information would make troubleshooting a whole load easier !!

    Thursday, June 22, 2017 10:37 AM
  • @Malc45
    Me too, interestingly I postponed a recommended update only to 'go all blonde' and accidentally install it a few days back; then wham outlook starts breaking. Using google and the crumbs of clues I found the KIS plugin at fault, which then led me to find out about the systems info tool just search for Kaspersky + GetSystemInfo5.2. The results from this useful tool spurned a search for the reported cause of fault (Exception code: 0xc0000005 Fault offset: 0x0003dfbd Faulting process id: 0x1384 - OUTLMIME.DLL), I also wasted half an hour with the hopeless MSRA for oriffice 365 tool (should that be the MRSA tool?). Further search led me here, where on reading your post, kerching, me too. Anyone reading this should ignore the wannabe microsoft MVP's, and run the Kaspersky systems info tool, and check the properly reported errors it generates instead of the rubbish spouted by the offcial microsoft tool. Could this be pure coincidence, or is this a sign of things to come for Kaspersky users? (see theregister.co.uk/2017/06/06/windows_defender_competition_complaint/)

    Thursday, June 22, 2017 7:59 PM
  • Me too - trouble only started last Friday for me.  But since then Outlook just crashes within 30 seconds of opening.  Always same error content:

    Application Error Faulting application name: OUTLOOK.EXE, version: 16.0.8201.2102, time stamp: 0x593c233a
Faulting module name: OUTLMIME.DLL, version: 16.0.8201.2025, time stamp: 0x5918d8e4
Exception code: 0xc0000005
Fault offset: 0x0003dfbd
Faulting process ID: 0x1a30
Faulting application start time: 0x01d2ecfc0c3a6fbb
Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE
Faulting module path: C:\Program Files (x86)\Microsoft Office\Root\Office16\OUTLMIME.DLL
Report ID: febddf56-310c-456b-b738-b503be78d4a1
Faulting package full name: 
Faulting package-relative application ID:

    Unlike 0MattEllis0 I use Norton INtenet Security but even if I have the anti-spam add-in disabled and even the main functionality disabled Outlook still crashes so I would not attribute anything to security software.  I think it is more related to the search fault caused by the KB4022405 from June 14th as after that time the search function leaves Outlook data files open causing them to become corrupted.  If you have multiple data files in your profile they all become corrupted and SCANPST can't even fix them!

    That's my current status after two days of 8 hours of MS Level2 support effort now escalated to Level 3 who is still unable to fix the problem.

    Saturday, June 24, 2017 3:44 PM
  • I am having same issue only I have McAfee for Antivirus.  I don't think is related to Antivirus.  Sounds more like the Outlook data file has gotten corrupted but not sure what to do about it.  I have several email accounts active on this install of outlook...know that I added a new gmail email account to outlook and that is when mine started crashing.
    Monday, June 26, 2017 1:52 PM
  • I too am having this same issue with Outlook 2016 (Office 365 version) running on Windows 10 Pro on a Surface Book.

    it started on Friday 23/06/2017 when Outlook had been working just fine on this machine for about a year.  I move an email from a folder in my Hotmail account into a folder that is in an account connected via IMAP.  This is something that I've been able to do perfectly OK

    Outlook crashed, and thereafter crashes a small number of seconds after startup.

    The same thing happens in Safe Mode, so I don't believe it is any Add-In causing the problem. (And besides the addins have not changed since the setup when it was working just fine)

    No software updates other than Windows and Office updates have been applied in the time before the crash started happening.

    My first course of action was to try starting ourlook in Safe Mode, but this also crashes after just a few seconds.

    Next step was to carry out the "Online Repair" of Office from the Control Panel, but this didn't solve anything

    I ran the mailbox  PST/OST repair tool on all the PSTs (just one of them) and OSTs (3 of them) but still didn't work.

    So I tried some further things:

    Starting Outlook with a brand new Mail Profile with no accounts added to it works just fine.

    Removing the IMAP account that the email was moved into from the original profile and again it works fine.

    So then I re-added that account and all was OK for a few days

    Today I moved an email from Hotmail account into the newly added IMAP account and the same behaviour has come back

    Outlook crashed, and now crashes a few seconds after start-up whether in safe mode or not

    Some other people on this thread have had the problem appear in the last few days or weeks, so it really looks like a recent Windows or more likely recent Office (Outlook) update has caused this.

    Looks like OUTMIME.DLL was updated on 14/06/2017 and probably started being used when I restarted my machine for the first time in a while on 21/06 or 22/06, just before the problem started happening in Outlook

    <svg style="width:100% !important;height:100% !important;"><polyline points="" style="fill:none !important;stroke:#1ba1e2 !important;stroke-linecap:round !important;stroke-linejoin:round !important;stroke-width:7 !important;"></polyline></svg>
    • Edited by TimDSMoss Monday, June 26, 2017 3:20 PM updated with screenshot
    Monday, June 26, 2017 3:11 PM
  • same issues here, tried all the steps above and no luck.  i have even tried to roll back office versions and still same issue
    Monday, June 26, 2017 10:10 PM
  • @Malc45

    Same here - I've done the same steps. Running Outlook in safe-mode (at command-prompt: Outlook.exe /safe) and disabling add-ins. After disabling the Kaspersky-Addin Outlook works again.


    • Edited by anykéy Tuesday, June 27, 2017 8:24 AM
    Tuesday, June 27, 2017 8:19 AM
  • I am having the exact same issue.  

    I am running both Exchange and IMAP accounts in Outlook.  

    Outlook repeatedly crashes after approximately 30 seconds, since 22nd June.

    I have tried running in Safe Mode and it still crashes.

    I have disabled all add-ins.

    I have disabled antivirus.

    I am not running MalwareBytes.

    I have deleted OST files.

    I have tried repairing Office 2016.

    I have tried a full re-installation of Office 2016.

    I still get the same error:

    Faulting module name: OUTLMIME.DLL, version: 16.0.8201.2025

    I've seen a thread on answers.microsoft.com with several other people facing the same problem.

    https://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook-mso_win10/outlook-2016-crahes/d0528755-6495-4a9f-b8fb-cd5c9a1fd53a?


    Any updates on when a fix is going to be made available please?

    Tuesday, June 27, 2017 10:10 PM
  • A solution that worked for me:

    For all who is having this type of problem. I tried everything posted here and nothing worked. Since I'm using IMAP emails, I only backed up the old OST fiiles in a different folder and then opened the outlook as usual. The software will recreate the OST folders by downloading the required information from the servers.

    It took a while because I'm syncing contacts, emails and calendar with my outlook account. I use that in android phone and tablet so everything is synced and I do not depend on the particular computer I'm using. Everything is stored in the cloud so nothing is lost when these repeated problems happen.

    I strongly recommend to do that: back up the OST IN A DIFFERENT FOLDER and then open Outlook. Please, let us know here whether this works for those of you who try it

    best of lucks.


    Wednesday, June 28, 2017 8:55 AM
  • I have tried backing up the OST files and recreating.  After 10 minutes, when the new OST files start generating, the same issue arises and it crashes with the same error.  And then you are back to crashing every 30 seconds.

    Wednesday, June 28, 2017 10:47 AM
  • This reply from Kaspersky Tech Support on this issue:

    "Dear customer,
    Sorry about this.
    According to our headquarters, this situation has been identified as bug 2268278. We are working on a fix, and will update you once one is made available.
    As a temporary solution, please disable the Anti-Spam addin in Outlook.
    Apologies for any inconvenience caused."
    Wednesday, June 28, 2017 2:57 PM
  • Root cause unrelated to Kaspersky.

    Better info in this thread.

    Wednesday, June 28, 2017 4:53 PM
  • Hi All,

    We are aware of this issue and have fixed it for the next update.

    If you need to workaround it for now, try to revert to an earlier build that does not have the issue:

    https://support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-clic

    Let me know if you have any other concerns.

    Regards,

    Ethan Hua


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, June 30, 2017 5:08 AM
    Moderator
  • Hi, 

    For me this has started happening in build 8229.2073. I am not sure which one was installed before (I am Inside Slow). Is this the "next update", or is it the one that is supposed to be broken?

    I have tried going back to build 8201.2075 and I still have the same problem. 

    I cannot install any earlier build: ClickTuRun tells me that "The latest version of Office approved by my system admin is installed" when I try to install 8067.2157.

    This is the error I now get:

    Faulting application name: OUTLOOK.EXE, version: 16.0.8229.2073, time stamp: 0x594d2c28
    Faulting module name: OUTLMIME.DLL, version: 16.0.8229.2073, time stamp: 0x594d5f0a
    Exception code: 0xc0000005
    Fault offset: 0x000000000004e8fc
    Faulting process ID: 0x4038
    Faulting application start time: 0x01d2f178ef354ee2
    Faulting application path: C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE
    Faulting module path: C:\Program Files\Microsoft Office\Root\Office16\OUTLMIME.DLL
    Report ID: b0d3401a-55f2-405f-bff1-13b473b29b63
    Faulting package full name:
    Faulting package-relative application ID:



    • Edited by Wigster Friday, June 30, 2017 9:20 AM
    Friday, June 30, 2017 8:52 AM
  • When should the fix be ready. 

    How exaclty do I revert to a previous version. To which Version exactly.

    Friday, June 30, 2017 7:35 PM
  • Hello - when can we expect this update this is causing major problems?

    Thank you.

    Sunday, July 2, 2017 4:23 PM
  • Hi there,

    The Outlook Team has developed a fix for it and it was first released to Current Channel ETA 6/29-6/30 currently scheduled as build 16.0.8229.2073.  Fixes for all other versions including MSI are in process but not yet scheduled.  

    If there is anything new, I will update here. Thanks for your great understanding.

    Regards,

    Ethan Hua


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, July 4, 2017 9:19 AM
    Moderator
  • Hi,

    I upgraded to the latest version today (version 1706 (Build 8229.2073)), and it still crashes with the below log:

    Faulting application name: OUTLOOK.EXE, version: 16.0.8229.2073, time stamp: 0x594d2c28
    Faulting module name: OUTLMIME.DLL, version: 16.0.8229.2073, time stamp: 0x594d5f0a
    Exception code: 0xc0000005
    Fault offset: 0x000000000004e8fc
    Faulting process id: 0x2a78
    Faulting application start time: 0x01d2f501c3ea746b
    Faulting application path: C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE
    Faulting module path: C:\Program Files\Microsoft Office\Root\Office16\OUTLMIME.DLL
    Report Id: 1e72f40b-60f5-11e7-82db-b82a72ca103d
    Faulting package full name: 
    Faulting package-relative application ID: 

    I have moved out the OUTLMIME.DLL file and now it does not crash when i open Outlook, but sending from IMAP accounts results in Outlook getting "stuck" in "Preparing to Send/receive".

    Any ideas on what to do? 

    Thanks!


    Tuesday, July 4, 2017 8:28 PM
  • Hi,

    I upgraded to the latest version today (version 1706 (Build 8229.2073)), and it still crashes with the below log:

    Faulting application name: OUTLOOK.EXE, version: 16.0.8229.2073, time stamp: 0x594d2c28
    Faulting module name: OUTLMIME.DLL, version: 16.0.8229.2073, time stamp: 0x594d5f0a
    Exception code: 0xc0000005
    Fault offset: 0x000000000004e8fc
    Faulting process id: 0x2a78
    Faulting application start time: 0x01d2f501c3ea746b
    Faulting application path: C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE
    Faulting module path: C:\Program Files\Microsoft Office\Root\Office16\OUTLMIME.DLL
    Report Id: 1e72f40b-60f5-11e7-82db-b82a72ca103d
    Faulting package full name: 
    Faulting package-relative application ID: 

    I have moved out the OUTLMIME.DLL file and now it does not crash when i open Outlook, but sending from IMAP accounts results in Outlook getting "stuck" in "Preparing to Send/receive".

    Any ideas on what to do? 

    Thanks!

    Thank you very much for the update.

    We're aware of this and are actively working on it. Currently, there is no exact release date can be provided. If there is anything new, I will update you all here.

    Regards,

    Ethan Hua


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, July 5, 2017 7:45 AM
    Moderator
  • Still can't use my Outlook :-/

    What about the mails I was trying to move. Will they be gone?

    Tuesday, July 11, 2017 6:40 AM
  • Would love to be able to use my Outlook again sometime (including the mails I was trying to move on my IMAP).

    Thanks!

    Tuesday, July 18, 2017 8:50 AM
  • I have a user that is using version 1706 (Build 8229.2086) Click to Run that is having the same issue 

    Faulting application path: C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE
    Faulting module path: C:\Program Files\Microsoft Office\Root\Office16\OUTLMIME.DLL

    Thanks 

    Scott Foster

    Tuesday, July 18, 2017 2:53 PM
  • I've the same problem with Outlook 2010, running with one local PST and some IMAPs. Rebuilding OST file does not have an effect.

    Outlook crashes when I try to move some  mail entries from one account to another.

    I'm running ESET NOD32 Antivirus on a Windows 10 Pro 64Bit Intel NUC.

    Signaturdatenbank: 15780 (20170720)
    Soforteinsatz-Modul: 10413 (20170720)
    Updates: 1010 (20170621)
    Viren- und Spyware-Schutz: 1522.1 (20170621)
    Advanced Heuristik: 1177 (20170220)
    Archivunterstützung: 1265 (20170623)
    Säuberungstechnologie: 1135 (20170505)
    Anti-Stealth-Unterstützung: 1113 (20170530)
    ESET SysInspector: 1269 (20170321)
    Lokalisierungsunterstützung: 1611 (20170627)
    HIPS-Unterstützung: 1290 (20170705)
    Internet-Schutz: 1310 (20170630)
    Datenbank: 1091 (20170620)
    Konfigurationsmodul (33): 1483.3 (20170413)
    LiveGrid-Kommunikationsmodul: 1022 (20160401)
    Spezielles Säuberungsprogramm: 1012 (20160405)
    Rootkit-Erkennungs- und Bereinigungsmodul: 1018 (20170601)
    Netzwerk-Schutzmodul: 1494 (20170720)
    Schutz vor skriptbasierten Angriffen: 1018 (20170616)
    Support-Modul für das Kryptografieprotokoll: 1018 (20170613)


    Holger

    Thursday, July 20, 2017 7:37 PM
  • I have an Customer with similar Problem. after starting Outlook IMAP syncs and after some seconds Outlook crashed with:

    Name der fehlerhaften Anwendung: OUTLOOK.EXE, Version: 16.0.4549.1002, Zeitstempel: 0x5929678b
    Name des fehlerhaften Moduls: OUTLMIME.DLL, Version: 16.0.4549.1000, Zeitstempel: 0x591b5308
    Ausnahmecode: 0xc0000005
    Fehleroffset: 0x0003c4d0
    ID des fehlerhaften Prozesses: 0x1e98
    Startzeit der fehlerhaften Anwendung: 0x01d2fb9f2660995f
    Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Microsoft Office\Office16\OUTLOOK.EXE
    Pfad des fehlerhaften Moduls: C:\PROGRA~3\MICROS~1\Office16\OUTLMIME.DLL
    Berichtskennung: 9b3abb1a-0f94-45d4-b72e-e43a250c641a
    Vollständiger Name des fehlerhaften Pakets:
    Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

    I have found following: I started with new account and set the amount of offline saved time first to 1 Month, ALL OK.

    them every time all worked i set it to one Option more. until to ALL Mails. Now it crashed again.

    the Provider is T-Online and the size on Server of saved mails is about 6GB ! The Offline OST is only 4.6GB !

    It Looks like either the amount of mails or a faulty mail on the Server produces the Error.


    regads, A. Jacubowsky

    Monday, July 24, 2017 9:28 AM
  • from this https://support.office.com/en-ie/article/Outlook-for-Windows-crashes-on-outlmime-dll-moving-email-to-an-IMAP-account-ee8e5788-7807-49a8-a139-0685f5bfa418?ui=en-US&rs=en-IE&ad=IE&fromAR=1 the problem should be solved.

    But it is still there. Yesterday I updated my Office Pro Plus 2016 to version 1706 (build 8229.2103) and I see there is a OUTLMIME.DLL Version 16.0.8229.2086, but invoking the IConvertersession the application crashes. This can be reproduced with MFCMapi converting a eml to msg, too.

    regards, Toni Santa

    Thursday, July 27, 2017 1:30 PM
  • In the hopeness Microsoft will solve the problem with the next Office-update, in the meantime I went back to a previous build of Office. This can be done by creating a batch-file (.bat) with following lines on Desktop and launching it:

    rem May 9, 2017
    cd %programfiles%\Common Files\Microsoft Shared\ClickToRun
    officec2rclient.exe /update user updatetoversion=16.0.7967.2161

    I hope this helps.

    Toni

    Thursday, July 27, 2017 3:26 PM
  • Hi,

    the problem is still there after last update to v. 1707 build 8236.2087. Dear Microsoft, are there any plans to solve the issue?

    Toni

    Saturday, August 26, 2017 8:36 PM
  • Add me to this issue!

    Tuesday, September 12, 2017 6:48 PM
  • Another month passed with several updates of Office (at the moment of writing this reply it's v 1708 build 8431.2079) but the problems are still there. Please, solve the issues with IConverterSession and closing a third-party application accessing the MAPI-session.

    Thursday, September 28, 2017 3:59 PM
  • With update to v 1709 the bugs are fixed.
    • Proposed as answer by MT25 Securities Wednesday, October 25, 2017 9:37 PM
    Thursday, October 19, 2017 9:30 AM
  • Update V1709 problem continues.......

    Thought I'd struck gold with this post as it was long, detailed and explained ALL the issues I was having. 

    My Outlook 2016 version V1709 Build 8528.2139 is still doing exactly the same as above.  Regardless of what is disabled, removed, repaired, etc... will continue to have Outlook crash in approx 30 seconds.  Only way I can keep it open is to open Outlook then immediately access File -> Options and just let it the Options box stay open... Outlook won't crash.  As soon as I close the Options box and Outlook continues to load - BOOM, crashes.

    My Application Error message

    Faulting application name: OUTLOOK.EXE, version: 16.0.8528.2139, time stamp: 0x59e046a3
    Faulting module name: OUTLMIME.DLL, version: 16.0.8528.2136, time stamp: 0x59d6c23f
    Exception code: 0xc0000005
    Fault offset: 0x0003af27
    Faulting process id: 0xcf8
    Faulting application start time: 0x01d34dd51c09d6c5
    Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE
    Faulting module path: C:\Program Files (x86)\Microsoft Office\Root\Office16\OUTLMIME.DLL
    Report Id: 627e8515-b9c8-11e7-bb2b-1866da149b76

    Older PST file works great - but I'm pretty indebted to my current one with required e-mails.

    Sure hope there's a fix ASAP

    Wednesday, October 25, 2017 9:45 PM
  • Hi, could it be your are working on a Windows, where your upgraded from Outlook 2013 to Outlook 2016? I had a similar problem on such PC, since the upgrade does not change all the registry-keys pointing to OUTLMIME.DLL, so someone was still pointing to the previos one. Try to find "outlmime.dll" in regedit and change them manually.

    Is your pst on a network drive? If so, move it to a local one. Excude .pst from antivirus-check.

    Create a new pst, if it works, import the missing mails from "old" pst.

    Did you try to repair the pst with scanpst.exe?

    Toni

    Thursday, November 2, 2017 9:36 AM
  • We have multible users, with same Outlook problem occuring after update to v 1709 the last days.

    we don't know what to do!!!!!


    ksa

    Tuesday, November 14, 2017 11:59 AM
  • DataVare OST to PST Software is brilliant tool to convert your outlook OST file to PST file format with extract all email folders like- Inbox, Outbox, Delete Items, Notes, Draft and Contacts and other.This utility is really works out to get OST data back in original format.It's One of the best solution to recover and convert OST file to PST file. This tool is specially designed to repair damaged or inaccessible Outlook data file and save them new PST, MSG, EML and HTML file formats. Convert OST To PST is the best converter/repair/restore software which can repair your damaged and corrupted OST files and restores into a new PST file format.

    One of the great and successive solution which able to fix all the corruption issues of OST files and used for conversion OST files to PST files. This OST to PST Converter is more potentiality more conductive for MS Outlook users. In very easy and successive manner, the Outlook admin can successfully neutralize the entire issues of MS Outlook OST File and obliterate the entire impossibilities which could be hurdles in opening an .ost file.The program is proficient enough to export all the properties like To, Cc, Bcc, Date, subjects, and email headers in new file.
    Saturday, January 6, 2018 10:24 AM
  • Thanks for the suggestion. Also, it worked for me.
    Thursday, February 22, 2018 9:49 AM
  • for me it apparently solved the problem. Thank you

    Friday, March 16, 2018 8:29 PM
  • In that list are several OST-to-PST converters.  But they all specifically mention that they recover damaged or corrupt OST files.  I'm not sure if they would be applicable in my case--I do not have a damaged OST

    Visit at ; http://www.osttopstapp.com/

    Friday, November 30, 2018 4:37 AM
  • I'm resurrecting this old thread because today I had to deal with this issue and i found that the most common and widespread workaround that can be found online to fix it (at least as of today) is the one described in the following posts:

    Basically, such workaround is based on a "double change" of the root folder in the offending IMAP account's configuration settings, with the aim of forcing Outlook to "acknowledge" the (double) change and perform a series of internal activities which, in turn, should fix the root issue. This is a procedure that, other than being extremely slow when dealing with multiple IMAP accounts, doesn't seem effective in a vast majority of scenarios where this annoying problem actually occurs.

    For this very reason I suggest the following workaround, which is much simpler to put into practice than the previous one and, most importantly, has a 100% success rate (at least until now - and I had to pull it off quite a lot):

    • Go to Control Panel > Mail > E-Mail Account.
    • In the popup window that will appear, take note of all the IMAP accounts (E-Mail panel) and the .ost file paths (Data Files panel).
    • Navigate through the folder containing the .ost files (you can easily do that from the Data Files panel using the Open file location button).
    • Create a new BACKUP_yyyyMMdd folder within the folder containing the .ost files.
    • Move all the .ost files related to the IMAP accounts that you identified earlier.
    • Launch MS Outlook again.

    During its startup phase, Outlook should automatically retrieve all the IMAP messages from the configured mail accounts from the mail server, reconstructing the .ost files that we moved earlier. The whole procedure could last a few minutes or even a few hours, depending on the connection speed and/or the number of messages to be recovered. The good news is that the messages will be retrieved in order of arrival (from the most recent to the least recent) in the background, thus allowing us to work immediately with Outlook without having to wait for the conclusion.

    As soon as the download/reconstruction process is completed we'll just have to confirm that all the messages have been recovered: once done, we can safely delete the BACKUP_yyyyMMdd folder created previously.

    That's it :) 

    For further details on this issue, read this post.


    • Edited by Ryan v2MVP Monday, July 22, 2019 3:39 PM
    Monday, July 22, 2019 3:39 PM