If you see the error “Data Source.Error: The ‘Microsoft.ACE.OLEDB.12.0’ provider is not registered,” it means Excel or Power Query cannot find the background software driver needed to read an external file, like an Access database or an older .xls spreadsheet. This usually happens because there is a mismatch between your version of Excel and the background driver, specifically, one is running in 64-bit mode while the other is running in 32-bit mode. To fix this right away, you need to download and install the Microsoft Access Database Engine driver that matches your specific version of Excel.
Fast-Fix: The 45-Second Solution
This low-risk error occurs due to a bitness mismatch between your Excel installation and the installed Windows data connection drivers, which prevents Power Query from accessing legacy source files. While your data remains secure, connectivity is suspended until corrected. To resolve this, verify your Excel architecture (32-bit or 64-bit) and install the corresponding Microsoft Access Database Engine driver.
Diagnostic Snapshot
- Severity Tier: Moderate (Blocks data refreshes and external file imports, halting automated workflows)
- Data Safety Risk: Low (No data is deleted or corrupted; the communication link is just down)
- Common Cause: Mixing 34-bit background software with 64-bit Office installations, or missing database drivers entirely after an update
- Admin Requirement: Requires local computer administrative privileges to install the missing system driver
Condition: Low Risk vs. High Risk
- Low Risk Condition: The error pops up on a single desktop computer while trying to import an old
.xlsor.mdbfile. Standard formulas, web data connections, and native cloud sync profiles continue to perform normally. - High Risk Condition: The failure hits a shared business report or an automated workspace path. This blocks multiple departments from refreshing central inventory, sales, or manufacturing data. If the local client cache breaks down completely during these data transfers, you may encounter deeper application sync cycles like the one detailed in “Refresh Recommended” Loop when Co-authoring in Teams.
The System Break (What This Means)
Think of the ACE OLEDB 12.0 driver like a specialized physical adapter cable connecting two different pieces of machinery. When you ask Power Query to extract data from an external file, Excel looks into your Windows system directory for this adapter plug to translate the incoming data stream.
The system break occurs when Excel tries to use the adapter but finds it missing or built for a completely different size. A 64-bit version of Excel is physically incapable of connecting to a 32-bit driver, and vice versa.
[64-bit Excel Engine] ─── (Tries to connect) ───► [32-bit ACE Driver] = CONNECTION CRASH
│
(Driver is "Not Registered")
If the bitness sizes do not align perfectly, Windows fails to register the connection path. Excel drops the connection entirely and displays the “provider is not registered” error message.
Root Cause Probability
- Likely (60%): Bitness conflict. You are running 64-bit Excel, but an older 32-bit version of the Access database engine (or older Office components) is installed on the computer.
- Possible (30%): The driver is completely missing. A recent Windows update or corporate software migration wiped out legacy database components.
- Rare (10%): The driver is present, but the underlying Windows Registry paths are corrupted. If your file data model fails due to a larger cloud capacity issue rather than a local driver block, look at Troubleshooting “File too large for Excel Online” (The 100MB+ Barrier).
Conflict Escalators
Specific hardware environments and software versions can make this driver issue worse:
- Automatic M365 Background Updates: If your company silently updates your computer from old 32-bit Office apps to modern 64-bit Microsoft 365, the old 32-bit data engines are often left behind, causing immediate connection errors.
- Mixed Database Formats: Using a mix of newer
.accdbfiles and older.mdbfile paths in the same Power Query model strains the driver mapping, especially if trust settings are disabled. For help with broken macro and file trust paths, see “External Links are Disabled” in Excel Online (The Trust Center Fix). - Web Browser Virtualization: Running Excel inside limited browser frameworks or cloud wrappers can prevent local system drivers from responding, which can sometimes look like a standard web drop covered in How to Resolve “Workbook Session Timeout” in SharePoint-hosted Excel.
Progression: 1 Hour → 24 Hours → 1 Week
- 1 Hour: Local data refreshes are blocked. Users are forced to manually copy and paste text information from old files into modern formats.
- 24 Hours: Automated workflows stall out. Executive dashboards start showing stale information because background update schedules are failing.
- 1 Week: Workaround accumulation. Out of frustration, users build messy, manual tracking spreadsheets to bypass the broken connections. This fragments company data and makes future automated cleanups much harder.
Common Misdiagnoses
The most common mistake is assuming the source spreadsheet or database file is corrupted. Technicians often waste time rebuilding the query steps or running file repair utilities.
Another common error is confusing this database engine block with an issue regarding unsupported active layout shapes. For visual layout and object rendering errors, consult Troubleshooting “Object not supported” in Excel Online (Shapes/Textboxes). The ACE provider issue is purely a system driver mismatch, not a design or file formatting limitation.
Immediate Action Steps
To match your system bitness and register the driver correctly, follow these steps:
Step 1: Verify Your Excel Bitness
Open Excel on the computer experiencing the error. Click on File in the top left corner, select Account, and click the About Excel button. Look at the top line of the text panel to see if it explicitly says 32-bit or 64-bit.
Step 2: Download the Matching Driver
Go to the official Microsoft Download Center and search for the Microsoft Access Database Engine 2016 Redistributable (or the latest stable version provided by your IT department).
- If your Excel is 64-bit, download
AccessDatabaseEngine_X64.exe. - If your Excel is 32-bit, download
AccessDatabaseEngine.exe.
Step 3: Use the Command Prompt Bypass (If Installer Blocks You)
If you have a mixed software setup, the installer might warn you that it cannot proceed because it detects conflicting Office components. You can bypass this check:
- Click the Windows Start menu, type
cmd, right-click Command Prompt, and choose Run as Administrator. - Type the file path of your download followed by
/passive. For example:C:\Users\YourName\Downloads\AccessDatabaseEngine_X64.exe /passive - Press Enter. This forces the driver to install silently in the background without throwing an error block. Restart Excel and refresh your query.
Hard-Stop Red Flags
Stop attempting local installations and contact your enterprise infrastructure team if you see these symptoms:
- The installer fails instantly with an access warning that says “Installation Prevented by Group Policy”.
- Installing the driver causes other core office apps (like Outlook or Word) to crash or ask for license keys upon launch.
- The system prevents any driver installation because your machine profile has been isolated by automated network security policies.
What the IT Admin Will Check
When this driver failure pops up across multiple corporate workstations, a systems administrator must verify these central points:
- Centralized App Deployments: Ensure that internal endpoint software packages (like Microsoft Intune) are deploying uniform 64-bit versions of Microsoft 365 Apps across all company computers.
- Automated Patch Management: Check if corporate update policies are pushing conflicting system drivers that break legacy data links, a common root cause for automated execution breaks like those in Troubleshooting “Office Script” Execution Failures in Automated Workbooks.
- Registry Key Verification: Deploy a policy to verify that the following path exists and points to the correct driver file location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\Access Connectivity Engine\Engines.
Resolution Complexity
- User Installation (Minor): Downloading and installing the matching driver executable from Microsoft’s website.
- Command Line Install (Moderate): Using the administrative Command Prompt switch to force install the driver past legacy software blocks.
- Enterprise Standardization (Major): Re-building deployment profiles to convert all corporate machines to the same 64-bit architecture and updating all data sources to cloud-native formats.
Related Error Escalators
Driver and connection failures often trigger other automated file errors across shared workspaces. If your data import bugs spread into your shared cloud libraries, read these specialized troubleshooting guides:
- If your local connection failures start causing automatic backup and saving routine errors, follow “AutoSave is Off” because of “Unsupported Features” in Cloud Files.
- If your local data updates break down while hosting real-time online business reviews, see Troubleshooting “Excel Live” Sync Failures during Teams Meetings.
- For errors concerning regional mismatches during data transfers, consult How to Fix “Regional Format Mismatches” in Multi-User Cloud Workbooks.
Ticket Closed
If you need to refresh your report immediately and cannot install software, your quickest workaround is to save the source file as a generic .csv or .txt format, which does not require advanced drivers to read. For a long-term fix, check your version of Excel under the About Excel menu and install the matching Access Database Engine driver. This aligns your software pieces and restores your automated Power Query paths instantly.