Outlook | MacOS | Legacy Outlook for Mac | For home
Using older versions of Outlook for Mac for personal email and calendar
That worked for about 15 minutes, then Outlook updated and I'm back to crashing very time it opnes.
Outlook Crashes Shortly After Starting
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
I've been running the Office aps for quite a while, and this just started happening. Shortly after I ope Outlook, I get a message saying "There was a problem with Microsoft Office and your recent work might be lost." I have tried restrating the computer and also re-installing Office. I'm running OS 10.13.6 (the latest version that my old computer will support).
The first part of the error report is:
Microsoft Error Reporting log version: 2.0
Error Signature:
Exception: EXC_BAD_ACCESS
ExceptionEnumString: 1
Exception Code: KERN_INVALID_ADDRESS (0x0000000000000000)
Date/Time: 2021-05-24 23:53:33 +0000
Application Name: Microsoft Outlook
Application Bundle ID: com.microsoft.Outlook
Application Signature: OPIM
Application Bitness: x64
Application Version: 16.43.0.20110804
Crashed Module Name: OutlookCore
Crashed Module Version: 16.43.0.201108
Crashed Module Offset: 0x000000000014710a
Blame Module Name: OutlookCore
Blame Module Version: 16.43.0.201108
UnsymbolicatedChecksum: 8BC5BFFD2940F64C6085EBDA9FE093A3
Blame Module Offset: 0x000000000014710a
StackHash: 4f401b8c62430da7-dm_1_bk
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
Build Type: Release
Crashed thread Stack Pointer: 0x_00007000017516c0
Crashed thread: 2
Outlook | MacOS | Legacy Outlook for Mac | 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.
84 answers
Sort by: Newest
-
Anonymous
2021-06-03T19:03:00+00:00 -
Anonymous
2021-06-03T18:10:47+00:00 In exactly the same boat my friend.
Outlook was working perfectly under 10.13.6 and a backend MS update has screwed it over. We have 32 full users, only one suffering this so far.
MS FIX IT for 10.13.6 users, I cannot up the OS and shouldn't need to.
Outlook 16.47 requires 10.14 or higher. Here's a thing..... I log into the other account (our company admin account) and Outlook boots. So what is going on in the user folder. Fed up with this utter rubbish. The ONLY thing that works flawlessly all the time is the rental monthly payments that go into your bank account Microsoft. FIX IT for 10.13.6!!
-
Anonymous
2021-06-03T16:40:55+00:00 Tried that and it worked for about 15 minutes. Then I got a message saying that Outlook needed to restart. After restarting, it continually crashes, just like before.
Microsoft Error Reporting log version: 2.0
Error Signature:
Exception: EXC_BAD_ACCESS
ExceptionEnumString: 1
Exception Code: KERN_INVALID_ADDRESS (0x0000000000000000)
Date/Time: 2021-06-03 16:40:25 +0000
Application Name: Microsoft Outlook
Application Bundle ID: com.microsoft.Outlook
Application Signature: OPIM
Application Bitness: x64
Application Version: 16.43.0.20110804
Crashed Module Name: OutlookCore
Crashed Module Version: 16.43.0.201108
Crashed Module Offset: 0x000000000014710a
Blame Module Name: OutlookCore
Blame Module Version: 16.43.0.201108
UnsymbolicatedChecksum: 8BC5BFFD2940F64C6085EBDA9FE093A3
Blame Module Offset: 0x000000000014710a
StackHash: 4f401b8c62430da7-dm_1_bk
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
Build Type: Release
Crashed thread Stack Pointer: 0x_000070000acbe6c0
Crashed thread: 17 -
Anonymous
2021-06-03T15:42:11+00:00 So until I buy a new Mac I can no longer use the Outlook client (that I paid for)? That was working perfectly on 10.13.6 until MS changed something?
-
Anonymous
2021-06-03T15:12:08+00:00 I am in a similar situation running 10.13.6 and therefore saying "use the web version of outlook" is not a fully viable solution.