Excel Crashing: Faulting module name: mso20win32client.dll

Anonymous
2018-12-12T16:08:20+00:00

Hello,

I have constant crashes for Excel. It all started suddenly and it happens on two different computers (one a PC the other a laptop).

I have tried quick repair, online repair, uninstalling completely using the diagcab tool. Nothing works. The crash appears when doing simple tasks such as editing a chart, scrolling or selecting a cell. It happens in various files. I have also disabled all add-ins and it still happens. Below the error:

Faulting application name: EXCEL.EXE, version: 16.0.11029.20108, time stamp: 0x5c0b39a9

Faulting module name: mso20win32client.dll, version: 0.0.0.0, time stamp: 0x5c099da4

Exception code: 0x012a168b

Fault offset: 0x00000000001ea7b3

Faulting process id: 0x5a98

Faulting application start time: 0x01d492335c963195

Faulting application path: C:\Program Files\Microsoft Office\Root\Office16\EXCEL.EXE

Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll

Report Id: 0ce00505-d17d-4703-9ad3-62452c74****

Faulting package full name:

Faulting package-relative application ID:

Thank you!

[private message is removed by forum moderator]

Microsoft 365 and Office | Excel | For home | Windows

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
2018-12-25T01:50:42+00:00

Hi All,

Thanks for all the provided information, your time and efforts during these days. We'd like to share a summary for the issue here which will benefit other community members.

Symptoms:

Office 365 for Windows apps crash frequently when we do any simple actions such as editing, scrolling or selecting a cell. The crash log in the Event Viewer shows faulting module name: mso20win32client.dll.

Workaround:

Run as administrator when you launch the apps.

Assessment:

This issue is caused by Sticky Password, the 3^rd^ party conflict. Please place Excel in ''ignoring programs' within Sticky Password settings. You can get further help from Lamantine Software to see whether they will update a fix.

Regards,

Rena

[Updated by Rena Yu MSFT, 02:20 Jan 7, 2019(UTC)]

Was this answer helpful?

20+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2019-01-06T13:37:57+00:00

Update

I received a reply to my post about this Excel crash in the Excel/Windows 10/Office 2016 forum (same thread title as this one). The poster suggested that Sticky Password (SP) may be causing a conflict that crashes Excel. I made the necessary settings change to SP - making an entry for Excel.exe in the 'Ignored Apps' section. After testing this change, removing it and then reapplying it, I can confirm that Excel no longer crashes for me when running Excel as normal (i.e. not as Administrator). However, on this forum I doubt many of you will be running SP, but it may indicate another 3rd party program may be involved. I had been running SP for quite some time and it had never caused an issue with Excel, or any other program I run, so I'm not sure what started these crashes towards the beginning of December. I'm raising this issue with Lamantine Software, producers of SP, hoping they may be able to see why a conflict appears to exist.

Was this answer helpful?

20+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2019-01-07T10:43:56+00:00

Further update

As promised, I have had a response from Lamantine Software who publish Sticky Password. I have posted their reply here and it includes the steps previously outlined to resolve the immediate issue with the Excel crashes.

Quote:

We are sorry for this problem, our developers are already working on it. Possibly some other apps may cause similar conflicts but we recently found a conflict with our app. To resolve it immediately, please do the following:

1) Please navigate to the main Sticky Password window - Menu - Settings - Ignored apps and try to add the executive file of Excel to the list.

2) If it won´t help directly, on the same tab in the main Sticky Password window - Menu - Settings - Ignored apps, try to disable autofill for the 32bit or the 64bit apps accordingly to the version of the problematic app.

Thank you for understanding.

End quote.

Hopefully it won't be long before a permanent fix is supplied.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

83 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-12-21T13:28:48+00:00

    Hi All,

    Thanks for all the information and logs. Please follow Bjarne Nelson's suggestion to run as administrator as a current workaround. We will post back when we get any new updates.

    We appreciate all your effort and time.

    Regards,

    Rena

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-12-21T12:44:55+00:00

    In my case I just got something added yesterday, so OS level is now at 1809 (17763.195) and started getting impacted about the same time as Bruce.

    Issues still persist with Excel and I'm also impacted with Outlook...

    Faulting application name: OUTLOOK.EXE, version: 16.0.11029.20108, time stamp: 0x5c0b3947

    Faulting module name: mso20win32client.dll, version: 0.0.0.0, time stamp: 0x5be4e5fb

    Exception code: 0x0152139a

    Fault offset: 0x00199948

    Faulting process id: 0x4154

    Faulting application start time: 0x01d499211c48c00c

    Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE

    Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office16\mso20win32client.dll

    Report Id: ed5b697b-c2***251b6c97b39

    Faulting package full name: 

    Faulting package-relative application ID: 

    *PII has been removed by MSFT

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments