Fix Microsoft Jet OLE DB 4.0 Provider Not Registered on 64-Bit Windows
Question details
Resolve a Microsoft.Jet.OLEDB.4.0 provider registration error when connecting to an Access database on 64-bit Windows.

- Product
- Microsoft Jet OLE DB 4.0 and Microsoft Access Database Engine
- Device & OS
- 64-bit Windows
- Scenario
- An application using a 32-bit OLE DB provider needs to connect to an Access database on a 64-bit computer with 32-bit Office installed.
- Observed behavior
- The application reports that the Microsoft.Jet.OLEDB.4.0 provider is not registered.
Check whether the application process and installed Office are 32-bit or 64-bit, and note the provider name in the connection string. Microsoft.Jet.OLEDB.4.0 is a 32-bit provider, so a 64-bit process cannot load it.
Run the application as a 32-bit process
Use this approach when the application must continue using Microsoft.Jet.OLEDB.4.0.
On 64-bit Windows, a 32-bit application can use the 32-bit Jet provider if it is available and registered. Installing the Access Database Engine adds ACE, not the Jet 4.0 provider.
In Visual Studio, open the application project's Properties, select Build, and set Platform target to x86. Avoid x64 or an Any CPU configuration that runs the process as 64-bit.
Select Build > Rebuild Solution, then launch the rebuilt application and retry the database connection.
If the error remains, open the 32-bit Registry Editor at C:\Windows\SysWOW64\regedit.exe and look for HKEY_CLASSES_ROOT\Microsoft.Jet.OLEDB.4.0. If the key is missing, ask your Windows administrator to investigate the Jet installation or registration.

Switch the connection to the Access Database Engine provider
Use ACE when you can change the connection string and need a supported provider for the application's database format.
Work with Office spreadsheets in WPS Office
WPS Office is a free, lightweight alternative with a familiar interface for working with Office files. It can help you move spreadsheet work to WPS, but it does not fix Jet or ACE provider registration errors.

Frequently Asked Questions
Why does Jet fail on a 64-bit computer?
Microsoft.Jet.OLEDB.4.0 is a 32-bit provider. A 64-bit application process cannot load it, even if 32-bit Office is installed. Set the application's platform target to x86 if it must use Jet.
Does installing the Access Database Engine register Jet 4.0?
No. The Access Database Engine installs an ACE provider. To use it, change the provider name in the application's connection string and match the engine's bitness to the application process.
Do I need 64-bit Office to run on 64-bit Windows?
No. A 32-bit Office installation and 32-bit applications can run on 64-bit Windows. A 32-bit application can use a compatible 32-bit provider without switching Office to 64-bit.
Why does the provider error remain after I build a library for x86?
The application or service hosting the library may still be running as a 64-bit process. Check the host's platform settings and run the database connection in a 32-bit process when using Jet 4.0.




