How to fix mso20win32client.dll Bad Image error in Windows?

mso20win32client.dll is a shared Microsoft Office file, so the Bad Image window (Error status 0xc000012f) and the Outlook or Excel crashes that name it are Office problems, not Windows ones. Start with an Office repair: Quick Repair, then Online Repair. If the crashes began after an Office update, update again or go back one build.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What the mso20win32client.dll error means

mso20win32client.dll is a library that Word, Excel, Outlook, PowerPoint and the other Office apps load when they start. It sits in Office's shared folder, not in C:\Windows\System32, and it is installed and updated by Office itself. People search for it in two situations that look different but have the same owner.

Message 1: the Bad Image window (as the old version of this guide recorded it)

OUTLOOK.EXE - Bad Image
C:\Program Files (x86)\Common Files\Microsoft Shared\Office16\mso20win32client.dll is either not designed to run on Windows or it contains an error.
Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.
Error status 0xc000012f.

To read the crash version, press Win + R, type eventvwr.msc and open Windows Logs > Application. Look for an Error with source Application Error at the time the app closed. The lines Faulting application name and Faulting module path tell you which app crashed and where mso20win32client.dll lives, for example C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll.

What causes the mso20win32client.dll error, from most to least common

Most often the Office installation is damaged: an interrupted update, a disk error or a cleanup tool left mso20win32client.dll or a file next to it broken. Less often a new Office build crashes on your setup, or an Outlook profile is broken. Rarely Windows itself is damaged.

• Why SFC alone rarely helps. System File Checker repairs protected Windows files. mso20win32client.dll is an Office file, so only the Office repair or a reinstall replaces it.
• Why graphics drivers are not on the list. The old version of this page told readers to update drivers. Nothing ties this Office file to a driver, so that step is gone.
• Why not copy the file from another PC. Users on forums report copying mso20win32client.dll from a working machine. It must match your exact Office build, and the Office repair puts back the right one for you.

How to fix the mso20win32client.dll error in Windows

Fix 1 helps most readers with the Bad Image window. Fix 2 and Fix 3 are for crashes that began after an Office update. Fix 4 is for Outlook only. Fix 5 to Fix 8 are for the cases the first fixes do not solve.

Fix 1. Repair Microsoft 365 or Office with Quick Repair, then Online Repair

10 to 30 minutesLow riskYou see the Bad Image window naming mso20win32client.dll in Outlook, Word or Excel. This is the first fix for nearly everyone.

mso20win32client.dll is one of Office's own files. Microsoft's repair checks the Office installation and replaces damaged files, and Online Repair reinstalls Office's program files completely, so the DLL comes back in the version that matches your build.

1. Open Installed apps. Right-click the Start button and select Installed apps.
2. Find Microsoft 365 or Office. Find your Microsoft 365 or Office product in the list. If you have a standalone app such as Visio or Project, search for it by its own name.
3. Open the repair window. Select the three dots next to the product and select Modify.
4. Start with Quick Repair. In the repair window, select Quick Repair, then Repair. It is the faster option: it finds damaged files and replaces them.
5. Finish and test. Follow the instructions on the screen until the repair is done. Restart the PC if you are asked to, then open the app that had the problem.
6. Run Online Repair if the problem is still there. Open the same repair window again and select Online Repair, then Repair. Microsoft recommends this option to make sure everything gets fixed. It takes longer than Quick Repair.

These steps were written for Windows 11 25H2 and 26H2. The full page with the other versions and what each result means: How to repair Microsoft 365 or Office

Fix 2. Update Office to the newest build

5 to 15 minutesNo riskThe apps open but crash, Event Viewer names mso20win32client.dll, or Office has not updated for a while.

A crash inside mso20win32client.dll is often a bug of one Office build. Microsoft fixes such bugs in later builds, and an update also replaces the DLL and the files it works with as one matching set.

1. Open any Office app that still starts, for example Word, and open a blank document.
2. Select File > Account (in Outlook: File > Office Account).
3. Under Product Information, select Update Options > Update Now.
4. Wait until Office reports You're up to date!, then close all Office apps.
5. Open the app that crashed and use it as before.

Fix 3. Go back to the previous Office build if an update started the crashes

15 to 30 minutesRead the warningOffice updated itself and the crashes started right after it, on one PC or on many with the same build.

In January 2025 Microsoft 365 build 16.0.18324.20168 crashed Outlook and Excel on Windows Server 2016 terminal servers, with mso20win32client.dll as the faulting module. Microsoft confirmed it under MO978220, and administrators reported that returning to build 16.0.18227.20162 stopped the crashes.

1. In Word, open File > Account > About Word and note your current Version and Build.
2. Find the build released before yours on Microsoft's update history page for Microsoft 365 Apps, for your update channel.
3. Close all Office apps.
4. Type cmd in Windows search, right-click Command Prompt and select Run as administrator.
5. Run the Click-to-Run client with the previous build number. This is the command from the January 2025 case; replace the number with yours:

   "C:\Program Files\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe" /update user updatetoversion=16.0.18227.20162

6. Let the Office update window finish, then open the app that crashed.
7. To stop Office installing the faulty build again at once, select File > Account > Update Options > Disable Updates, and turn updates back on with Enable Updates within a few weeks.

Fix 4. Test Outlook in a new Windows user account

10 to 20 minutesLow riskOnly Outlook (classic) crashes, even in safe mode, and repairing or reinstalling Office changed nothing. One trigger users report is switching to the new Outlook and back.

A reader on Microsoft Q&A had this exact case on Windows 11. An independent advisor answered that it was tied to the Windows user profile, because Office files are shared by all users but each profile keeps its own Outlook settings and cache.

1. Open Other users. Open Settings > Accounts > Other users. You can also press Windows key + R and run the command below.

   ms-settings:otherusers

2. Add an account. Next to Add other user, select Add account.

   

3. Skip the Microsoft account. Select I don't have this person's sign-in information.

   

4. Choose a local account. Select Add a user without a Microsoft account.
5. Name the account. Type a user name and, if you want one, a password. If you set a password, Windows also asks for answers to security questions. Select Next.
6. Make it an administrator (optional). Back in Other users, select the new account, then Change account type next to Account options. Choose Administrator and select OK. For testing a problem, a standard account is usually enough.
7. Sign in to the new account. Open Start, select your account picture and choose the new account. The first sign-in takes a few minutes while Windows sets up the profile.

These steps were written for Windows 11 24H2, 25H2 and 26H2. The full page with the other versions and what each result means: Create a new user account to test a problem

1. Sign in to the new account and open Outlook (classic).
2. Add your mail account when Outlook asks for it.
3. If Outlook works here, the problem is in your own profile. Keep the new account, or move your files over to it.

The reader in that thread fixed it in his own account by deleting some Office cache folders from his profile and restarting. We could not confirm which folders those were, so we do not list them here.

Fix 5. Remove Office completely and install it again

30 to 60 minutesLow riskThe Online Repair failed or did not help, or Installed apps shows two Office entries.

Uninstalling removes the whole Office16 shared folder, mso20win32client.dll included, and a fresh install writes every file again. It also clears leftovers of an older or half-removed Office that a repair keeps.

1. Uninstall from the Start menu. Select Start > All apps and find the app. Right-click it (or press and hold) and select Uninstall.
2. Or uninstall in Settings. Select Start > Settings > Apps > Installed apps. Find the app, select More (the three dots) > Uninstall, and confirm.
3. Or uninstall from Control Panel. Some programs can only be removed here. Type Control Panel in the search box on the taskbar and open it, then select Programs > Programs and Features. Right-click the program and select Uninstall or Uninstall/Change, then follow the program's own uninstaller.
4. Restart if the uninstaller asks. Some programs finish removing their files only after a restart.

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Uninstall a program or app in Windows

1. Restart the PC after the uninstall.
2. Sign in at your Microsoft account's Services & subscriptions page, or the Office portal for work accounts, and install Office from there.
3. Open Outlook, Word and Excel once and check that no Bad Image window appears.

Fix 6. Repair Windows system files with DISM and SFC

20 to 30 minutesNo riskBad Image windows also name files in C:\Windows\System32, or Office will not reinstall.

SFC does not replace Office files, but Office depends on Windows libraries. If those are damaged, Office files can fail to load too, and DISM and SFC restore the Windows side.

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.

   

2. Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

   

3. Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.

   sfc /scannow

   

4. Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

   

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

Run DISM first, then SFC, then restart and run the Office repair from Fix 1 once more.

Fix 7. Remove the Windows update installed just before the error

10 to 20 minutesLow riskThe Bad Image window or the crashes started on the day a Windows update was installed.

Users of the old version of this guide reported that the error came with a Windows update. Removing that update undoes the change, so you can tell whether it caused the problem.

1. Open Windows Update. Select Start > Settings > Windows Update.
2. Open the update history. Under More options, select Update history. Note the KB number and the date of the update you suspect.
3. Open the list of removable updates. Scroll down to Related settings and select Uninstall updates.

   

4. Uninstall the update. Find the update in the list and select Uninstall next to it. If the update is not in the list, Windows does not allow it to be removed this way.

   

5. Pause updates. Go back to Settings > Windows Update and select Pick a date on the Pause updates control. If your PC shows a list there instead, select the pause length you prefer. Without a pause Windows downloads the same update again.

These steps were written for Windows 11 25H2 and 26H2. The full page with the other versions and what each result means: How to uninstall a Windows update

Fix 8. Undo recent changes with System Restore

20 to 40 minutesLow riskThe error started recently and a restore point from before exists.

System Restore puts back programs, drivers and system settings from a restore point, Office files included, so a change that damaged the installation is undone in one step.

1. Open System Restore. Press Windows+R, type the command below and press Enter. You can also open Control Panel > Recovery > Open System Restore. If a first page opens, select Next.

   rstrui.exe

2. Choose a restore point. Select a restore point from a time before the problem started. The Description often names the event, such as a driver or app install. If the one you need is missing, select Show more restore points (shown only when there are more).

   

3. See what will change. Select Scan for affected programs. The upper list shows programs and drivers that will be removed; the lower list shows those that might come back and may need to be reinstalled. Select Close.

   

