ODBC Connection Errors After Windows 11 Update — How to Fix Access and Excel Data Sources

Monday morning. You open the Access database your team has used for five years. The linked tables that pull data from SQL Server — the ones that have always worked — now show #Deleted in every row. Or you get an error: "ODBC — call failed. [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified."

You check Excel. The workbook that refreshes sales data from MySQL every morning? Same thing. "ODBC driver is not installed" or "The DSN refers to a driver which is not installed."

What changed? Windows updated over the weekend. Nobody touched the database. Nobody touched the connection strings. The drivers just... vanished.

This is one of the most common and least understood problems facing IT teams managing legacy Office files on Windows 11. Here's what's actually happening and how to fix it.

Quick Reference: Common ODBC Errors and What They Mean

Error Message	Likely Cause	Fix
"Data source name not found"	DSN exists in 32-bit registry but Office is 64-bit	Recreate DSN in 64-bit ODBC Administrator
"ODBC driver is not installed"	Driver removed by Windows update or wrong bitness	Install matching 64-bit or 32-bit driver
"Architecture mismatch"	32-bit driver loaded by 64-bit Office	Install 64-bit driver or switch to 32-bit Office
"#Deleted" in linked tables	ODBC connection silently failing	Relink tables with correct driver/DSN
"Connection failed: SQLState '08001'"	Driver can't reach server (firewall, TLS, or driver mismatch)	Check driver version and server connectivity

Why Windows 11 Updates Break ODBC Connections

Three things converge to create this problem:

1. The 32-bit to 64-bit Office Shift

For years, Microsoft installed 32-bit Office by default — even on 64-bit Windows. Most ODBC drivers, DSNs, and connection strings in production were configured for 32-bit. Starting with Microsoft 365 and Office 2021, 64-bit is now the default installation. If your organization upgraded Office or got new machines with Windows 11, you likely went from 32-bit to 64-bit Office without anyone realizing the ODBC implications.

The critical thing to understand: Windows maintains two completely separate ODBC registries. A 32-bit DSN is invisible to a 64-bit application. A 32-bit driver cannot be loaded by a 64-bit process. Your connection strings reference drivers that still exist on disk — but your 64-bit Office literally cannot see them.

2. Windows Updates Remove or Replace Drivers

Feature updates (like 23H2 to 24H2) can remove older ODBC drivers that Microsoft considers deprecated. The "Microsoft Access Driver (*.mdb)" — the Jet 4.0 ODBC driver — is particularly affected. It's a 32-bit-only driver that ships with Windows but gets removed or disabled during major updates. If your Access database links to .mdb files via ODBC (rather than native Access linking), this breaks silently.

3. The ODBC Administrator Confusion

Windows has two ODBC Data Source Administrator programs with the same name:

How to Diagnose the Problem

Step 1: Determine Your Office Bitness

Open Access or Excel. Go to File > Account > About Access (or About Excel). The first line of the About dialog says either "64-bit" or "32-bit." This is the single most important piece of information for fixing ODBC issues. Write it down.

Step 2: Check Which Drivers Are Installed

Open the ODBC Administrator that matches your Office bitness:

• 64-bit Office: Run C:\Windows\System32\odbcad32.exe
• 32-bit Office: Run C:\Windows\SysWOW64\odbcad32.exe

Click the Drivers tab. This shows every ODBC driver registered for that bitness. If the driver your connection string references isn't listed here, that's your problem.

Step 3: Find Your Current Connection Strings

In Access, right-click a linked table and choose Linked Table Manager. The connection string for each table shows the driver name. Look for the DRIVER= portion. Common examples:

• DRIVER={SQL Server} — the legacy SQL Server driver (ships with Windows)
• DRIVER={ODBC Driver 17 for SQL Server} — the modern Microsoft driver
• DRIVER={MySQL ODBC 8.0 Unicode Driver} — MySQL Connector/ODBC
• DRIVER={Microsoft Access Driver (*.mdb, *.accdb)} — Access-to-Access ODBC links

In Excel, go to Data > Queries & Connections, right-click the connection, and choose Properties. The connection string is under the Definition tab.

How to Fix It

Fix 1: Install the Correct Driver Bitness

If you're on 64-bit Office and your driver only exists in the 32-bit registry, you need the 64-bit version of that driver.

For SQL Server: Download "Microsoft ODBC Driver 18 for SQL Server" from Microsoft. It installs both 32-bit and 64-bit drivers. This replaces the ancient {SQL Server} driver with the modern {ODBC Driver 18 for SQL Server}.

For MySQL: Download MySQL Connector/ODBC from the MySQL website. Choose the 64-bit MSI installer. After installation, verify it appears in the 64-bit ODBC Administrator's Drivers tab.

For Access-to-Access ODBC links: Install the "Microsoft Access Database Engine 2016 Redistributable" in the bitness matching your Office installation. Be aware that you cannot install a different-bitness Access Database Engine alongside an existing Office installation — they'll conflict.

Fix 2: Recreate Your DSNs

If you were using named DSNs (System DSN or User DSN), you need to recreate them in the correct ODBC Administrator:

1. Open the ODBC Administrator matching your Office bitness
2. Go to the System DSN tab (or User DSN)
3. Click Add and select the driver
4. Enter the same server, database, and authentication details as your old DSN
5. Use the same DSN name so your connection strings don't need updating

Fix 3: Switch to DSN-less Connection Strings

