Microsoft 2016 for Mac Products Crash When Opening

Anonymous
2019-03-11T19:33:38+00:00

Hi there, my Outlook, Excel, and PowerPoint applications crash right after I open them. I can't even access the File/Help/etc menu because the Microsoft Error Reporting prompt opens immediately, and prevents the application's menu bar from opening. 

I'm using Mac Mojave v 10.14.3 - the most updated version - and as many have suggested, I went into Microsoft 'Check for Updates' through my Word application (the one that will open), and found I'm using the most updated version. 

I've also restarted my Mac and opened in safe mode with no difference.

Here are the crash logs below.

What should I do from here?

Thanks so much!

________

Microsoft Error Reporting log version: 2.0

Error Signature:

Exception: EXC_BAD_ACCESS

ExceptionEnumString: 1

Exception Code: KERN_INVALID_ADDRESS (0x0000000000000000)

Date/Time: 2019-03-11 19:09:23 +0000

Application Name: Microsoft Excel

Application Bundle ID: com.microsoft.Excel

Application Signature: XCEL

Application Bitness: x64

Application Version: 16.16.7.19021001

Crashed Module Name: mso99

Crashed Module Version: 16.16.7.190210

Crashed Module Offset: 0x0000000000021ab6

Blame Module Name: mso99

Blame Module Version: 16.16.7.190210

UnsymbolicatedChecksum: FA4DBFDEDB1ECCDA29EC2FD8B06D1F9D

Blame Module Offset: 0x0000000000021ab6

StackHash: 728583b1ff983970-SB_1_bk

Application LCID: 1033

Extra app info: Reg=en Loc=0x0409

Build Type: SHIP

Crashed thread Stack Pointer: 0x_00007000092caaa0

Audience: Insiders

AudienceGroup: Insiders

AudienceChannel: CC

Crashed thread: 14

Microsoft Error Reporting log version: 2.0

Error Signature:

Exception: EXC_BAD_ACCESS

ExceptionEnumString: 1

Exception Code: KERN_INVALID_ADDRESS (0x0000000000000000)

Date/Time: 2019-03-11 19:09:43 +0000

Application Name: Microsoft Outlook

Application Bundle ID: com.microsoft.Outlook

Application Signature: OPIM

Application Bitness: x64

Application Version: 16.16.7.19021001

Crashed Module Name: mso99

Crashed Module Version: 16.16.7.190210

Crashed Module Offset: 0x0000000000021ab6

Blame Module Name: mso99

Blame Module Version: 16.16.7.190210

UnsymbolicatedChecksum: FA4DBFDEDB1ECCDA29EC2FD8B06D1F9D

Blame Module Offset: 0x0000000000021ab6

StackHash: 728583b1ff983970-SB_1_bk

Application LCID: 1033

Extra app info: Reg=en Loc=0x0409

Build Type: SHIP

Crashed thread Stack Pointer: 0x_0000700000b58aa0

Audience: Insiders

AudienceGroup: Insiders

AudienceChannel: CC

Crashed thread: 6

Microsoft 365 and Office | Excel | For home | MacOS

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
Jim G 134K Reputation points MVP
2019-03-13T02:18:31+00:00

Hi Michael,

As you probably already know, the 16.16.8 update is now available and this problem has been fixed.

If you have AutoUpdate set to automatically install updates, it is likely this update was automatically installed.

If you have AutoUpdate set to manual updates, you can launch AutoUpdate from any Office application and choose Check for Updates from the Help menu. If none of your applications will open, you can download the update to AutoUpdate manually from this link, then install and run AutoUpdate, which will install the 16.16.8 fixed update to Microsoft Office 2016.

https://go.microsoft.com/fwlink/p/?linkid=830196

I highly recommend that anyone affected launch AutoUpdate by going to the Help menu in any Office 2016 application and choosing Check for Updates. Remove your installation from Insider programs by unchecking the box that has you join the program. There will never be any future Insider builds of Office for Office 2016. The feature set of Office 2016 is not going to change, and there will never be any future Insider builds.

Was this answer helpful?

20+ people found this answer helpful.
0 comments No comments

142 additional answers

