Start with this diagnostic checklist
Before replacing anything, write down:
- Which program fails: an older Access database,
.mdbutility, business application, or another legacy program. - When it fails: at launch, when opening an
.mdbfile, while running an Access wizard, or when selecting a VBA reference. - The exact message: “a0004071.dll was not found,” “The specified module could not be found,” or Access’s “Error in loading DLL.”
- The application architecture: 32-bit or 64-bit.
- What changed: an Office upgrade, application reinstall, antivirus quarantine, registry-cleaning utility, or change from 32-bit to 64-bit Office.
The fastest safe fix is usually to repair or reinstall the program that needs a0004071.dll, not to copy a replacement DLL into Windows.
What a0004071.dll actually is
a0004071.dll is commonly identified as a renamed or catalogued copy of dao360.dll, the Microsoft DAO 3.6 Object Library used with Microsoft Jet. Microsoft documentation uses the canonical filename dao360.dll, not a0004071.dll.
As an Amazon Associate I earn from qualifying purchases.
DAO 3.6 belongs to older database software, especially applications using Microsoft Access .mdb files and legacy DAO code. The file is not a normal Windows 10 or Windows 11 System32 runtime component.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Microsoft documents the normal DAO locations as:
- 32-bit Windows or 64-bit Office:
C:Program FilesCommon FilesMicrosoft SharedDAOdao360.dll - 32-bit Office on 64-bit Windows:
C:Program Files (x86)Common FilesMicrosoft SharedDAOdao360.dll
The exact relationship between a0004071.dll and dao360.dll is based on third-party file metadata rather than a current Microsoft file catalog. Treat the error name as a clue pointing toward DAO 3.6, then verify the installed application and its trusted dao360.dll.
#1 Best Overall
Microsoft also states that Jet and Jet DAO are 32-bit components. A 32-bit application can use them on 64-bit Windows through WOW64, but a native 64-bit application cannot use 32-bit Jet DAO directly.
Fix 1: Repair the application that shows the error
This is the best first step when one older program fails and the rest of Windows works.
Repair from Windows Settings
- Close the affected program.
- Press Windows key + I.
- Select Apps.
- Select Installed apps on Windows 11, or Apps & features on Windows 10.
- Find the database program, Office installation, or legacy application.
- Select the three-dot menu beside it.
- Choose Advanced options, if available.
- Select Repair.
- Restart Windows.
- Open the original program and repeat the action that produced the error.
The Repair option may not appear for every desktop application. If it is missing, use the program’s original installer or Control Panel.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Repair from Control Panel
- Press Windows key + R.
- Type
appwiz.cpl. - Press Enter.
- Select the affected application or Microsoft Office.
- Select Change, Repair, or Modify.
- Follow the installer prompts.
- Restart Windows and test the program again.
If the application has its own launcher, look for Repair, Verify, Scan files, or Reinstall components. Use the original vendor installer or installation media. For a program that owns the database components, reinstalling that program remains the definitive repair.
If repair does not restore the application, uninstall it, restart Windows, and reinstall it from trusted original media. Back up the application’s databases and configuration files first.
What success looks like
The original application opens without the missing-file message, and the database or Access wizard that previously failed completes normally. If the error returns immediately after reinstalling, check the application’s bitness before attempting registration.
Fix 2: Confirm the 32-bit and 64-bit combination
A frequent failure pattern is:
- 64-bit Windows
- 32-bit Office or legacy application
- 32-bit DAO 3.6 required
- The wrong registration tool or wrong program directory used
Windows 64-bit does not mean every installed application is 64-bit. Check the application or Office architecture.
Check Office architecture
For Microsoft 365 or Office:
- Open Word or another Office application.
- Select File.
- Select Account.
- Select About Word, About Access, or the equivalent application.
- Read the line showing 32-bit or 64-bit.
For a third-party program, check its documentation, installer name, program properties, or contact the vendor. Do not assume that a 64-bit Windows installation requires a 64-bit database component.
Match the DAO location
On 64-bit Windows:
- A 32-bit Office installation commonly uses the DAO file under
C:Program Files (x86)Common FilesMicrosoft SharedDAO - A 64-bit Office installation may use
C:Program FilesCommon FilesMicrosoft SharedDAO
Current Click-to-Run Office installations can store components in Office-specific locations, so the older shared path is not guaranteed. Repair Office first if the file is absent.
Do not install a 64-bit Access Database Engine package merely to satisfy a 32-bit DAO error. ACE and DAO are different data-access technologies, and a 64-bit ACE installation does not make 32-bit Jet DAO available to a 64-bit process.
Rank #2
Fix 3: Register dao360.dll only for an Access loading error
Registration is appropriate when the trusted DAO file exists but its COM registration is missing or points to the wrong location. It is not a general-purpose repair for every missing DLL message.
Recommended Free Tools
Microsoft documents this path for Access errors such as Error in loading DLL, including wizard failures caused by missing, damaged, outdated, or misregistered DAO or ADO components.
Register DAO for 32-bit Office on 64-bit Windows
- Open File Explorer.
- Confirm that this file exists, adjusting the path if Office uses a different trusted location:
C:Program Files (x86)Common FilesMicrosoft SharedDAOdao360.dll
- Open the Start menu.
- Type Command Prompt.
- Right-click Command Prompt.
- Select Run as administrator.
- Run:
%windir%SysWOW64regsvr32.exe "%CommonProgramFiles(x86)%Microsoft SharedDAOdao360.dll"
- Select OK on the registration result.
- Restart Access or the affected program.
Register DAO for 64-bit Office on 64-bit Windows
Use this only when the application that needs DAO is genuinely 64-bit and the installed DAO component is in the 64-bit shared location.
- Open Command Prompt as administrator.
- Run:
%windir%System32regsvr32.exe "%CommonProgramFiles%Microsoft SharedDAOdao360.dll"
- Restart Windows or reopen the application.
The names are counterintuitive. On 64-bit Windows, System32 contains the 64-bit registration tool, while SysWOW64 contains the 32-bit registration tool.
If Microsoft Access still reports a loading error involving ADO, Microsoft also documents registering msado15.dll from its trusted installed location. Do not register random files simply because their names resemble the error.
If regsvr32 says the module could not be found
That message does not always mean the target file is absent. It can indicate:
- The command points to the wrong path.
- The wrong 32-bit or 64-bit
regsvr32was used. - A dependent component is missing.
- The file is damaged.
- The COM registration belongs to another Office installation.
Return to application repair and architecture matching. Do not copy a DLL into System32 or `SysWOW64 to make the message disappear.
Fix 4: Check Windows Security quarantine
Antivirus software can remove or quarantine an installed DAO component after an application update or 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 minute- Open Windows Security from the Start menu.
- Select Virus & threat protection.
- Select Protection history.
- Review recent actions involving the application, Office, Jet, DAO, or the reported filename.
- Do not restore the file solely because its name matches the error.
- Restore or allow it only when the file came from the trusted original application or Microsoft installation and its origin is verified.
- Run the application repair again after restoring a trusted component.
If Windows Security detects the file again, stop restoring it and scan the system. An unknown DLL should not be added to exclusions. Reinstall the parent application from trusted media instead.
Rank #3
- 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
Fix 5: Repair protected Windows components
SFC and DISM can repair damaged Windows-protected components. They generally do not restore an Office-installed or third-party DAO file, so use this step when Windows itself is unstable or multiple built-in components are failing.
Run DISM, then SFC
- Open the Start menu.
- Type Command Prompt.
- Right-click it.
- Select Run as administrator.
- Run:
DISM /Online /Cleanup-Image /RestoreHealth
- Wait for it to finish.
- Run:
sfc /scannow
- Restart Windows.
- Test the affected application again.
Microsoft recommends running DISM before SFC. If SFC reports that it found and repaired corrupted files, restart and test. If it reports that it could not repair some files, repeat the application repair rather than manually replacing DAO.
Repeating SFC and DISM without knowing which component changed can make this step difficult to diagnose. Outbyte PC Repair can show what it identifies before repair, while the repair functions require the full version; it is optional, and reinstalling the specific application remains the definitive fix when that application owns DAO.
Fix 6: Install only the data-access package the program requires
Do not treat every Microsoft data-access package as interchangeable.
MDAC
MDAC 2.8 and MDAC 2.8 SP1 are not a general modern solution for this error. Microsoft documentation says the MDAC 2.8 SP1 redistributable was intended for older platforms, while later Windows versions include Windows Data Access Components as part of the operating system.
Do not install an old MDAC redistributable on Windows 10 or Windows 11 just because a search result recommends it.
Access Database Engine
Access Database Engine provides ACE and related Office connectivity components. It is not automatically a replacement for DAO 3.6. Microsoft provides separate 32-bit and 64-bit installers, and the package must match the application or Office architecture.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Use Access Database Engine only when the application documentation specifically requires ACE, OLE DB, or an Access Database Engine provider. It may resolve an ACE provider error, but it does not prove that dao360.dll has been repaired.
For an application that explicitly requires DAO 3.6, repair or reinstall the original application or compatible Office installation first.
Fix 7: Check for a recent change with System Restore
Use System Restore when the error began after a known software installation, Office change, or system modification and a suitable restore point exists.
- Press Windows key + R.
- Type
rstrui.exe. - Press Enter.
- Select Next.
- Choose a restore point from before the failure.
- Select Scan for affected programs if available.
- Review the changes.
- Select Next, then Finish.
- Let Windows restart and complete the restore.
System Restore rolls back system files, registry settings, and installed programs. It does not normally remove personal files. Afterward, test the original application before reinstalling recent updates.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
If no restore point exists, return to application repair and verify the application’s installer.
Fix 8: Update or reinstall related drivers only when evidence points there
A DAO error is usually not a graphics, chipset, printer, or storage-driver problem. Check drivers only if the application also crashes with device errors, Windows reports hardware problems, or the failure began after a hardware or driver change.
Check Device Manager
- Right-click the Start button.
- Select Device Manager.
- Expand categories related to the suspected device.
- Look for a yellow warning icon.
- Right-click the device.
- Select Properties.
- Read the Device status message under General.
- Open the Driver tab.
- Select Update Driver and search automatically, or install a driver downloaded from the device manufacturer.
- Restart Windows and test the application.
Do not remove a working device driver simply because a0004071.dll is missing. Outbyte Driver Updater can identify stale drivers during the manual search, but the driver installation requires the full version; it is optional and does not replace repairing the legacy application that requires DAO.
Fix 9: Use Windows Features only when the application requires them
Windows Features does not normally install DAO 3.6. Enabling random legacy components can add confusion rather than repair the missing library.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesIf the program’s documentation specifically requires a Windows feature:
- Press Windows key + R.
- Type
optionalfeatures. - Press Enter.
- Review the listed features.
- Enable only the feature named by the application’s documentation.
- Select OK.
- Restart Windows if prompted.
- Test the application.
Do not enable an optional feature as a substitute for installing the original database application.
Why downloading a0004071.dll is the wrong first move
A loose DLL from an arbitrary download archive can be:
- The wrong architecture.
- An incompatible build.
- Modified or malicious.
- Missing required dependencies.
- Unregistered even after copying.
- Unrelated to the application that generated the error.
Copying it into System32, SysWOW64, or the application directory can also create a second problem by making Windows load the wrong copy. The safe sources are the original application installer, a supported Microsoft Office or Access repair, and Microsoft’s own Windows repair and recovery procedures.
The filename in the error is not proof that a standalone file should be downloaded. First identify the program that needs DAO, repair that program, and use registration only after confirming the trusted installed dao360.dll.
When to use System Restore or Windows recovery
Use System Restore when a restore point predates the failure and the problem followed a specific software change.
Consider broader Windows recovery only when:
- Multiple unrelated Windows components are failing.
- DISM and SFC cannot repair the system.
- Malware or severe system corruption is suspected.
- The original application installer is unavailable and the system has a reliable backup.
Back up personal files and application databases first. A Windows recovery operation is not a substitute for finding the legacy program that owns DAO.
Best Value
FAQ
Is a0004071.dll a genuine Windows file?
It is a real file topic associated with the Microsoft DAO 3.6 Object Library, but it is not the canonical Microsoft filename used in current documentation. Microsoft refers to the component as dao360.dll.
Which program installed it?
There is no single universal modern application associated with the name. It usually points to an older Access database, Jet-based utility, or business application. The program that fails is the best lead.
Can a 64-bit application use DAO 3.6?
Microsoft says Jet and Jet DAO have no native 64-bit version. A 32-bit application can use them on 64-bit Windows through WOW64. A native 64-bit application needs a different supported data-access path or a compatible 32-bit version of the application.
Should I install MDAC?
Not as a general fix on Windows 10 or Windows 11. MDAC, Jet DAO, and ACE are different components, and an old MDAC redistributable does not automatically restore DAO 3.6.
Should I install Access Database Engine?
Only when the application specifically requires ACE or an Access Database Engine provider. It is not a guaranteed replacement for dao360.dll, and its bitness must match the application or Office installation.
When should I use regsvr32?
Use it when a trusted dao360.dll exists and the error is caused by missing or damaged COM registration, especially Access’s “Error in loading DLL.” Use the registration tool matching the application architecture.
Why does the file exist but the error continue?
The COM registration may be missing, point to an old path, or be in the wrong 32-bit or 64-bit registry view. A dependency or damaged application installation can produce the same result.
Can SFC or DISM restore it?
Usually not. They repair protected Windows components. DAO installed by Office or a third-party application normally requires Office or application repair.
What if every repair fails?
Check the program’s own repair or file-verification option, confirm whether it requires 32-bit DAO, and contact the application vendor. Do not replace the file with an arbitrary download.
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 problemsQuick 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.
