Share this article
Improve this guide
Mso20win32client.dll is the Faulting Module: 7 Ways to Fix it
Running Microsoft Office as an administrator is the quickest fix
5 min. read
Updated onNovember 7, 2024
updated onNovember 7, 2024
Share this article
Improve this guide
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
For fixing DLL errors, we recommend Fortect:
Fortect will search for an intitial version of your missing, corrupted or damaged DLL files that cause problems to your Windows OS and will replace it. Here is how to find them in 3 easy steps:
Often, when you try to run a Microsoft Office app, sayOutlook, Excel, Word, PowerPoint, orOneNote, or perform an action within it, the app crashes. Upon launching theEvent Viewertocheck the crash logs, you findMso20win32client.dllas theFaulting module name.
TheFaulting module path, as listed in the crash log, is:C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll
But when heading to the location, there’s usually no DLL by the same name. If you are, too, facing this issue, first re-login into Microsoft Office and install any pending updates for both the OS and Microsoft Office. In most cases, this alone will fix the crash triggered byMso20win32client.dll!
What can I do when Mso20win32client.dll crashes Microsoft Office?
1. Run with administrative privileges
2. Delete the Office cache and credentials
3. Run Microsoft Office in Safe Mode
Running Microsoft Office apps inSafe Modewill temporarily get rid of theMso20win32client.dllerror. To do that, either holdCrtland then click on the app in theSearchmenu or use the/safeparameter.
Here’s how you can open different Office apps inSafe Modefrom theRun(Windows+R) command:
4. Uninstall conflicting programs
In the past, Office apps like Microsoft Excel crashed due toMso20win32client.dllwhenSticky Passwordwas installed. At the time, adding Excel to the list of exclusions inSticky Passworddid the trick. But it could be another app in your case. So, remove any that you suspect of triggering the crash!
If a quick removal doesn’t work, use atop-rated software uninstallerto delete the app cache, leftover files, and Registry entries, which may still cause conflicts post-uninstall.
5. Create the DisableSupportDiagnostics DWORD
6. Disable OneDrive
In several instances, OneDrive was the reason behind theMso20win32client.dllcrash. Here, you have two options: quit OneDrive or sign out of your account. I prefer the latter since it proved helpful in 4 out of 5 cases.
To sign out of OneDrive, select the app’s entry in the system tray, click on the gear icon, chooseSettings> navigate to theAccounttab > click onUnlink this PC> confirm the change.
7. Repair Microsoft Office
The built-in repair functions offered by Microsoft Office come in handy when fixing crashes due toMso20win32client.dllin Excel, Word, Outlook, or PowerPoint.
In case the issue persists, it’s best that youcontact Microsoft supportsince the problem, in all likelihood, lies at their end.
Before you leave, discover expert tips tomake Microsoft Office run fasterand get better performance!
For any queries or to share which fix worked for you, drop a comment below.
More about the topics:DLL errors,DLL issues,Microsoft Office
Kazim Ali Alvi
Windows Hardware Expert
Kazim has always been fond of technology, be it scrolling through the settings on his iPhone, Android device, or Windows PC. He’s specialized in hardware devices, always ready to remove a screw or two to find out the real cause of a problem.
Long-time Windows user, Kazim is ready to provide a solution for your every software & hardware error on Windows 11, Windows 10 and any previous iteration. He’s also one of our experts in Networking & Security.
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Kazim Ali Alvi
Windows Hardware Expert
Kazim is specialized in hardware devices, always ready to remove a screw or two to find out the real cause of a problem.
