Start with this diagnostic checklist
Before changing anything, note:
- Which program reports the error: Office Setup, Outlook, Word, another application, or a game.
- When it appears: during installation, repair, update, application startup, or Windows startup.
- The complete path in the message: especially whether it mentions
Office10,Office11,Office12, orCommon FilesSystemMapi. - Your Office architecture: 32-bit Office can be installed on 64-bit Windows, and it needs matching Office files.
- Whether antivirus recently quarantined anything.
exchcsp.dll is a genuine legacy Microsoft cryptographic-provider DLL associated with Outlook and Microsoft Office. It is not a normal Windows system file that you should download and copy into System32.
The safest repair is to fix the Office installation that owns the file. Microsoft describes the underlying component as the Microsoft Exchange Cryptographic Provider, associated with the Mail API. Historical Microsoft updates place EXCHCSP.DLL in Outlook 2002 and Outlook 2003 packages, while Microsoft has also documented Office 2007 Setup failing with an Office12EXCHCSP.DLL path.
As an Amazon Associate I earn from qualifying purchases.
Read the path before repairing anything
The path usually identifies the damaged installation better than the filename does.
| Error path | What it usually indicates |
|---|---|
Office10 |
Office or Outlook 2002-era files |
Office11 |
Office or Outlook 2003-era files |
Office12 |
Office 2007-era files |
Common FilesSystemMapi |
Older Outlook or shared MAPI components |
| An unrelated game or application folder | A program that copied or expects the component, possibly through an old Office dependency |
A message such as:
C:Program Files (x86)Microsoft OfficeOffice12EXCHCSP.DLL
points to the Office installation, not to Windows itself. Microsoft has recorded this path with Office Setup Error 2318.
#1 Best Overall
- The Microsoft Office 365 Bible: The Most Updated and Complete Guide to Excel, Word, PowerPoint, Outlook, OneNote, OneDrive, Teams, Access, and Publisher from Beginners to Advanced
- ABIS BOOK
If the message says “the specified module could not be found” even though exchcsp.dll is visible, a dependency may be missing. Repairing the parent Office installation is still safer than downloading individual dependencies.
Fix 1: Repair Office from Windows Settings
Use this first for Microsoft 365 and other supported Office installations.
- Close Office applications.
- Press Windows + I to open Settings.
- Select Apps.
- Select Installed apps.
- Find Microsoft Office, Microsoft 365, or the Office entry named in the error.
- Select the three-dot menu beside it.
- Choose Modify.
- If offered, select Online Repair.
- Select Repair and follow the prompts.
- Restart Windows when the repair finishes.
Online Repair replaces damaged Office files and rebuilds the installation configuration. It is more thorough than a quick local repair, so it may take longer and require an internet connection.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →For an MSI-based installation, the dialog may show Repair instead of Online Repair:
- Open Settings > Apps > Installed apps.
- Select the Office entry.
- Choose Modify.
- Select Repair.
- Complete the wizard and restart Windows.
How to tell whether it worked
Start the application that produced the error. If the message appeared during setup, run the Office installer again. The error is resolved when Setup no longer stops at EXCHCSP.DLL and Outlook or Office opens without the missing-file message.
If there are several Office entries, repair the one whose installation path matches the error. Repairing a different generation may leave the broken source untouched.
Microsoft’s current Office repair instructions explain the supported repair choices.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix 2: Repair older Office from Control Panel
Office 2003 and Office 2007 may not appear in the same repair workflow as current Microsoft 365 installations.
- Press Windows + R.
- Type
appwiz.cpl. - Press Enter.
- Select Microsoft Office in Programs and Features.
- Select Change.
- Choose Repair or Detect and Repair, depending on the Office release.
- Follow the prompts.
- Restart Windows.
Older MSI installations may ask for the original installation disc, network source, or product key. Use the same Office generation that created the path in the error. Do not point an Office 2007 repair at files from Office 2003 or a newer release.
Office 2007 is unsupported. Microsoft says installation requires the original disc and product key, so a repair may not be possible if that media is gone. In that situation, use a supported Office release if the old application is no longer required, or locate the legitimate original media before attempting a reinstall. Microsoft’s Office 2007 installation guidance covers those limitations.
Fix 3: Reinstall the Office version that owns the file
Repair cannot always restore a missing installer source. This is common after an interrupted upgrade, an incomplete uninstall, or a trial edition conflicting with a retail Office installation.
First remove the conflicting entry:
- Open Settings > Apps > Installed apps.
- Search for Office.
- Remove an unused trial, older Office generation, or duplicate installation.
- Restart Windows.
- Open Control Panel > Programs and Features as a second check.
- Remove any remaining conflicting Office entry.
- Restart again.
- Install the intended Office version from its legitimate Microsoft media or installer.
- Run Office Setup as an administrator if the installer requires elevated permission.
Do not delete the Office directory manually before uninstalling the product. The installer database may still refer to that directory and then fail while looking for EXCHCSP.DLL.
If Setup asks for a source location, use the original disc, mounted installation image, or authorized network location. A random DLL file is not an installation source because it does not restore registry entries, dependencies, installer records, or the rest of the Office component.
Fix 4: Check antivirus quarantine
Security software can remove or quarantine an old DLL if it considers the file suspicious or detects tampering.
- Open Windows Security.
- Select Virus & threat protection.
- Select Protection history.
- Look for an event involving
exchcsp.dllor the Office directory. - Check the reported file path and detection details.
- Do not restore the file merely because its name matches the error.
- Restore it only when the path belongs to the verified Office installation and the file is part of legitimate installation media.
- Repair Office afterward so the installer can supply the correct component.
Do not disable antivirus protection to obtain a DLL from the internet. If the file was replaced or appeared in an unrelated application directory, run a full scan and compare the installation path with the Office product you actually use.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Fix 5: Check 32-bit and 64-bit Office compatibility
A 64-bit Windows installation does not mean every installed application is 64-bit. Many legacy Office releases are 32-bit and use paths such as:
C:Program Files (x86)Microsoft Office
The required file must match the Office installation’s architecture and release. Do not replace a 32-bit Office component with a similarly named file from a 64-bit installation, and do not mix Office 2003, Office 2007, and Microsoft 365 files.
To check the architecture of a working Office application:
- Open Word or another Office program.
- Select File > Account.
- Select About Word, About Outlook, or the equivalent product option.
- Read the architecture shown in the dialog.
If Office will not open, inspect the installation entry in Settings > Apps > Installed apps and use the path from the error as the primary clue. The exact location varies by Office generation, language, installation method, and architecture.
Recommended Free Tools
Fix 6: Check for mixed Office versions and failed upgrades
A failed upgrade can leave an old installer record pointing at a file that was removed by a newer installation. A trial edition can also conflict with a retail or volume installation.
Look for:
- Two Office generations listed in Installed apps
- A trial edition left behind after installing another Office release
- Office folders from an older release that remain after an uninstall
- Setup errors that began immediately after an upgrade
- Outlook installed separately from the Office suite
Remove the unused or conflicting Office product through Windows, restart, and repair the intended installation. If the old application is required, reinstall that exact release from its original media instead of copying files from another computer.
Fix 7: Use DISM and SFC only for broader Windows corruption
exchcsp.dll is normally an Office-private component, so System File Checker is not the primary way to restore it. Use Windows integrity tools when you also see damaged Windows features, failed system updates, installer errors across multiple programs, or other protected system-file problems.
Open an elevated terminal:
- Right-click Start.
- Select Terminal (Admin) or Windows PowerShell (Admin).
- Select Yes at the User Account Control prompt.
- Run:
DISM.exe /Online /Cleanup-image /Restorehealth
- Wait for it to finish.
- Then run:
sfc /scannow
- Restart Windows.
Microsoft recommends running DISM before SFC. These commands can repair the Windows component store and protected Windows files, but they may not restore a DLL stored privately inside an Office directory. If the error remains, return to Office Repair or reinstall the owning Office product.
Repeatedly running SFC and DISM without checking what changed usually wastes time. If you prefer a guided scan that identifies broader repair issues while you work through these manual checks, Outbyte PC Repair can show what it detects; its full version performs the repair, but reinstalling the owning Office program remains the definitive fix for an Office-private DLL.
Do not use regsvr32 as a generic fix
regsvr32 registers certain COM and ActiveX DLLs that export a DllRegisterServer function. It is not a general-purpose missing-file repair command.
There is no verified reason to manually register EXCHCSP.DLL. Running:
regsvr32 exchcsp.dll
may produce an error stating that DllRegisterServer was not found. Even if registration succeeded, it would not restore a missing Office source, correct a wrong architecture, or replace a damaged installation.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsUse the Office installer instead. Microsoft’s regsvr32 documentation explains when the command applies.
Drivers are rarely the cause
A graphics, chipset, or storage driver does not normally provide exchcsp.dll. Do not start by updating every driver unless Device Manager shows a separate hardware problem or Windows itself is unstable.
If you do have a related hardware issue:
- Right-click Start.
- Select Device Manager.
- Expand the relevant category.
- Right-click the device.
- Select Update driver.
- Choose Search automatically for drivers.
- Restart if Windows installs an update.
Outbyte Driver Updater can reduce the manual work of hunting through device entries and checking which drivers are stale; its free scan identifies issues and the full version handles driver installation, but driver updates will not replace a missing Office component.
Why random DLL downloads are the wrong fix
Downloading exchcsp.dll from an unverified DLL website can introduce:
- Malware or a tampered binary
- The wrong Office release
- The wrong 32-bit or 64-bit architecture
- Missing dependencies
- A file with no trustworthy installation context
- A replacement that breaks the next Office repair
Copying it into C:WindowsSystem32, C:WindowsSysWOW64, or an application folder can also create a second problem while leaving the original Office installer damaged.
Use Microsoft Office repair, the original Office media, or a legitimate Microsoft installation package. Historical Microsoft bulletins confirm that the file shipped with older Outlook update packages, but they are not instructions to extract a DLL manually.
When System Restore is worth trying
Use System Restore only when the error began after a known installation, update, or cleanup and no current Office repair source is available.
- Press Windows + R.
- Type
rstrui.exe. - Press Enter.
- Select a restore point from before the change.
- Review the affected programs.
- Complete the restore and restart Windows.
System Restore is not guaranteed to restore an Office component and may remove applications installed after the selected restore point. Treat it as a fallback, not the first repair.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteFAQ
Is exchcsp.dll part of Windows?
It is a legacy Microsoft Office and Outlook component, not a normal Windows 10 or Windows 11 system file. Current Microsoft 365 installations may not contain it.
Is it part of Microsoft Exchange Server?
The name refers to the Microsoft Exchange Cryptographic Provider, associated with Outlook and the Mail API. A missing file in an Office directory points to the local Office installation, not automatically to Exchange Server.
Which Office versions used it?
Historical Microsoft security bulletins list it in Outlook 2002 and Outlook 2003 update packages. Microsoft has also documented an Office 2007 Setup failure involving Office12EXCHCSP.DLL.
Can SFC restore the file?
Usually not. SFC repairs protected Windows files. It can help with broader Windows corruption that prevents installation, but Office Repair or the original Office installer is the correct source for this component.
Free tools Windows power users keep installed
One-click scans. No signup required.
What if the file exists but still will not load?
The file may have a missing dependency, wrong architecture, wrong version, damaged signature, or an invalid installer reference. Repair the Office installation rather than registering or replacing the DLL manually.
What is the final fix if every repair fails?
Remove conflicting Office versions, restart, and reinstall the intended release from legitimate media. If the problem began after a known system change, try System Restore. For unsupported legacy Office, migrate to a supported Office release when the original media and product key are unavailable.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
