Outlook Crashes Shortly After Starting

Anonymous
2021-05-25T00:04:58+00:00

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.

0 comments No comments

84 answers

Sort by: Oldest
  1. Anonymous
    2021-06-06T18:34:19+00:00

    Jim I understand where you are going with this, firstly if you read the forum you'll see it wasn't a Mac OS update that broke Outlook. This was an update that Microsoft pushed to a client of mine, in good faith he allowed Microsoft to install an Office update that they were recommending for his system...which he has done for the past 9yrs of using various Macs. This time it cost him more than he afford to give, it's like Microsoft just shot him in the head.

    But like you say...he should have first put his bulletproof vest on that fateful morning before turning his MacBook on, it's all his fault.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-06-07T06:03:27+00:00

    In my opinion we were not expecting this kind of bugs/changes crashing the product. Microsoft states: "Product functionality and feature availability may vary on older systems" and "....quality of your Microsoft 365 experience may diminish over time." I did understand in the way, that we were not receiving any additional functionality and may not receive security updates. That's fine. But essentially behind this marketing sentense above, its says in reality: "We can do whatever we want. If you don't update to the newest version, be prepared to loose any service at any time and don't call support for help because we are not going to do anything about it".

    This would be more truthful and transparent towards us as paying customers.

    I have around 65 Macs which could have the same problem at any time.... not funny at all! Troubleshooting identifying the problematic calendar entry is a nightmare due to poor logging mechanism within Outlook. So I have to discover it by trial/error.

    I hope Microsoft decides to do one of the 3 possible things:

    • Release a 16.43 Version with the fix in order that Office doesn't crash anymore
    • Revert your changes on the Office365 plattform
    • provide a detailed description of the bug so we can train our employees not to use that specific feature in Office365 which creates the bug

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-06-07T10:17:22+00:00

    If I could update the OS on our Macs I wouldn't have this issue. I cannot.

    The Microsoft website for Office 2016.

    Operating system

    Mac OS X version 10.10 or later

    You have broken Office 2016 by doing something at your end. Your System requirements still state that 2016 will run under 10.10.x or above. Please issue an update for Outlook 2016 that will work under 10.13.x. Saying 'use the web portal until you can update' is insulting. Sorry, we haven't got 30k to drop on mew Macs because you've broken the functionality.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-06-07T10:22:44+00:00

    From Microsofts website for Office 2016:

    Operating system

    Mac OS X version 10.10 or later

    It won't actually let you perform an update of an app that isn't supported by the OS you're running. The update pushed out by Microsoft has broken the functionality and all the checking in the world would not have indicated that the update would cause quite catastrophic effects.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2021-06-08T09:48:29+00:00

    Hi everyone,

    This is very frustrating. I have reverted back to my Apple mail as using the web all day isn't great. I don't have the MS Teams integration I need and I was also using the tasks function of Outlook, so that I will have to visit on the web. This change from MS has changed my entire workflow and there seems to be no interest in a fix.

    MAC OS 10.13.6 - Can't upgrade any further, machine doesn't support it

    Outlook 16.43.0.201108 - I have also tried to uninstall and run older versions

    There is discussion about Calendar entries causing this?

    Has anyone made any contact to anyone else besides Qian, is he able to help us?

    Simply put, something happened to Outlook and it won't run, we can't upgrade Outlook or Mac OS any further due to the hardware. Everything was working, then Outlook just started blowing up.

    Thanks to everyone for their input here, the future doesn't look good with our existing hardware.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments