Excel Crashing: Faulting module name: mso20win32client.dll

Anonymous

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]

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

Answer accepted by question author

Anonymous

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)]

0 comments

Answer accepted by question author

Anonymous

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.

0 comments

Answer accepted by question author

Anonymous

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.

0 comments

83 additional answers

Anonymous

2018-12-19T16:22:58+00:00

Hi All,

Thanks for reporting the issue here in this community forum.

Please first try the possible solutions below to see the result:

1.      Sometimes, such mso20win32client.dll module crash may be caused by "Block signing into Office" policy. Example thread and the detailed steps to check that. Please help us check this.

2.      In the meantime, refer to this thread, you can also try the steps to delete some registry keys to see whether this solution can work for you as well.

If the issue persists, we would like to collect the information below for further investigation:

1.      It seems all of you are using the 16.0.11029.20108. Does the issue happen to other users in your company? If so, are all the affected computers using this same version?

2.      When did the issue first happen? Was there anything changed before that?

3.      Your OS version.

4.      Does the issue only happen to Excel app?

5.      Please provide us the whole crash log for further investigation. To collect it, you can provide them in the private message I have sent you.

*This page contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view How to back up and restore the registry in Windows. Modifying Registry incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry can be solved. Modify Registry at your own risk.

Thanks,

Rena
Was this answer helpful?

0 comments No comments
Anonymous

2018-12-19T16:34:02+00:00

Hi JayDTee,

it's not just O365. I have Pro Plus installed on the laptop.

In my case it all started, when Microsoft pushed some Office updates down my throat. I was holding off taking the updates for as long as I could, given past bad experiences of such updates severely impacting indexing of Outlook files.
Was this answer helpful?

0 comments No comments