4. Start the restore. Select Next, check the summary and select Finish. Windows restarts and applies the restore point. Do not turn the PC off.
5. Check the result. After sign-in Windows reports whether the restore succeeded. Check whether the problem is gone.

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Undo recent changes with System Restore

Your documents stay. Programs and updates installed after the restore point are removed, so check Scan for affected programs first.

If the mso20win32client.dll error is still there

Stop trying fixes at random and collect what Microsoft support or your IT needs. Three facts decide the next step: the exact message, the Office build and the event log entry.

1. Photograph the Bad Image window with the title, the full path and the Error status line.
2. Note the Office version and build from File > Account > About in any app that opens.
3. In Event Viewer, under Windows Logs > Application, copy the Application Error entry: faulting application, faulting module, exception code and module path.
4. Note which fixes you tried, for example "Online Repair done, reinstall done, crash only in my Windows account".
5. Send this to Microsoft support from the Office help page, or post it on Microsoft Q&A.

• Same result again. If the window comes back after a clean reinstall, the cause is outside Office: check Windows with Fix 6 and look for other Bad Image windows.
• When it is hardware. If files break again after each repair, check the disk with Check a disk for errors (chkdsk) and the memory with How to test your RAM with Windows Memory Diagnostic.

How to keep the mso20win32client.dll error from coming back

• Let Office updates finish. Do not shut the PC down while Office shows an update in progress.
• Keep one Office version. Remove old trials and older editions before installing a new one.
• Never replace Office files by hand. Use the Office repair instead of copied or downloaded DLLs.
• Keep restore points on. They make Fix 8 possible after a bad update.
• On managed PCs, test updates first. The January 2025 case shows why a test group before a wide rollout pays off.

If you still run Windows 10, plan the move to Windows 11: Windows 10 left support on 14 October 2025 and no longer gets regular fixes.

Frequently asked questions

What is mso20win32client.dll?

mso20win32client.dll is a shared Microsoft Office library. It lives in C:\Program Files\Common Files\Microsoft Shared\Office16 for 64-bit Office, or under Program Files (x86) for 32-bit Office. Word, Excel, Outlook and the other apps load it when they start. It is not a Windows system file and not malware. Office installs, updates and repairs it on its own, so you never need to download it.

Is it safe to download mso20win32client.dll from a DLL website?

No. The file must match your exact Office build, and a copy from a DLL site may be from another build, unsigned or infected. Even a correct file does not fix the files next to it that may also be damaged. Run the Office repair (Fix 1) instead: it replaces mso20win32client.dll with the copy that belongs to your installation, signed by Microsoft.

What does Error status 0xc000012f mean?

0xc000012f is the Windows status for a bad image. Windows found the file named in the window but refused to load it, because its content is damaged or not a valid program file for this system. The window title names the app that tried to load it, for example OUTLOOK.EXE. For mso20win32client.dll the cure is an Office repair, because the file belongs to Office.

Why does Outlook crash with mso20win32client.dll as the faulting module?

The crash happens inside the Office library, but the cause is often around it: a faulty Office build, a damaged Office installation or a broken Outlook profile. Update Office first (Fix 2). If the crashes started with an update, go back one build (Fix 3). If only Outlook crashes, even in safe mode, test it in a new Windows user account (Fix 4).

Excel crashes with mso20win32client.dll. Is the fix the same?

Yes. The file is shared by all Office apps, so an Excel crash that names mso20win32client.dll is handled like the Outlook one. Repair Office (Fix 1), then update it (Fix 2). If Excel crashes in every workbook from one day on, roll back to the previous build (Fix 3). If it crashes only in one file, the file or an add-in is the more likely cause.

Does running Office as administrator fix the error?

No. Running an app as administrator changes its permissions, not the files it loads. A damaged or mismatched mso20win32client.dll stays damaged, so the Bad Image window or the crash comes back. Readers who tried it and saw no change are on the right track: go straight to the Office repair in Fix 1, which replaces the file.

Will repairing or reinstalling Office delete my files or emails?

No. The Quick Repair, the Online Repair and an uninstall work on Office's program files, not on your documents. Outlook data files and mail on the server stay as they are. You may have to sign in to Office again after a reinstall, so keep the Microsoft account or product key at hand. A backup of your files before bigger changes is still a good habit: Back up your files (Windows Backup, File History, Time Machine).

Can a cracked or unofficial copy of Office cause this error?

It can. Activators and repackaged Office copies change or replace Office files, and a mismatched mso20win32client.dll is exactly what triggers a Bad Image window. We do not help with such copies and cannot say what they changed. Remove them, scan the PC with Microsoft Defender (How to scan for malware with Microsoft Defender) and install genuine Office from your Microsoft account.

Does SFC /scannow fix the mso20win32client.dll error?

Usually not on its own. SFC repairs protected Windows files, and mso20win32client.dll is an Office file, so SFC does not check it. The old version of this guide put SFC first; it is now Fix 6. Run it when Bad Image windows also name Windows files, or when Office refuses to reinstall, and then run the Office repair once more.