If msdaerr.dll is missing, Windows cannot start an application that expects Microsoft OLE DB components. The safest fix is normally to identify the application reporting the error and repair or reinstall that complete application, rather than downloading a replacement DLL.
What msdaerr.dll is
msdaerr.dll is a Microsoft OLE DB library with the internal description Microsoft OLE DB Error Collection Localized Strings. It provides error-object resources and localized text used by OLE DB, a Microsoft data-access technology that applications use to communicate with databases and other data sources.
As an Amazon Associate I earn from qualifying purchases.
It is associated with Microsoft Data Access Components, historically called MDAC, and with Windows Data Access Components, or WDAC, on newer Windows releases. Microsoft documents WDAC as part of the Windows data-access stack in its Windows Data Access Components overview.
This file is:
- A Microsoft OLE DB component
- Usually needed by an older application or database-connected program
- Not a Visual C++ Redistributable file
- Not a DirectX component
- Not a .NET assembly
- Not a graphics driver
- Not the modern SQL Server OLE DB driver itself
Historical Microsoft component documentation placed it here:
#1 Best Overall
%ProgramFiles%Common FilesSystemOle Db
That does not mean every valid installation will contain the file there today. It also should not automatically be copied into C:WindowsSystem32.
Quick identification
| Item | Verified information |
|---|---|
| File | msdaerr.dll |
| Description | Microsoft OLE DB Error Collection Localized Strings |
| Publisher | Microsoft Corporation |
| Component | Microsoft OLE DB |
| Typical role | OLE DB error-object resources and localized strings |
| Current standalone download | No current Microsoft Windows 10 or Windows 11 package intended for lone manual replacement |
| Correct version | Depends on the parent application and Windows generation |
Do not treat an old file listing as a universal answer. Historical third-party metadata reports builds such as 2.0.3002.4, while archived MDAC listings show other build values. Those reports do not establish the correct version for your computer.
Fix msdaerr.dll errors in the safest order
1. Identify the program that displays the error
Before repairing Windows, determine which executable is failing.
Free tools Windows power users keep installed
One-click scans. No signup required.
Look at the title bar and message text. It may name the application, for example:
LegacyApp.exe - System Error
or:
program.exe - Bad Image
Also note whether the error appears:
- Immediately after launching one old application
- After reinstalling a program
- After a program update
- After disk-cleanup software removed files
- After antivirus quarantine
- When several unrelated programs start
- When a database connection is opened rather than when the program starts
If only one old application reports the error, its installation is the leading suspect. If several unrelated applications fail, investigate Windows corruption, malware, or a system-wide change.
2. Repair or reinstall the affected application
This is the most likely solution on Windows 10 and Windows 11.
Try Windows app repair
- Press Windows + I to open Settings.
- Select Apps.
- Select Installed apps.
- Find the application that reports the error.
- Select the three-dot menu beside it.
- Choose Advanced options, if available.
- Select Repair.
- Start the application again.
The Repair option may preserve the program’s settings while restoring missing files. If the error remains, return to the same screen and use Reset only if you understand that it may remove application data or settings.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Use the traditional repair option
Some desktop applications do not expose repair controls in Settings.
- Press Windows + R.
- Type
appwiz.cpl. - Press Enter.
- Select the affected program.
- Choose Change, Repair, or Uninstall/Change.
- Follow the vendor installer’s repair steps.
- Restart Windows and test the program.
If no repair option exists, uninstall the program and reinstall it from its original media or the software vendor’s official download. Use the installer intended for the same Windows architecture and application release.
If the application came from a game or software launcher, open that launcher and use its Verify, Repair, or Scan files feature before replacing anything manually. Such a feature can restore the exact private files expected by that program.
How to tell whether this worked
The repair succeeded if:
- The application opens without the
msdaerr.dllmessage - Its database or data connection works normally
- No new “entry point not found” or “Bad Image” error appears
If the application now reports a different missing file, the installation may be incomplete or the program may depend on an older prerequisite package. Reinstall the complete application rather than replacing a series of individual DLLs.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →3. Check Microsoft Defender quarantine
An antivirus quarantine event can explain why a previously working program suddenly reports a missing DLL.
Rank #2
- Open Start.
- Type Windows Security.
- Open it.
- Select Virus & threat protection.
- Select Protection history.
- Review recent detections.
- Expand any entry associated with the affected application or
msdaerr.dll.
Restore the file only when all of the following are true:
- You recognize the application that installed it
- The application came from a trusted vendor or original media
- The detection is demonstrably a false positive
- The file’s origin and digital signature can be trusted
If the detection is unclear, do not restore the DLL. Reinstall the parent application from a trusted source and scan the system. Microsoft notes that restoring a malicious file can cause Defender to detect it again. Its guidance is available in Protection History in Windows Security.
4. Check whether the existing file is in the expected location
You can inspect common locations without copying or registering anything.
Open Windows Terminal or PowerShell, then run:
Get-ChildItem "$env:ProgramFilesCommon FilesSystemOle Dbmsdaerr.dll",
"$env:windirSystem32msdaerr.dll",
"$env:windirSysWOW64msdaerr.dll" -ErrorAction SilentlyContinue |
Select-Object FullName, Length, VersionInfo
This reports any matching files found in those locations.
The command does not prove that a file is safe, correct, or compatible. An unexpected copy in a temporary folder, a user profile, or an unrelated application directory deserves additional scanning and vendor verification.
5. Consider 32-bit and 64-bit compatibility
Older OLE DB documentation identifies msdaerr.dll as a 32-bit component, although MDAC and WDAC existed in both 32-bit and 64-bit Windows environments.
On 64-bit Windows:
C:WindowsSystem32is normally the 64-bit system directoryC:WindowsSysWOW64is normally the 32-bit system directory- A 32-bit application may use 32-bit dependencies even when Windows itself is 64-bit
Do not assume that putting a 32-bit DLL in System32 is a fix. Do not copy a file from another computer unless it is being restored by a documented vendor installer or a verified backup.
To determine whether the application is 32-bit or 64-bit, check the application vendor’s documentation or inspect the executable with a trusted administrative tool. More importantly, reinstall the application using the installer intended for its architecture.
An entry point not found message usually means the file exists but is the wrong version or does not match another dependency. A Bad Image message can indicate corruption, an incompatible binary, or a mixed set of application files. In both cases, reinstall the complete application or its documented OLE DB prerequisite.
6. Understand the MDAC and WDAC distinction
MDAC 2.8 was included with Windows XP SP2 and Windows Server 2003. Windows Vista and later include WDAC as an operating-system component. Microsoft states that WDAC is not separately redistributable for modern Windows.
That means the old standalone mdac_typ.exe installer should not be treated as a general repair for Windows 10 or Windows 11. It was primarily intended for older Windows releases, especially Windows 2000-era installations.
Recommended Free Tools
If an old program’s original installer includes an MDAC or OLE DB prerequisite, use that vendor-provided installer only when it is explicitly intended for your Windows version. Microsoft’s MDAC and WDAC version history explains the relationship between these components.
The Microsoft MDAC Component Checker can help diagnose legacy MDAC installations, but it is a diagnostic utility for older environments, not a modern replacement package. Microsoft provides it through its MDAC Component Checker download page.
7. Repair Windows component corruption with DISM and SFC
Use this step when:
- Windows reports missing or damaged system components
- Several unrelated applications fail
- The problem began after an interrupted update
- System files appear corrupted
- Application repair did not resolve a broader Windows problem
Open Windows Terminal as administrator:
- Open Start.
- Type
terminal. - Right-click Windows Terminal.
- Select Run as administrator.
- Approve the User Account Control prompt.
Run this command first:
DISM.exe /Online /Cleanup-Image /RestoreHealth
Wait for it to finish. Then run:
sfc /scannow
Run the commands separately, not on the same line. Restart Windows when both have completed.
DISM repairs the Windows component store. SFC checks protected Windows system files against that repaired component store. Microsoft documents these procedures in Repair a Windows image and System File Checker.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, 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 minuteIf DISM cannot find repair files, install pending Windows Updates and restart. If Windows Update is also damaged, DISM may require an installation image or another approved repair source.
If you prefer an assisted scan that shows what needs attention before you work through the commands manually, Outbyte PC Repair can identify reported Windows issues; its repair operation is performed by the full version. It is optional, and reinstalling the affected application remains the definitive fix when that program owns the missing dependency.
Check the result
Test the original application after restarting. If it still fails but unrelated Windows programs work normally, return to application repair rather than repeatedly running SFC and DISM.
8. Install Windows updates and use System Restore when appropriate
Install pending updates
- Press Windows + I.
- Select Windows Update.
- Select Check for updates.
- Install available updates.
- Restart when prompted.
- Test the affected application again.
Updates can repair Windows components, but they do not necessarily restore a private DLL that belonged to an old application.
Use System Restore after a recent system-wide change
System Restore is appropriate when the error began immediately after a driver, application, or Windows change and a restore point exists from before that event.
- Press Windows + R.
- Type
rstrui.exe. - Press Enter.
- Select Next.
- Choose a restore point dated before the problem began.
- Select Scan for affected programs if available.
- Review the changes.
- Select Next, then Finish.
System Restore can revert applications, settings, registry data, and monitored system files. It is not a substitute for reinstalling the affected application, and it does not restore personal documents.
9. Treat modern SQL Server driver files as a separate issue
Applications that connect to SQL Server may use Microsoft’s modern OLE DB Driver for SQL Server. That package uses files such as msoledbsql.dll, not msdaerr.dll. Installing or repairing the modern SQL Server driver will usually not replace an old application’s missing msdaerr.dll.
If the error specifically names a SQL Server driver, follow the application vendor’s database-driver requirements. Microsoft’s OLE DB Driver for SQL Server installation documentation covers that separate package.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
10. Update a driver only when the application identifies one
msdaerr.dll is not a hardware driver, so Device Manager is normally irrelevant. Use it only when the error also identifies a storage controller, database appliance, USB device, or other hardware-related driver.
To check:
- Right-click Start.
- Select Device Manager.
- Expand the relevant device category.
- Right-click the identified device.
- Select Properties.
- Open the Driver tab.
- Review the provider, date, and version.
- Use Update Driver only with a driver supplied by Windows Update or the hardware vendor.
Avoid changing unrelated drivers simply because the filename contains “DLL.”
When manually hunting through device vendors and matching driver versions is the difficult part, Outbyte Driver Updater can scan for reported driver issues; the full version performs the driver installation. It is optional, and updating a driver will not repair an application-specific OLE DB installation unless the error actually identifies a driver problem.
What not to do
Do not download a lone DLL
Random DLL download sites can provide:
- The wrong build
- The wrong architecture
- A file intended for a different Windows generation
- A modified or malicious binary
- A DLL that creates a second dependency error
Even a genuine-looking file may not fix the application because OLE DB components belong to a matched installation. The correct recovery source is the affected application’s official installer, original media, a trusted backup, Windows component repair, or an applicable Microsoft package intended for that Windows release.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteDo not copy a 32-bit file into System32
On 64-bit Windows, System32 is the 64-bit system directory. Copying files between System32, SysWOW64, and an application folder can make the loader select the wrong binary or hide the actual installation problem.
Do not run regsvr32 as a generic repair
regsvr32 is designed for DLLs or OCX files that expose a self-registration entry point such as DllRegisterServer. A resource and localized-string library normally does not need this registration.
Running:
regsvr32 msdaerr.dll
is therefore not a general repair and may produce an error that adds confusion. Microsoft’s self-registration guidance applies to controls that support registration, not every DLL.
Do not install Visual C++, DirectX, or .NET at random
Those packages solve different dependency problems. They are relevant only when the application’s error specifically identifies a Visual C++ runtime, DirectX component, or .NET assembly.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Do not use Windows Features to install OLE DB
Windows Features can enable certain Windows capabilities, but they are not a general installer for msdaerr.dll. Do not enable or disable unrelated features in the hope of restoring one application’s private dependency.
When to escalate
Contact the application vendor or your internal administrator when:
- The program is business-critical or connects to production data
- Its installer requires an old MDAC package
- You have only an unknown DLL copy and no original media
- Defender repeatedly quarantines the file
- The program fails after a complete reinstall
- Several applications fail even after DISM, SFC, updates, and a restart
- The error identifies an entry point rather than a missing file
For an old application, compatibility settings may help, but they cannot make an incompatible or incomplete OLE DB installation correct. Preserve the installer, configuration files, database connection details, and logs before uninstalling a production application.
Frequently asked questions
Is msdaerr.dll a Windows system file?
It is a Microsoft OLE DB component, but it should not automatically be treated as a current Windows 10 or Windows 11 system file. Historical documentation placed it under the OLE DB common-files directory, and an old application may install or expect it there.
Should I put msdaerr.dll in System32?
No. Do not copy it there unless a trusted, documented installer specifically does so. The correct location depends on the Windows architecture, application architecture, and component package.
Is msdaerr.dll part of SQL Server?
It belongs to Microsoft OLE DB and may be used by database-connected software. It is not the same thing as the modern Microsoft OLE DB Driver for SQL Server, whose package uses files such as msoledbsql.dll.
Will reinstalling Windows fix the error?
Usually that is excessive. Repair or reinstall the affected application first. Use DISM and SFC when there is evidence of Windows component corruption. Consider System Restore after a recent system-wide change.
Can I register msdaerr.dll with regsvr32?
Normally no. regsvr32 is for self-registering controls and DLLs that expose the required registration entry point. It is not a universal missing-DLL repair command.
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 →Why does only one old program show the error?
That usually indicates an incomplete application installation, an old bundled prerequisite, a quarantine event, or an architecture mismatch. Repair or reinstall that program before changing Windows globally.
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.