DSN-based connections are fragile — they depend on a registry entry that can disappear during updates. DSN-less connection strings embed the driver name and server details directly, making them more portable and resilient.

Instead of:

DSN=MyCompanyData;UID=reader;PWD=*****

Use:

DRIVER={ODBC Driver 18 for SQL Server};SERVER=dbserver.company.local;DATABASE=CompanyData;UID=reader;PWD=*****

In Access VBA, you can update linked table connections programmatically:

Dim td As DAO.TableDef
For Each td In CurrentDb.TableDefs
    If Len(td.Connect) > 0 And InStr(td.Connect, "ODBC") > 0 Then
        td.Connect = "ODBC;DRIVER={ODBC Driver 18 for SQL Server};" & _
                     "SERVER=dbserver.company.local;" & _
                     "DATABASE=CompanyData;" & _
                     "Trusted_Connection=Yes"
        td.RefreshLink
    End If
Next td

Fix 4: When No 64-bit Driver Exists

Some legacy database systems (Pervasive SQL, older Oracle versions, AS/400 ODBC drivers) never released 64-bit ODBC drivers. If you're stuck with a 32-bit-only driver, your options are:

• Install 32-bit Office: You can install 32-bit Microsoft 365 or Office 2021 on Windows 11. It works fine. Go to your Microsoft 365 admin portal, choose "Other install options," and select 32-bit.
• Use an ODBC-ODBC bridge: Products like OpenLink ODBC Bridge can proxy a 32-bit driver through a 64-bit interface. Complex but works for legacy drivers with no upgrade path.
• Migrate the data source: If the upstream database is the legacy piece, consider migrating it to SQL Server or PostgreSQL and updating your Access/Excel connections.

Special Case: .mdb Files Linked via ODBC

Some Access databases link to other .mdb files using ODBC rather than native Access linking. This was common when IT teams wanted a single connection method across different database types. The problem: the {Microsoft Access Driver (*.mdb)} is the old Jet 4.0 ODBC driver, which is 32-bit only and has been deprecated since Windows 7.

The fix: convert your linked .mdb files to .accdb format. Then use the {Microsoft Access Driver (*.mdb, *.accdb)} driver from the Access Database Engine Redistributable, which comes in a 64-bit version.

Better yet: convert the ODBC links to native Access linked tables. Native Access table linking doesn't go through the ODBC layer at all — it's faster, more reliable, and immune to ODBC driver issues. In Access, use External Data > Access to create native links.

Special Case: Excel Power Query and Legacy ODBC

Excel's Power Query (Get & Transform Data) sometimes creates ODBC connections behind the scenes. If you built a query using the "From ODBC" connector, it stores the DSN reference in the workbook. When the DSN disappears after a Windows update, the query breaks.

To fix: edit the query in Power Query Editor, go to Home > Advanced Editor, and update the Odbc.DataSource call to use a DSN-less connection string. Or better yet, switch to a native connector (like "From SQL Server Database") which manages the driver automatically.

Preventing Future ODBC Breakage

• Document every ODBC connection: Maintain a list of every DSN, driver, and connection string in your organization. When Windows updates break something, you'll know exactly what to recreate.
• Use DSN-less connections everywhere: They survive Windows updates because the driver reference travels with the application, not the registry.
• Standardize on one Office bitness: Pick 32-bit or 64-bit for your organization and stick with it. Mixed environments are where ODBC problems multiply.
• Test Windows updates on a pilot machine: Before rolling updates to all users, test on one machine that has your full set of ODBC connections configured.
• Keep driver installers accessible: Download and store the MSI installers for every ODBC driver you use. When a Windows update removes one, you can reinstall immediately.

Frequently Asked Questions

Why did my ODBC connection stop working after a Windows 11 update?

Windows 11 updates can remove or replace older ODBC drivers, especially 32-bit versions. If your Office installation is 64-bit (now the default) and your drivers were 32-bit, the update makes an existing incompatibility visible. The connection string points to a driver that exists on disk but can't be loaded by a 64-bit process.

How do I fix "ODBC driver not found" in Access on Windows 11?

Determine whether you're running 32-bit or 64-bit Access (File > Account > About Access). Open the matching ODBC Administrator — 64-bit is at C:\Windows\System32\odbcad32.exe, 32-bit is at C:\Windows\SysWOW64\odbcad32.exe. Check the Drivers tab for your driver. If missing, install the driver matching your Office bitness.

What is the 32-bit vs 64-bit ODBC mismatch?

Windows runs two separate ODBC registries — one for 32-bit and one for 64-bit applications. A 32-bit driver is invisible to 64-bit Office. If you upgraded from 32-bit to 64-bit Office, all your 32-bit DSNs and drivers become invisible to your applications.

Can I use 32-bit ODBC drivers with 64-bit Office?

No. A 64-bit process cannot load a 32-bit DLL. Install the 64-bit version of the driver, or switch to 32-bit Office. For drivers where no 64-bit version exists, 32-bit Office on Windows 11 is a supported configuration.

How do I find which ODBC driver my Access database uses?

Right-click any linked table in the Navigation Pane and choose Linked Table Manager. The connection string includes the driver name (e.g., DRIVER={SQL Server}). In VBA: CurrentDb.TableDefs("YourTable").Connect.

Related Resources

• Microsoft Access Runtime on Windows 11 — What Still Works
• Access Database Not Opening After Windows 11 Update
• MDB to ACCDB Migration Guide
• Migrating Access Linked Tables to Modern Databases

← Back to all posts