You upgraded to Windows 11. You double-clicked an .mdb file that has worked fine for years. Nothing happened — or worse, you got a cryptic error about the database not being recognized. You are not alone. This is one of the most common problems organizations face after a Windows upgrade, and the fix depends on which version of Access created the file, whether you have 32-bit or 64-bit software, and what you actually need to do with the data. This guide walks through every scenario.
The .mdb format was introduced with Access 1.0 in 1992 and remained the default through Access 2003. It uses the Microsoft Jet database engine — a technology Microsoft stopped actively developing in 2005. When Microsoft released Access 2007, the default format changed to .accdb, which uses the newer ACE (Access Connectivity Engine) driver instead of Jet.
Windows 11, like Windows 10 before it, does not include the Jet engine or the ACE engine out of the box. Previous Windows versions (XP, 7) shipped with Jet 4.0 as a system component because so many applications depended on it. That is no longer the case. Windows 11 assumes that if you need database engine support, you will install it yourself — either through an Office installation or by downloading the standalone Access Database Engine.
This means a clean Windows 11 machine with no Office installed has zero ability to open .mdb files. Even machines with Office installed can hit problems if there is a bitness mismatch between Office and the database engine, or if the .mdb file was created with an older Jet format version.
The error message you get tells you which fix to apply. Here are the most common ones:
| Error Message | Likely Cause | Jump To |
|---|---|---|
| "How do you want to open this file?" | No application associated with .mdb | Install ACE driver |
| "Unrecognized database format" | Access 97 file opened with newer engine | Access 97 section |
| "The database cannot be opened because the VBA project contained in it cannot be read" | VBA references to missing libraries | Migration section |
| "Could not use ''; file already in use" | Lock file (.ldb) stuck from previous crash | Delete the .ldb file |
| "Architecture mismatch" or ODBC error | 32-bit / 64-bit conflict | Bitness section |
| "Not a valid password" | Database-level or workgroup security | Migration section |
| "The database has been placed in a state by user 'Admin' on machine '...' that prevents it from being opened" | Exclusive lock from design mode | Open with /runtime switch or compact and repair |
If your error is not listed above, the most common catch-all fix is installing the correct version of the ACE driver. Start there.
The Microsoft Access Database Engine 2016 Redistributable is a free download that provides the ACE driver. It lets any application on your machine — not just Access — read and write .mdb and .accdb files through ODBC or OLE DB.
AccessDatabaseEngine_X64.exe. If you have 32-bit Office or no Office at all, download AccessDatabaseEngine.exe (the 32-bit version).If the ACE driver installation succeeds but your .mdb file still does not open, the problem is likely a format version issue (see the Access 97 section below) or you need to associate the .mdb extension with the correct application.
If you have Access installed but .mdb files do not open when you double-click them:
If Access does not appear in the list, your Office installation may not include Access. The standalone Access license or Microsoft 365 Apps for Business (or higher) includes it. Microsoft 365 Basic and Personal plans do not.
This is the single most frustrating issue with .mdb files on modern Windows. The problem manifests differently depending on what application is trying to read the database:
Scenario 1: A 32-bit application needs to read the .mdb, but you have 64-bit Office. This is the most common scenario. Many older line-of-business applications are 32-bit and use the 32-bit ODBC driver to connect to .mdb files. But if you installed 64-bit Office, only the 64-bit ACE driver is present. The 32-bit app cannot see the 64-bit driver.
The fix: You need to install the 32-bit ACE driver alongside your 64-bit Office. Normally this is not possible through the standard installer. The workaround is to run the 32-bit installer with the /passive flag:
AccessDatabaseEngine.exe /passiveThis forces installation without the conflict check. Both drivers will coexist, and 32-bit applications will use the 32-bit driver while 64-bit applications use the 64-bit driver.
Scenario 2: You have 32-bit Office and a 64-bit application needs the database. Less common, but the same solution in reverse — install the 64-bit ACE driver with the /passive flag.
Scenario 3: ODBC Data Source Administrator shows the wrong drivers. Windows 11 has two ODBC administrators — a 64-bit version and a 32-bit version. They are different programs:
C:\Windows\System32\odbcad32.exe — this is the 64-bit ODBC administrator (yes, System32 contains 64-bit binaries; the naming is a legacy quirk)C:\Windows\SysWOW64\odbcad32.exe — this is the 32-bit ODBC administratorIf you set up an ODBC connection in the wrong administrator, your application will not see it. 32-bit apps can only see DSNs created in the 32-bit ODBC administrator, and vice versa.
LegacyLeaps scans your .mdb files and tells you the exact Jet version, whether they contain VBA, linked tables, or workgroup security — before you change anything.
Run a Free ScanIf your .mdb file is being accessed by another application — a reporting tool, a custom business app, or a script — through ODBC, you need to configure a Data Source Name (DSN) correctly.
Your application should now be able to connect using the DSN name. If the application uses a connection string instead of a DSN, the format is:
Driver={Microsoft Access Driver (*.mdb, *.accdb)};DBQ=C:\Path\To\database.mdb;For databases with workgroup security (.mdw files), you need to add the SystemDB parameter:
Driver={Microsoft Access Driver (*.mdb, *.accdb)};DBQ=C:\Path\To\database.mdb;SystemDB=C:\Path\To\security.mdw;Access 97 databases use Jet 3.5, which is a different binary format from Jet 4.0 (used by Access 2000-2003). Modern versions of Access — including Access in Microsoft 365 — cannot open Jet 3.5 databases directly. When you try, you get one of these messages:
The conversion path for Access 97 databases is:
You cannot skip the middle step. You need an intermediate version of Access — specifically Access 2000, 2002 (XP), or 2003 — to open the Jet 3.5 database and convert it to Jet 4.0 format. Once it is in Jet 4.0 format, modern Access can open and convert it to .accdb.
If you do not have an old version of Access available, your options are:
pyodbc or mdbtools (Linux/Mac) to extract tables to CSV or SQL.Installing drivers and fixing ODBC connections is a perfectly valid approach if you need to read an old database occasionally. But if any of the following are true, you should migrate the database to a modern format rather than continuing to work around compatibility issues:
If two or more of these apply to your situation, stop patching and migrate. The cost of the migration is almost always less than the cost of the next outage or data loss event.
Once you decide to migrate, you have two main paths. The right choice depends on the size of the database, the number of users, and whether the Access forms and reports need to survive.
This is the simplest migration. The .accdb format is essentially an upgraded .mdb — same general architecture, but using the ACE engine instead of Jet. You keep your tables, queries, forms, reports, macros, and VBA code. The conversion handles most things automatically.
Best for: Single-user or small-team databases under 2 GB where the Access forms and reports are critical to the workflow.
What can break:
For larger databases or multi-user environments, moving the data tier to SQL Server (or Azure SQL) while keeping Access as a front-end is the standard approach. Microsoft provides the SQL Server Migration Assistant (SSMA) for Access to automate most of this process.
Best for: Databases with more than 5 concurrent users, databases approaching the 2 GB limit, or organizations that need proper backup, security, and audit capabilities.
What changes:
IIf(), Nz(), or DLookup())DoCmd.RunSQL with Jet SQL) needs updatingLegacyLeaps analyzes your databases, flags VBA issues, maps linked tables, and converts everything — without uploading your files anywhere. Your data stays on your machine.
Download LegacyLeaps FreeNo. Windows 11 does not include built-in support for .mdb files. You need either Microsoft Access (included with Microsoft 365 Apps for Business or standalone) or the free Access Database Engine (ACE driver) installed. Without one of these, double-clicking an .mdb file will prompt you to find an app in the Microsoft Store.
This usually means a 32-bit/64-bit mismatch. If you have 64-bit Access or the 64-bit ACE driver installed but the .mdb was created with Access 97 or Access 2000 using Jet 3.5, the 64-bit engine may not fully support the older Jet format. Installing the 32-bit ACE driver alongside a 32-bit application, or converting the .mdb to .accdb, typically resolves this.
If you only need to read the data occasionally, patching with drivers is fine. But if the database is actively used in production, converting to .accdb (or migrating to SQL Server) is the better long-term move. The .mdb format uses the legacy Jet engine which receives no security updates, has a 2 GB size limit, and lacks features like complex data types and attachment fields.
Access 365 cannot open Access 97 format databases directly. When you try, it will prompt you to convert the file to .accdb format. If the database contains VBA code or uses legacy features like Data Access Pages, the conversion may require manual fixes. You should always convert a copy and keep the original intact.
Practical fixes for legacy Excel and Access problems. No spam.