msmdun80.dll Not Found: Fix the Legacy Analysis Services Client

msmdun80.dll is an obsolete Microsoft SQL Server 2000 Analysis Services and PivotTable Service client component. It is not a normal Windows system DLL, so downloading a replacement and placing it in System32 is usually the wrong repair.

The safest solution is to identify the program requesting msmdun80.dll, then repair or reinstall that program’s Microsoft Analysis Services or PivotTable Service feature.

As an Amazon Associate I earn from qualifying purchases.

What msmdun80.dll does

Microsoft’s archived Analysis Services documentation lists Msmdun80.dll as part of the PivotTable Service file set. That component was used by older applications to read OLAP and relational data-mining models.

It was installed with a group of related files, including:

• Msolap80.dll
• Msolui80.dll
• Msmdcb80.dll
• Msmdgd80.dll
• Msdmine.dll
• Msmdun80.dll
• Msdmeng.dll

The documented location is normally:

C:Program FilesCommon FilesSystemOLE DB

The exact path can vary with the installer, Windows architecture, and application. The file does not belong to modern Windows itself.

Older software that may request it includes:

• SQL Server 2000 Analysis Services clients
• PivotTable Service installations
• Office or Excel-era OLAP features
• Reporting and business-intelligence programs
• Custom applications built against Microsoft’s older OLAP client components

Common reported messages include:

MSMDUN80.DLL is missing
The program can't start because MSMDUN80.DLL is missing from your computer.
MSMDUN80.DLL cannot be located
MSMDUN80.DLL file cannot be loaded
MSMDUN80.DLL file could not be loaded
MSMDUN80.DLL is corrupted

The wording depends on Windows and the application. A “bad image” or “not designed to run on Windows” message generally means the file is wrong, damaged, incompatible, or missing a dependency. It does not prove that the file is malware.

Before fixing it, identify the program that needs the file

Do not begin by copying a DLL. First determine which application is failing.

Check when the error appears

Note whether the message appears when you:

• Start a particular accounting or reporting program
• Open an old Excel workbook
• Launch a database client
• Use an older Office feature
• Start a scheduled task or background utility
• Log in to Windows

If only one program triggers the error, that program is the repair target.

Check the shortcut

1. Right-click the shortcut that produces the error.
2. Select Properties.
3. Open the Shortcut tab.
4. Read the Target field.
5. Note the program folder and whether it is under Program Files or Program Files (x86).

A program under Program Files (x86) is commonly 32-bit. That matters because a 32-bit application may need the 32-bit PivotTable Service files even when Windows itself is 64-bit.

Check installed applications

On Windows 11:

1. Open Settings.
2. Select Apps.
3. Select Installed apps.
4. Search for the program named in the error.
5. Select the three-dot menu beside it.
6. Choose Advanced options, if available.
7. Use Repair or Reset only if the application provides those choices.

On Windows 10:

1. Open Settings.
2. Select Apps.
3. Select Apps & features.
4. Select the affected program.
5. Choose Advanced options or Modify, depending on what is available.
6. Select Repair when offered.

Older desktop applications often do not provide a modern Repair button. In that case, use the application’s original installer or Control Panel.

Fix 1: Repair the application that reports the error

Time needed: 5 to 20 minutes.

This is the best first fix when one program produces the message. The missing file may be only one part of an incomplete installation, and replacing it alone can leave the rest of the component set mismatched.

Try the Windows repair entry

1. Press Windows + R.
2. Type:

appwiz.cpl

1. Press Enter.
2. Select the affected application.
3. Look for Change, Modify, Repair, or Reinstall.
4. Choose Repair if available.
5. Restart Windows.
6. Open the program again.

If the error returns, repeat the process and choose Modify. Look for database connectivity, OLAP, reporting, Analysis Services, or PivotTable features and install them.

Use the original application installer

If the program has no repair option:

1. Locate its original installation media or setup package.
2. Run the installer as an administrator.
3. Choose Repair or Modify.
4. Install the database, analysis, reporting, or client feature that the program originally used.
5. Restart Windows.
6. Test the affected program.

Do not mix a DLL from one SQL Server generation with files from another. These components work as an installation set.

Fix 2: Reinstall PivotTable Service from SQL Server 2000 media

Time needed: 15 to 30 minutes, not including locating the media.

Microsoft documented two historical PivotTable Service installers:

• PtsLite.exe installs PivotTable Service only.
• PtsFull.exe installs PivotTable Service plus Microsoft Data Access Components, also known as MDAC.

On SQL Server 2000 media, these files were supplied under:

MsolapInstallPts

If you have the original, legitimate SQL Server 2000 media:

1. Insert the disc or mount the approved installation image.
2. Open the MsolapInstallPts folder.
3. Choose PtsLite.exe if the application needs only PivotTable Service.
4. Choose PtsFull.exe if the application also requires the bundled data-access components.
5. Right-click the installer.
6. Select Run as administrator.
7. Complete the installation.
8. Restart Windows.
9. Test the application again.

The installers are historical SQL Server 2000 media components, not confirmed current standalone downloads. If you do not have the original media, do not obtain msmdun80.dll from an unverified DLL archive. Repairing or reinstalling the parent application is safer.

Microsoft’s archived documentation describes the component and its file set, while its archived technical guidance explains the PtsLite.exe and PtsFull.exe installers.

Fix 3: Check antivirus quarantine and file integrity

Time needed: 10 to 20 minutes.

Security software or cleanup utilities can remove files from an old installation. Do not immediately disable protection or restore a quarantined file.

Check Windows Security

1. Open Start.
2. Type Windows Security.
3. Open it.
4. Select Virus & threat protection.
5. Select Protection history.
6. Look for an event involving the affected application or msmdun80.dll.
7. Expand the event and review the file path and detection details.

Restore the file only when all of the following are true:

• It came from the original application installation.
• The path matches the application or PivotTable Service installation.
• The file is identified as Microsoft-signed or otherwise verified.
• You have confirmed the detection is a false positive.

Afterward, repair the parent application rather than relying on the restored file alone. Run a full security scan.

Check the file’s location and signature

If a copy of the file remains:

1. Right-click it.
2. Select Properties.
3. Open the Digital Signatures tab, if present.
4. Select the signature and choose Details.
5. Confirm that Windows reports a valid signature and a Microsoft publisher.
6. Open the General tab and record the full path.

A file with the right name in a temporary folder, a download folder, or an unrelated application directory should not be trusted merely because its filename matches.

Fix 4: Confirm 32-bit and 64-bit compatibility

Time needed: 10 to 25 minutes.

msmdun80.dll belongs to an old client component. A 32-bit application can require 32-bit Analysis Services files on 64-bit Windows.

Use these clues:

• C:Program Files (x86) usually contains 32-bit applications.
• C:Program Files usually contains 64-bit applications, although older installers do not always follow modern conventions.
• The application’s own documentation or executable properties may identify its architecture.

Install the architecture required by the calling application. Do not copy a 64-bit DLL into a 32-bit application folder, or the reverse.

Also keep related PivotTable Service files from the same installation set. Replacing only msmdun80.dll can produce a new error involving Msolap80.dll, Msolui80.dll, or another dependency.

Fix 5: Register the file only as part of a known-good installation

Time needed: 5 to 15 minutes.

Registration can apply to this file, but it should not be your first repair. Microsoft’s archived PivotTable Service documentation lists Msmdun80.dll among the components registered by Regsvr32.exe.

Reinstalling the component is safer because the installer registers the file and restores its dependencies together.

If you have already repaired the complete component and need to test registration, use the full path. On 64-bit Windows, a 32-bit application generally requires the 32-bit registration tool:

1. Open Start.
2. Type Command Prompt.
3. Right-click it.
4. Select Run as administrator.
5. Run:

%SystemRoot%SysWOW64regsvr32.exe "C:Program FilesCommon FilesSystemOLE DBmsmdun80.dll"

Adjust the path if the verified file is installed elsewhere.

A successful registration message means the registration request completed. It does not prove that the application has every required dependency.

If you see:

• The module could not be found: the file or one of its dependencies is missing.
• The entry point was not found: the wrong binary or registration tool may have been used, or that build may not expose the expected registration entry point.
• Access denied: reopen Command Prompt as administrator.
• The file is not compatible: the architecture is wrong or the file is damaged.

Stop trying random regsvr32 commands if registration fails. Reinstall the complete PivotTable Service or parent application instead.

Fix 6: Repair Windows components only when Windows files are also failing

Time needed: 15 to 45 minutes.

SFC and DISM repair Windows component storage and protected Windows files. They generally do not restore a missing third-party SQL Server 2000 Analysis Services DLL.

Use them when you are also seeing Windows file errors, broken system utilities, update failures, or several unrelated applications failing.

1. Save your work.
2. Open Start.
3. Type Command Prompt.
4. Right-click Command Prompt.
5. Select Run as administrator.
6. Run DISM first:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for it to finish.
2. Run System File Checker:

sfc /scannow

1. Restart Windows.
2. Test the affected application.

If SFC says it repaired files, test Windows and the application again. If it reports that it could not repair some files, repeat the process only after DISM completes successfully and review the result. Do not expect these commands to provide a missing SQL Server 2000 client file.

If manually hunting through Windows components and repeating SFC/DISM is taking more time than you can spare, Outbyte PC Repair can scan for system problems and show what needs attention; its free scan identifies issues, while repair is handled by the full version. It is optional, and reinstalling the affected legacy application remains the definitive fix when that application owns the missing file.

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

Fix 7: Update related software and drivers only when the failure involves them

Time needed: 15 to 30 minutes.

A device driver does not normally install msmdun80.dll, and Device Manager will not restore this SQL Server component. However, if the error began after updating a database-connected device, reporting workstation, scanner, or vendor application, check that vendor’s software and driver package as part of the wider repair.

To inspect drivers:

