“The program can’t start because msdasc.dll is missing from your computer.”
Other messages may say that msdasc.dll was not found, could not be loaded, or is either not designed to run on Windows. These messages identify a Microsoft Data Access component, but they do not always prove that the named file itself is the part that is missing.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.97 | Buy on Amazon |
| 2 |
|
Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |... | $119.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
Which fix applies to you
Use the first description that matches your situation:
- Only one older program fails: Repair or reinstall that application first. Its private files, dependencies, or OLE DB provider may be damaged.
- Several programs fail, or Windows recently had problems: Install Windows updates, restart, then run DISM and SFC.
- The application is old and expects MDAC: Check whether it was designed for Windows 2000, XP, or Server 2003. Do not install an old MDAC package on Windows 10 or 11 unless the application vendor specifically documents a compatible method.
- The message says “specified module could not be found”: A dependency of
msdasc.dllmay be missing instead ofmsdasc.dllitself. - The application is 32-bit on 64-bit Windows: Check the bitness of its OLE DB provider or ODBC driver. A 32-bit application may require 32-bit database components.
- Security software recently quarantined a file: Review its quarantine history and verify the Microsoft signature before restoring anything.
- You downloaded a replacement DLL: Do not copy it into
System32,SysWOW64, or the application folder. Remove the download and use the repair paths below.
What msdasc.dll is
msdasc.dll is a genuine Microsoft component described as Microsoft Data Access – OLE DB Service Components Stub. It belongs to Microsoft Data Access Components, or MDAC, and the later Windows Data Access Components, or WDAC.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
MDAC and WDAC provide database-access technologies including OLE DB, ADO, and ODBC. OLE DB service components sit between an application and database providers, helping applications use data-access services consistently. Microsoft documents the history of MDAC and WDAC in its data-access technology history and describes the related OLE DB service providers and components.
This is not a Visual C++ runtime, DirectX file, .NET assembly, or device driver. Installing a Visual C++ Redistributable package is therefore not a supported repair for an msdasc.dll error.
On older systems, MDAC was integrated into Windows XP and Windows Server 2003. Starting with Windows Vista and Windows Server 2008, the technology was called WDAC and shipped as part of Windows. Modern Windows versions do not use a normal standalone “latest MDAC” installer for this repair.
The file name alone also does not prove that a copy is safe. Verify the file’s path, Microsoft digital signature, and security status before trusting it.
Fix 1: Repair the application that reports the error
When only one program displays the error, the program’s installation is the most useful place to start. The application may have lost its own copy of a dependency, an OLE DB provider, or configuration data during an uninstall, cleanup operation, update, or antivirus event.
Repair from Installed apps
- Close the affected application.
- Open Start > Settings.
- Select Apps > Installed apps.
- Find the program named in the error dialog.
- Select its three-dot menu.
- Choose Advanced options, if available.
- Select Repair.
- Start the application again.
Some desktop applications do not provide a Repair button in Settings. In that case:
- Press Windows key + R.
- Type
appwiz.cpl. - Press Enter.
- Select the affected program in Programs and Features.
- Choose Change, Repair, or a similarly named option.
- Complete the installer and restart Windows.
If the program has a launcher, look for Verify files, Verify integrity, or Repair installation in that launcher. This is preferable to replacing one DLL because it restores the application’s files as a matched set.
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 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchReinstall from the original publisher
If repair is unavailable or does not work:
- Back up the application’s settings and saved data if necessary.
- Uninstall the program from Settings > Apps > Installed apps.
- Restart Windows.
- Download the installer from the application’s original publisher or use the original installation media.
- Install the program again.
- Restart once more and test it.
Do not assume that reinstalling the application will install a modern MDAC runtime. For a current Windows program, the installer may instead restore an application-specific provider or configuration that the program needs.
If the application still fails after a clean reinstall, note its name, release era, and whether it is 32-bit or 64-bit. Those details determine whether the next step is Windows repair or a provider repair.
Fix 2: Install Windows updates and restart
WDAC components are part of Windows on supported modern releases. Pending servicing updates can leave protected components in an incomplete state, especially after an interrupted update or restart.
- Open Start > Settings.
- Select Windows Update.
- Choose Check for updates.
- Install all available updates.
- Restart when Windows requests it.
- Return to Windows Update and check again.
- Test the application.
If Windows Update itself reports an error, restart first and try again. If the application works after updating, no manual DLL replacement or registration is needed.
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 minuteFix 3: Repair Windows components with DISM and SFC
Use this step when several applications fail, when Windows recently experienced corruption, or when reinstalling the affected application did not help. Microsoft recommends running DISM before System File Checker because DISM repairs the component store that SFC may need as a source.
Run DISM
- Open Start.
- Type
Command Prompt. - Select Run as administrator.
- Approve the User Account Control prompt.
- Enter this command:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Press Enter.
- Wait for the operation to finish.
- Leave the window open even if progress appears to pause.
When DISM completes, restart Windows. Then open an elevated Command Prompt again and run:
sfc /scannow
Wait until verification reaches 100 percent, then restart and test the affected program.
Microsoft’s System File Checker guidance covers this procedure and the result messages.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Understand the result
- Windows Resource Protection did not find any integrity violations: Protected Windows files appear intact. Focus on the application, provider, or architecture.
- Windows Resource Protection found corrupt files and successfully repaired them: Restart and test the application.
- Windows Resource Protection found corrupt files but was unable to fix some of them: Run DISM again, restart, and repeat SFC. If it still cannot repair the files, inspect the CBS log and consider an offline repair or System Restore.
- DISM cannot complete: Record the exact error, install pending updates, restart, and run it again from an administrator account.
SFC can repair protected Windows components. It may not restore an application-private copy of msdasc.dll, and it will not install a missing third-party database provider.
If you want help identifying which Windows component repair changed without repeatedly running commands and interpreting logs, Outbyte PC Repair can scan for issues and show what needs attention; its repair actions are completed by the full version. Reinstalling the affected program remains the definitive fix when the damaged file belongs to that program.
Fix 4: Check the OLE DB provider and application architecture
The calling application may not need msdasc.dll alone. It may need a database provider such as an Access provider, SQL Server provider, Oracle provider, or an ODBC driver. If that provider is absent or has the wrong architecture, Windows can report that a module could not be found even when the named DLL is present.
Identify whether the program is 32-bit or 64-bit
The application’s documentation or publisher support page may state its architecture. You can also inspect the installation location:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
C:Program Filescommonly contains 64-bit applications.C:Program Files (x86)commonly contains 32-bit applications.
This is a useful clue, not a definitive test. Some installers use different layouts.
On 64-bit Windows, WOW64 redirects many 32-bit applications from the normal system view to the 32-bit system component view. Microsoft documents this behavior in its file-system redirector documentation. A 32-bit application may therefore require a 32-bit provider even though Windows itself is 64-bit.
Install the provider or driver version documented by the application publisher. Do not mix individual DLLs from different MDAC or OLE DB releases. These components were tested as matched sets.
Check the provider requirement
Look in the application’s documentation, setup notes, or error log for terms such as:
Recommended Free Tools
- Microsoft Access Database Engine
- Jet or ACE
- SQL Server OLE DB provider
- Oracle provider
- ODBC driver
- Data Source Name, or DSN
Install only the provider required by that application, from its original vendor or Microsoft documentation. An msdasc.dll message alone is not enough evidence to choose a provider.
If a provider installer fails, remove only the provider version the application no longer needs, restart Windows, and install the documented architecture. Avoid installing several unrelated database engines to guess at the problem.
Fix 5: Check antivirus quarantine and file integrity
Security software can quarantine a component after a false positive, or a damaged installation may cause the security product to flag an unusual file.
Rank #2
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
- Open Windows Security from the Start menu.
- Select Virus & threat protection.
- Choose Protection history.
- Look for an event involving the affected application or
msdasc.dll. - Do not restore the file merely because its name matches the error.
- Verify the original path and Microsoft digital signature first.
- Run a full security scan.
If another antivirus product is installed, use its quarantine and history screens instead. Do not disable antivirus protection to install a DLL downloaded from an unknown source.
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 →A legitimate Microsoft file is normally restored through Windows servicing or the application installer, not through a random archive.
Fix 6: Reinstall or update a related driver only when evidence points there
msdasc.dll is not a device driver, so Device Manager is not a direct repair tool for this file. It becomes relevant only if the failing application also depends on a database-connected device, storage controller, chipset component, or another driver that recently changed.
To check for driver problems:
- Right-click Start.
- Select Device Manager.
- Expand the category related to the hardware named in the application’s error or documentation.
- Look for a warning icon.
- Right-click the device and select Properties.
- Read the message under Device status.
- Select the Driver tab.
- Use Update Driver or Roll Back Driver only when the timing and device match the failure.
- Restart Windows and test the application.
Obtain drivers from Windows Update or the hardware manufacturer. Do not use Device Manager to replace msdasc.dll.
When several hardware drivers are outdated, Outbyte Driver Updater can scan and identify the versions that need attention, avoiding the need to hunt through many manufacturer pages; the full version performs the driver installation. A driver update is not a substitute for reinstalling an application that owns the failing file.
Fix 7: Use System Restore or another Windows repair path
Use System Restore when the error began after a software installation, cleanup utility, update, or configuration change and the earlier restore point is known to predate the problem.
- Press Windows key + R.
- Type
rstrui.exe. - Press Enter.
- Select Choose a different restore point, if offered.
- Pick a restore point from before the error began.
- Select Scan for affected programs.
- Review the applications and drivers that may be removed or restored.
- Select Next, then Finish.
- Let Windows restart and complete the operation.
System Restore does not replace personal documents, but it can remove applications or drivers installed after the selected point. If SFC continues to report unrepaired files, test the application under another Windows user profile and run a malware scan. Persistent corruption may require an in-place Windows repair using official installation media.
Legacy Windows and MDAC 2.8
Do not install MDAC 2.8 merely because a current Windows 10 or Windows 11 application reports msdasc.dll.
Microsoft states that MDAC 2.8 SP1 was a historical redistributable intended for specific older Windows environments, and that it should only be installed on Windows 2000. The old runtime used mdac_typ.exe. The separate mdac28sdk.msi package is an MDAC 2.8 SDK for developers, not a general end-user repair installer. Microsoft’s MDAC 2.8 distribution guidance explains this limitation, while the MDAC 2.8 SDK page identifies the SDK’s purpose.
For a legacy application running on an old supported installation, use the application vendor’s documented MDAC requirement. For Windows 10 and Windows 11, use Windows Update, DISM, SFC, and the application’s own installer instead.
Why regsvr32 msdasc.dll usually does not help
regsvr32 is not a universal DLL repair command. It registers DLLs that expose an appropriate registration entry point, such as DllRegisterServer. Microsoft documents its purpose and syntax in the regsvr32 command reference.
A missing file, a damaged component, a missing dependency, and a missing COM registration are different problems. Running:
regsvr32 msdasc.dll
is therefore not routine advice for this error. It can produce another error if the DLL is not designed for that registration method, and it does not restore a missing file or install a missing provider.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use regsvr32 only when the application vendor or Microsoft documentation specifically identifies a registration problem and gives the correct architecture-specific command.
Why manual DLL downloads are unsafe
Do not download msdasc.dll from a DLL index, file mirror, forum attachment, or another PC. A replacement may have:
- The wrong architecture
- An incompatible version
- Missing dependencies
- An invalid or absent Microsoft signature
- Malware
- A mismatch with the application’s provider set
Copying it into System32, SysWOW64, or the program directory can also make diagnosis harder by hiding the original installation problem.
The safe sources are Windows servicing, Microsoft’s built-in repair tools, and the original application or provider installer. The correct repair restores the complete matching component rather than replacing one file in isolation.
Prevention and final diagnostic checklist
Before escalating the problem, record:
- The exact application named in the error
- Whether every program fails or only one
- Whether Windows is 32-bit or 64-bit
- Whether the application is 32-bit or 64-bit
- What changed immediately before the failure
- Whether antivirus quarantine contains a related item
- The result of DISM and SFC
- Whether the application requires a specific OLE DB provider or ODBC driver
Do not delete system files, install MDAC 2.8 on modern Windows, or repeatedly register the DLL without evidence. Keep the application updated, retain its original installer, and use supported provider versions. In most cases, repairing the named application or repairing Windows components restores the correct OLE DB files without any manual DLL download.
FAQ
Is msdasc.dll a legitimate Microsoft file?
Yes. It is the Microsoft Data Access OLE DB Service Components Stub and belongs to the MDAC or WDAC family. Verify the path and Microsoft signature rather than trusting the filename alone.
Is msdasc.dll a system file?
On supported Windows versions, the underlying WDAC components are part of Windows. Older applications may also have installed or expected MDAC components. The correct location depends on the Windows generation, architecture, servicing model, and application.
Should I install Visual C++ Redistributable?
No. msdasc.dll is not a Visual C++ runtime file. Repair the application, Windows components, or the required database provider instead.
Should I register msdasc.dll?
Usually no. regsvr32 applies to DLLs that expose the required registration entry point. It does not repair a missing file, dependency, or provider.
Should I install MDAC 2.8 on Windows 11 or Windows 10?
Generally no. WDAC is included in modern Windows, and the historical MDAC 2.8 SP1 runtime is not a general repair package for current releases.
Why does Windows say the specified module cannot be found when the file exists?
The loader may be unable to find a dependency of msdasc.dll, or the application may be requesting a provider with the wrong architecture. Check the application’s database-provider requirement and 32-bit or 64-bit compatibility.
Can I copy msdasc.dll from another computer?
No. The other computer may have a different Windows release, architecture, component set, or security status. Restore the file through Windows servicing or the original application installer.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