Sort by: Newest
  1. Anonymous
    2019-03-12T13:04:10+00:00

    I encountered crashes on all Microsoft Office applications only this morning after using Word, PowerPoint and Outlook all day yesterday with no problems. I made no changes between then and now, other than having restarted my computers. Same problem exists on both my Mackbook Pro laptop and my iMac desktop, running High Sierra 10.13.6.

    I've checked the "Notify Me" below, but it's unclear as to how I'll receive notifications under the circumstances.

    Here is partial content of the log from my iMac:

    Microsoft Error Reporting log version: 2.0

    Error Signature:

    Exception: EXC_BAD_ACCESS

    ExceptionEnumString: 1

    Exception Code: KERN_INVALID_ADDRESS (0x0000000000000000)

    Date/Time: 2019-03-12 13:00:36 +0000

    Application Name: Microsoft PowerPoint

    Application Bundle ID: com.microsoft.Powerpoint

    Application Signature: PPT3

    Application Bitness: x64

    Application Version: 16.16.7.19021001

    Crashed Module Name: mso99

    Crashed Module Version: 16.16.7.190210

    Crashed Module Offset: 0x0000000000021ab6

    Blame Module Name: mso99

    Blame Module Version: 16.16.7.190210

    UnsymbolicatedChecksum: FA4DBFDEDB1ECCDA29EC2FD8B06D1F9D

    Blame Module Offset: 0x0000000000021ab6

    StackHash: 728583b1ff983970-SB_1_bk

    Application LCID: 1033

    Extra app info: Reg=en Loc=0x0409

    Build Type: SHIP

    Crashed thread Stack Pointer: 0x_00007000036ed9d0

    Audience: Insiders

    AudienceGroup: Insiders

    AudienceChannel: CC

    Crashed thread: 5

    .......

    Operating System Information

    Operating System: Mac OS X 10.13.6 (Build 17G5019)

    CPU: Intel x86, Logical CPU Count: 4, Frequency: 3400 MHz

    Physical Memory: 8192 MB

    Device_model: iMac14,2

    Screen: 2048.000000 x 1152.000000, bitsPerPixel = 24, frame = 0.000000, 0.000000, 2048.000000, 1152.000000

    Microsoft Application Information:

    ErrorReportingDeviceUUID: A4F467E5-9781-51B5-BF9F-F46BA92B15DF

    ErrorReportingUUID: B16F06E0-BA98-4F05-84BD-591CF7768308

    ULS UUID: 681923A6-1554-4E12-8E91-5FF92F298678

    CrashedLogSessionId: 681923A6-1554-4E12-8E91-5FF92F298678

    TimeFromLaunch: 0 hours, 0 minutes, 0 seconds

    CrashedSessionDuration: 0

    Total errors on this client: 38

    CrashedApp_Virtual_Memory_Size_MB: 4968.492

    CrashedApp_Resident_Memory_Size_MB: 99.85937

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-03-12T13:03:57+00:00

    This has saved my working day!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-03-12T12:59:27+00:00

    Hi,

    Has there been a fix on this? Excel and Outlook won't open for me and crash immediately or I get 'application not responding'

    Uninstalled all of Office, & reinstalled yet the same issue keeps happening.

    Other office applications, Word, Powerpoint work fine on my machine.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-03-12T12:50:46+00:00

    As another user found, the MicrosoftRegistrationDB.reg file seems to be the issue for me, although I didn't lock it to keep it from being updates.

    I have been able to get things working again by doing an uninstall (per https://support.office.com/en-us/article/uninstall-office-for-mac-eefa1199-5b58- 43af-8a3d-b73dc1a8cae3?ui=en-US&rs=en-US&ad=US) and reinstall and then doing updates, and deleting the MicrosoftRegistrationDB.reg file from the ~/Library/Group Containers/UBF8T346G9.Office directory.

    I had already done an uninstall/reinstall/reapply updates, but I had done the updates from the Insider Fast update channel. On the second try, I did only the regular updates. That still didn't fix it, but I noticed that the MicrosoftRegistrationDB.reg was being modified when an Office application starts, so I deleted just that file (rather than the whole directory), and now the Office apps are starting up normally every time.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments