msorun.dll Is Missing: Find the Right Office Repair Path

“The program can’t start because msorun.dll is missing from your computer.” “The code execution cannot proceed because msorun.dll was not found.”

You may also see “There was a problem starting msorun.dll,” “Error loading msorun.dll,” “The specified module could not be found,” or “msorun.dll is either not designed to run on Windows or it contains an error.”

As an Amazon Associate I earn from qualifying purchases.

The 60-second answer

msorun.dll is a Microsoft Office Runtime library, not a normal Windows system file. It is associated with Microsoft Office 2003 and historical 2007 Microsoft Office system installations, and is commonly found under:

C:Program Files (x86)Common Filesmicrosoft sharedMSORUNMSORUN.DLL

The safest fix is to identify the program displaying the error and repair or reinstall that program from its original Office installer, recovery media, or legitimate vendor package. Do not download a loose copy of msorun.dll and place it in System32.

The file is commonly associated with 32-bit Office-era software. A 32-bit application requires the matching 32-bit Office component even when it runs on 64-bit Windows.

What is msorun.dll?

msorun.dll has the embedded description Microsoft Office Runtime and is published by Microsoft Corporation. Public Microsoft file inventories associate it with Microsoft Office installations rather than with the protected Windows operating system.

A commonly reported 32-bit record is version 11.0.5510.0, approximately 368 KB, from the Office 2003 era. Historical Office 2007 file lists also contain a different version, so that build should not be treated as the only valid copy.

Microsoft Office 2003 and Office 2007 are legacy products. Office 2003 support ended on April 9, 2014, and current Microsoft 365 Access Runtime packages are not guaranteed drop-in replacements for an older msorun.dll installation.

The exact product that installed the file cannot be determined from the filename alone. It may have been installed with:

• Microsoft Office 2003
• A historical 2007 Microsoft Office system component
• An old Access-based application
• An Office add-in or document converter
• A vendor program that bundled or redistributed an Office component

The first practical task is therefore to find the executable that is failing.

What caused the error?

Likely cause	What it means	Best response
Damaged Office or application installation	The file or a related component was removed or corrupted	Repair, then reinstall the affected program
Partial uninstall	A program was removed while another application still expects the shared runtime	Reinstall the calling application or complete Office package
Wrong architecture	A 32-bit program is being matched with an incompatible component	Use the architecture required by the original application
Antivirus quarantine	Security software removed or isolated the file	Review Protection history and verify provenance
Missing dependency	The named DLL exists, but another library it needs does not	Repair the original installation and inspect application logs
Failed update or system change	A restore, cleanup, or update left the installation incomplete	Repair first, then consider System Restore
Windows corruption	A broader servicing problem affects Windows components	Run DISM followed by SFC

The message “The specified module could not be found” does not always mean msorun.dll itself is absent. Windows can show that wording when a dependency required by the DLL is missing.

First, identify the affected application

Before replacing anything, determine which program is calling the file.

Check the error dialog

Look for the executable name in the title bar or the expanded error text. Record the application name and whether the error appears:

• When launching a particular Office program
• When opening an old Access database
• When starting a vendor application
• During login or startup
• After uninstalling Office
• After antivirus cleanup
• After restoring an old disk image or application

If the message names a program, repair that program rather than Windows.

Check shortcuts and installed applications

1. Right-click the shortcut that produces the error.
2. Select Properties.
3. On the Shortcut tab, read the Target field.
4. Note the executable path.
5. Open Settings → Apps → Installed apps.
6. Search for the application or publisher.
7. Open its menu and look for Modify, Repair, or Uninstall.

For an old application, also inspect its installation folder. Do not delete or replace files yet. The folder path often reveals whether the caller is Office, an Access database tool, an add-in, or a separate vendor application.

Determine whether it is 32-bit or 64-bit

A 32-bit program normally needs a 32-bit Office runtime. Installing a 64-bit replacement is not a safe substitute.

To inspect a running program:

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Select Details.
3. Right-click a column heading.
4. Choose Select columns.
5. Enable Platform, if available.
6. Check whether the executable is listed as 32-bit or 64-bit.

On some Windows versions, a 32-bit process is marked with *32. If the program will not start, check its documentation, installer name, or vendor support information instead.

Fix 1: Repair the application that displays the error

This is the most likely successful repair.

Repair a current Office installation

For Microsoft 365 or a supported modern Office installation:

1. Save your work and close all Office programs.
2. Open Settings.
3. Select Apps → Installed apps.
4. Find Microsoft 365 or Microsoft Office.
5. Select the three-dot menu beside it.
6. Choose Modify.
7. Select Quick Repair and choose Repair.
8. Restart Windows.
9. Test the application that reported msorun.dll.

If Quick Repair does not help, repeat the process and choose Online Repair. Online Repair uses a more complete replacement process and may require an internet connection.

For an MSI-based installation, choose Repair when Windows presents that option.

Repair Office 2003 or another legacy Office package

The labels vary by Windows version and installation type, but the historical process is generally:

1. Open Control Panel.
2. Select Programs and Features or Add or Remove Programs.
3. Select Microsoft Office 2003 or the relevant Office package.
4. Choose Change.
5. Select Repair or Reinstall.
6. Provide the original installation media or source if requested.
7. Restart Windows.
8. Test the affected program.

If Office 2003 is no longer listed, use the original installer or recovery media to reinstall it. Do not assume that repairing modern Microsoft 365 will restore a legacy Office 2003 component.

Repair the separate program

If the error appears in a non-Office application:

1. Open Settings → Apps → Installed apps.
2. Locate the named program.
3. Select its three-dot menu.
4. Choose Modify or Repair, if available.
5. Restart Windows.
6. Launch the program again.

If no repair option exists, uninstall the program, restart Windows, and reinstall it from the original installer or the software vendor’s legitimate recovery source. A packaged application may include the precise Office runtime version it requires.

How to tell whether this worked

The repair succeeded if the original program opens without the msorun.dll message and its normal features work. If the same message returns, the repair source may not contain the required legacy component, the wrong architecture may have been installed, or the message may identify a missing dependency rather than the named file.

Fix 2: Check antivirus quarantine

Security software can quarantine a legitimate old DLL, particularly when an old application behaves unusually. Do not restore a file solely because its name matches.

Review Windows Security

1. Open Start and search for Windows Security.
2. Select Virus & threat protection.
3. Under Current threats, choose Protection history.
4. Review recent quarantined or blocked items.
5. Expand an entry related to the affected application or msorun.dll.
6. Record the detected path and action.
7. Confirm that the file came from the original Office or application installation source.
8. If the provenance is clear and the detection is known to be incorrect, use the available restore or allow action.
9. Reinstall or repair the application afterward if Windows Security does not offer a safe restore.

Microsoft warns that allowing a real threat can expose the device. If the file came from an unknown download, do not whitelist it. Obtain a clean copy through the original installer instead.

Run a full Microsoft Defender scan if the DLL disappeared unexpectedly. An offline scan may be appropriate when you suspect malware or when security software repeatedly removes replacement files.

Fix 3: Reinstall from the original source

If repair cannot restore the component, reinstall the application that originally used it.

Use, in order of preference:

1. The original Office installation media
2. A company deployment share or recovery image
3. The program’s built-in recovery package
4. The original vendor installer obtained through its legitimate support channel

An Office 2003 service pack is an Office update, not a standalone msorun.dll installer. Installing a service pack by itself should not be treated as a guaranteed repair.

Microsoft’s current Access Runtime is also not automatically interchangeable with the legacy runtime required by an Office 2003 or Office 2007-era application. It has separate x86 and x64 packages and its own compatibility requirements.

After reinstalling:

1. Restart Windows.
2. Launch the program directly from its installed shortcut.
3. Open the file or database that previously failed.
4. Confirm that the application can load its normal components.
5. Apply only updates that are compatible with that legacy application.

If several Office generations are installed side by side, record which program needs the runtime before changing another Office installation. Removing or repairing the wrong generation can create additional shared-component problems.

Fix 4: Repair Windows components with DISM and SFC

msorun.dll is generally an Office file, not a Windows-protected operating-system file. Windows File Protection tools may therefore report no problem or fail to restore it. Still, run these commands when other Windows files are also damaged, Windows Update is failing, or multiple applications show system-component errors.

Run DISM first

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Approve the User Account Control prompt.
6. Run:

DISM.exe /Online /Cleanup-image /Restorehealth

1. Wait for the operation to finish.
2. Restart Windows if DISM reports that a restart is required.

Run System File Checker

Open an elevated Command Prompt again and run:

sfc /scannow

Wait until verification reaches 100 percent. Then restart Windows and test the affected application.

If SFC reports that it repaired files, test the program. If it reports that it found no integrity violations, the problem is probably in the Office or application installation rather than Windows. If it cannot repair some files, run DISM again, restart, and repeat SFC once. Continued failure requires examining the original application installation and Windows servicing logs rather than repeatedly copying DLLs.

Manually hunting through Windows components and repeating DISM/SFC without knowing what changed can be time-consuming. Outbyte PC Repair provides a free scan that shows what it identifies, while repair is handled by the full version; it is optional, and reinstalling the application remains the definitive fix for an Office-specific component.

Fix 5: Update or reinstall related drivers only when evidence points there

A display, printer, storage, or security driver is not the normal cause of a missing Office runtime. Consider driver work only if the application also crashes with device-related errors, Device Manager reports a problem, or the failure began immediately after a driver change.

Check Device Manager

1. Right-click Start.
2. Select Device Manager.
3. Expand the category related to the affected hardware.
4. Look for a warning icon.
5. Right-click the device and select Properties.
6. Read the status on the General tab.
7. On the Driver tab, note the provider and version.
8. Use Update Driver only with a driver from Windows Update or the hardware manufacturer.
9. Restart Windows and test the application.

To reinstall a problematic device:

1. In Device Manager, right-click the device.
2. Select Uninstall device.
3. Confirm only if you have the correct replacement driver or Windows can reinstall it.
4. Restart Windows.
5. Install the verified driver package.
6. Test the original program.

Driver hunting can involve comparing hardware IDs and checking several architectures. Outbyte Driver Updater provides a free scan showing the drivers it identifies, while installation is handled by the full version; it is optional and is not a substitute for repairing the Office application that owns the missing component.

Fix 6: Use the program’s file verification or recovery feature

Some launchers and packaged applications provide Verify files, Repair, or Scan and repair.

Use that function before manually replacing a DLL:

1. Open the application launcher.
2. Select the affected program.
3. Open its settings or properties.
4. Choose Verify files, Repair, or Scan and repair.
5. Allow the process to complete.
6. Restart the launcher.
7. Test the application.

This method can restore the exact files, manifests, and dependencies expected by that program. It is safer than copying a DLL from another machine.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Do not run regsvr32 as a routine fix

regsvr32 is used for DLLs that expose registration functions such as DllRegisterServer. There is no verified evidence that msorun.dll is a self-registering COM server.

Do not treat this as a normal repair:

regsvr32 msorun.dll

It may return:

The module was loaded but the entry-point DllRegisterServer was not found.

That result does not repair the Office installation and can distract from a missing dependency, incomplete reinstall, or architecture mismatch. Use the original installer’s repair process instead.

Do not download msorun.dll from random websites

Downloading a loose DLL is risky because the file may:

• Contain malware
• Have the wrong Office version
• Be built for the wrong architecture
• Be modified or unsigned
• Require dependencies that are also missing
• Hide a damaged installer or incomplete application repair

Do not copy it into C:WindowsSystem32, C:WindowsSysWOW64, or an application folder unless you are carrying out a controlled recovery from a verified original installer and understand that program’s deployment layout. Copying a file does not recreate Office registration, manifests, installer records, dependencies, or shared-component paths.

The safe sources are the original Office media, a trusted organizational deployment source, the application’s legitimate recovery installer, or Microsoft’s supported Office repair process.

Fix 7: Try System Restore after a recent system change

Use System Restore only when the failure began after a known update, uninstall, cleanup operation, or configuration change and an appropriate restore point exists.

1. Press Win + R.
2. Type:

rstrui.exe

1. Press Enter.
2. Choose Next.
3. Select a restore point from before the error began.
4. Choose Scan for affected programs.
5. Review the changes.
6. Select Next → Finish.
7. Allow Windows to restart.
8. Test the affected application.

System Restore can revert applications, settings, updates, and other changes made after the selected restore point. It does not replace a proper reinstall and should not be used when you cannot account for the changes it will undo.

If the error remains after reinstalling

Work through this checklist:

1. Confirm the exact executable named by the error.
2. Confirm whether the program is 32-bit or 64-bit.
3. Check that the installed Office component matches that architecture.
4. Verify that the file path belongs to the original installation.
5. Review Windows Security Protection history.
6. Check whether a dependency, rather than msorun.dll, is missing.
7. Inspect Event Viewer → Windows Logs → Application for an error at the same time.
8. Test the program from a new Windows user profile.
9. Check whether multiple Office generations are installed.
10. Use the application’s repair or file-verification function.
11. Reinstall the exact legacy application, not merely a modern Access Runtime.
12. Run a full or offline Microsoft Defender scan if the file keeps disappearing.

A new user profile can distinguish per-user Office configuration damage from a machine-wide installation problem. If the program works there, repair the original profile’s application settings rather than replacing system DLLs.

Frequently asked questions

Is msorun.dll a Windows system file?

No. It is a Microsoft Office Runtime component associated with legacy Office software. Its common path is under the shared Office folders in Program Files (x86), not the normal Windows system directories.

Does msorun.dll belong only to Office 2003?

No. Public records associate it with Office 2003 and historical 2007 Microsoft Office system files. The filename alone does not identify the exact originating product or valid version.

Will SFC restore msorun.dll?

Usually not. SFC repairs protected Windows system files, while msorun.dll is generally an Office component. Run DISM and SFC when broader Windows corruption is suspected, but repair the Office or application installation first.

Can I install Microsoft 365 Access Runtime instead?

Not as a guaranteed replacement. Modern Access Runtime has different packages and compatibility requirements. Use the runtime or Office version required by the application displaying the error.

Should I register msorun.dll?

No, not routinely. There is no verified basis for treating it as a self-registering COM DLL, and regsvr32 will not repair an incomplete Office installation.

Why does Windows say “The specified module could not be found” when the file exists?

The named file may depend on another missing or incompatible library. The message can therefore indicate a dependency problem, not just a missing msorun.dll.

What is the safest fix?

Repair or reinstall the exact application that displays the error using its original installer or a legitimate recovery source. Avoid standalone DLL downloads and do not place the file in System32.

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.