Outlook 2016 crashes

Anonymous
2017-06-20T22:00:10+00:00

I have been using Outlook 2016 in Office 365 for a long time and Outlook starting crashing June 19 2017. This may be related to an upgrade of Windows 10 or Office. I have two accounts setup in Outlook, one is a Microsoft Exchange and the other one is IMAP. I have a rule to move messages from the Exchange account to the IMAP account. This has worked perfectly until yesterday. When I start Outlook, it crashes as soon as it starts updating the Inbox. The Event Viewer in Windows gives the following:

Log Name:      Application

Source:        Application Error

Date:          6/20/2017 11:39:17 AM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      VictorLabPC

Description:

Faulting application name: OUTLOOK.EXE, version: 16.0.8201.2102, time stamp: 0x593c2368

Faulting module name: OUTLMIME.DLL, version: 16.0.8201.2025, time stamp: 0x5918d91d

Exception code: 0xc0000005

Fault offset: 0x000000000004e91c

Faulting process id: 0x3190

Faulting application start time: 0x01d2e9db5c8c531a

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: 9e10405d-55ce-11e7-828f-eebe6cc8001c

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2017-06-20T15:39:17.157858900Z" />

    <EventRecordID>31734</EventRecordID>

    <Channel>Application</Channel>

    <Computer>VictorLabPC</Computer>

    <Security />

  </System>

  <EventData>

    <Data>OUTLOOK.EXE</Data>

    <Data>16.0.8201.2102</Data>

    <Data>593c2368</Data>

    <Data>OUTLMIME.DLL</Data>

    <Data>16.0.8201.2025</Data>

    <Data>5918d91d</Data>

    <Data>c0000005</Data>

    <Data>000000000004e91c</Data>

    <Data>3190</Data>

    <Data>01d2e9db5c8c531a</Data>

    <Data>C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE</Data>

    <Data>C:\Program Files\Microsoft Office\Root\Office16\OUTLMIME.DLL</Data>

    <Data>9e10405d-55ce-11e7-828f-eebe6cc8001c</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

The problem stops if I delete the OUTLMMIME.DLL file, but then I cannot transfer email between the accounts. If anyone has a solution, I would really appreciate it. Thanks,

Victor

Outlook | Windows | Classic Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2017-06-28T15:50:59+00:00

The issue with the crash moving email to an IMAP account was caused by a change in the service.  A new property was introduced that Outlook was not handling well.  The Outlook Team has developed a fix for it and it will first release 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.  

In addition to releasing fixes the Outlook Team has requested the property that caused it in the service be disabled until we can get fixes out.  My understanding is that should happen this morning 6/28.  After this is turned off you should not see the issue anymore with new email but it will probably happen with email already stamped with the property.

Was this answer helpful?

30+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2017-07-13T13:02:36+00:00

The fixed build is going to start rolling out today 7/13.  It is not showing yet for me but please try to force the install by clicking File, Office Account, Update Options, Update Now.  The build will be 16.0.8229.2086.  

If Outlook will not start, open Word and click File, Account, Update Options, Update Now.

When builds first go out they are throttled so it will be slowly available at first and then more widely as time goes.

Was this answer helpful?

9 people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2017-06-28T21:55:48+00:00

If you have Outlook on Current Channel and on the fixed build version 16.0.8229.2073 then you should not have any issues.  The fixed build is not yet showing up on the released version pages but I notice Victor was able to update to it today, https://support.office.com/en-us/article/Version-and-build-numbers-of-update-channel-releases-ae942449-1fca-4484-898b-a933ea23def7?ui=en-US&rs=en-US&ad=US.  A new install will pick up the latest build if it is published.  If that fixed build is not out yet you can install Office Insider Slow that has the fix, https://products.office.com/en-us/office-insider.

Was this answer helpful?

0 comments No comments

179 additional answers

Sort by: Newest
  1. Anonymous
    2017-07-11T19:41:27+00:00

    I don't know if this is how they decide when to updated, but I live in the Central Time Zone, and my updates usually come late Tuesday night or early Wednesday morning on all of my computers.  I've been checking several times today, and so far, still no updates, so if one is to come, I am assuming it will be on that timetable.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-07-11T19:39:01+00:00

    The Outlook Team pulled the update that was scheduled for today.  There was another regression that would have made matters worse.  The fix build version remains 16.0.8229.2086 but there will likely be another higher version when the next update comes out.  At this point there are no updates on the schedule until the regression bug is fixed in all channels.  I will post back when I know the next update is scheduled.

    In the meantime if you need to workaround it you could create a new Outlook Profile and put the non IMAP accounts in it, https://support.office.com/en-us/article/Create-an-Outlook-profile-F544C1BA-3352-4B3B-BE0B-8D42A540459D. If you do create another profile you will see this option to Prompt for profile so you can switch between them.  Do not delete the old profile.  It will work again when the fix comes out.  In some cases I have seen adding the IMAP account to the new profile also works because it does not pull down the bad property from the server.

    If you need help creating the new profile please contact support, https://support.microsoft.com.  Point them to this article so they know the issue you are running into, https://support.office.com/en-us/article/Outlook-for-Windows-crashes-on-outlmime-dll-moving-email-to-an-IMAP-account-ee8e5788-7807-49a8-a139-0685f5bfa418?ui=en-US&rs=en-US&ad=US.

    Was this answer helpful?

    0 comments No comments