Outlook Crashes Shortly After Starting

Qian-

I'm beginning to feel like you're not listening. There are a lot of us out here who for various reasons are unable to update our Mac OS. For many of us it would require purchasing new hardware, which is not a trivial issue whether we're talking about one machine or multiples. Most of us have been resigned to not being able to get the latest features, but at least we had working systems. I have been able to get things running, but only by going back to Outlook 16.16.27. We were all doing fine until two weeks ago when Microsoft changed something in the (already older) versions which we were running and everything crashed. Microsoft is, of course, free to stop supporting older hardware, but you owe us some advance notice as to when this is going to happen. For now, you should fix the problems which are causing the crash, and let us know when you will stop supporting our hardware so that we can plan for upgrades.

Glen

I am experiencing this same issue at work as of 5/27/2021. Multiple people started reporting this issue a few days ago. Here are some facts I have gathered. Are there any solutions?

This is happening to users on Macintosh computers only, with these specs:

• Mac OS 10.13.6
• Outlook Version 16.43.20110804

Other facts:

• It is not happening to everyone with those computer specs, only some of our users
• Users with issues have various sizes of mailboxes, anywhere from 1GB to 40GB
• Users with issues have various size inboxes, from 200 items up to 40,000 items
• Users with issues are from various departments within the company, nothing really in common
• Word, Excel, Teams, etc, all appear to be running fine
• If we setup a new computer with OS 10.15.x and the latest/newest version of outlook, the issue does not reoccur
• If we setup the user on a PC with Outlook, the issue does not reoccur

Did you just say -

"Hope it works!"

Are you joking? PLEASE fix this. Of all our users I am now starting to calculate how much MONEY this is costing us and how much time I am spending trying to fix this seeing as I CANNOT update the OS on these machines.

Please let me know what Microsoft department I need to send, what will be, the huge bill to. Responsibility goes both ways. You take the money, Office 2016 is spec'd to work under 10.10.x and above. Please, please, fix this and don't say things like 'Hope it works!'. Have at least a little respect for your constantly paying customers.

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.

I've tested the same user account with OSX 10.15.7 and Outlook 16.42 and the same issue happens. (with 16.49.20101102 the error is solved) There is no really a clear explanation for what to look for in the logs.

So for me its obvious, that Microsoft did change something in Office365 which makes the latest Version of Outlook on OSX 10.13.6 crash and becoming useless now. MICROSOFT PLEASE UNDO THIS! Thanks.

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-27 17:55:44 +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_oom

Application LCID: 1031

Extra app info: Reg=en Loc=0x0407

Build Type: Release

Crashed thread Stack Pointer: 0x_00007000082646c0

Crashed thread: 11

Last ObjC Exception Reason (may or may not be related to crash): -[NSOpenGLPixelFormat initWithAttributes:] failed in CGLChoosePixelFormat due to error 10002 (invalid pixel format)

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-26 11:46:05 +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: 1031

Extra app info: Reg=en Loc=0x0407

Build Type: Release

Crashed thread Stack Pointer: 0x_000070000551c6c0

Crashed thread: 14