1. Right-click Start.
2. Select Device Manager.
3. Expand the category related to the affected equipment.
4. Right-click the device.
5. Select Properties.
6. Open the Driver tab.
7. Review the provider, date, and version.
8. Select Update Driver.
9. Choose Search automatically for drivers.
10. Restart Windows if a driver is installed.

For a recent driver change:

1. Open the device’s Properties.
2. Select the Driver tab.
3. Choose Roll Back Driver, if available.
4. Restart and test the application.

Prefer the hardware or application manufacturer’s official driver package. Do not use Device Manager as a substitute for reinstalling PivotTable Service.

If checking every device manually is the difficult part, Outbyte Driver Updater can scan for outdated drivers and identify what needs attention; its free scan shows the findings, while installation is handled by the full version. It is optional and will not replace the correct SQL Server or Analysis Services installer.

Fix 8: Use System Restore only after a clearly dated change

Time needed: 20 to 45 minutes.

System Restore can help when the error began immediately after software removal, an update, or a configuration change. It does not guarantee recovery of an obsolete third-party component.

1. Press Windows + R.
2. Type:

rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point created before the error began.
4. Select Scan for affected programs if available.
5. Review the changes.
6. Select Next, then Finish.
7. Let Windows restart.

If the application still reports the error, repair or reinstall the application directly.

What not to do

Do not download the DLL from a random website

A matching filename can still have:

• The wrong architecture
• The wrong build
• Missing exports
• Missing dependencies
• A damaged signature
• Malicious content

It may also place a vulnerable or incompatible binary into a location where several applications can load it.

Use the original application installer, legitimate SQL Server 2000 media, or a supported replacement application. Microsoft’s current documentation does not provide a supported modern standalone download for msmdun80.dll.

Do not copy it into System32 by default

System32 is not a universal storage location for every DLL. Windows and applications use defined DLL search behavior, and arbitrary copies can cause version conflicts or DLL-preloading risks.

Keep the file in the directory selected by its installer, normally the application’s OLE DB common-files location.

Do not install unrelated runtimes

Visual C++ Redistributable, DirectX, and .NET are not established direct fixes for this old Analysis Services component. Install them only when the application’s own documentation identifies them as requirements.

Do not enable random Windows Features

Windows optional features do not provide a current replacement for SQL Server 2000 PivotTable Service. You can inspect them through:

1. Open Settings.
2. Select System.
3. Select Optional features.
4. Review the installed list.

Do not enable an unrelated feature simply because its name contains “database,” “media,” or “legacy.”

Why the error happens

The most likely causes are:

Cause	Appropriate response
Incomplete application installation	Repair or reinstall the parent application
Old Office, Excel, reporting, or OLAP feature removed	Restore that feature through its installer
PivotTable Service removed	Use the original SQL Server 2000 media
Antivirus quarantine	Verify the file, scan the system, then repair the installation
Mixed 32-bit and 64-bit files	Install the architecture required by the calling application
Damaged related files	Reinstall the complete component set
Windows corruption elsewhere	Run DISM followed by SFC
Obsolete software incompatibility	Replace or upgrade the dependent application

SQL Server 2000 is obsolete. Even if you restore the file successfully, the dependent application may remain incompatible with current Windows versions. A supported upgrade or replacement is the long-term repair when the software is no longer maintained.

FAQ

Is msmdun80.dll a Windows system file?

No. It is an old Microsoft Analysis Services and PivotTable Service client component associated with SQL Server 2000-era software.

Is msmdun80.dll safe?

A genuine copy installed by Microsoft software can be legitimate. Verify its path, publisher, signature, and relationship to the affected application. A file downloaded from an unknown source cannot be trusted just because the name matches.

Where should msmdun80.dll be installed?

Microsoft’s archived documentation lists:

C:Program FilesCommon FilesSystemOLE DB

The actual location depends on the installer and application. Do not assume that C:WindowsSystem32 is correct.

Should I run regsvr32 msmdun80.dll?

Not as a first step. The archived component documentation does list this file for registration, but the original installer should normally perform it. If you test registration, use the correct architecture-specific tool and the full verified path.

Will SFC fix this error?

Usually not. SFC and DISM repair Windows components, while msmdun80.dll belongs to an obsolete SQL Server client component. Use them when other Windows files are also damaged.

What if I no longer have the installer?

Look for the original application media, a vendor-provided installer, or a legitimate SQL Server 2000 installation source. Microsoft does not currently provide a confirmed supported standalone download for this DLL. If the software is business-critical, plan a migration rather than building a permanent repair around an unsupported component.

Why does the program still fail after I copied the DLL?

The application may require other PivotTable Service files, the wrong architecture may have been copied, registration may be incomplete, or a dependency may also be missing. Remove the arbitrary copy if appropriate and repair the complete application or component installation.

Should I replace the old application?

If it depends on SQL Server 2000 Analysis Services and cannot be repaired from legitimate media, replacement or upgrade is often safer than keeping an unsupported runtime alive.

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.