ACEOLEDB.DLL from Microsoft 365 Apps crash with Exception code 0xc0000005

No, unfortunately not: Microsoft is no longer going to correct these old drivers. I manually do a check on the contents of those registry keys and when they were changed by Windows, I put them back the way it works:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{3BE786A0-0366-4F5C-9434-25CF162E475E}\InprocServer32]

@="C:\Program Files\Common Files\Microsoft Shared\OFFICE16\ACEOLEDB.DLL"

"ThreadingModel"="Both"

Hope this is of some use to you....

Hi Bart, Yes, I think this trouble is still there in Access 2016 Database engine of Microsoft 365 (Office), also in today's 16.0.17231.20036 version. Microsoft 365 keeps on updating itself regularly and overwrites the failing version on customer PC's. Just two weeks ago had the last case. Workaround we have been using for 2 years is to open one database connection when program starts, and keep it alive. Close it only until the program ends. Code snippet here below:

Support for the Access Database Engine 2016 Redistributable ended on October 14, 2025. The recommended replacement is the Microsoft 365 Access Runtime. On my machine, the runtime's ACEOLEDB.DLL was signed on Dec 15, 2025. You might want to try out that version.

A static global connection fix might mean the connection pool does something unexpected when shutting down. You can try disable OLE DB Resource Pooling with OLE DB Services = 0; (at a cost of speed and resource usage) in your connection strings to see if it makes a difference.

has the problem solved with you? we also have an ACEOLEDB.DLL crash with Exception code 0xc0000005 with an APP with OfficePro2021LTSR current version. Microsoft is unable to analyze the problem, even though the problem has been recurring for years, either MS is incapable or ignorant?! and unfortunately you can forget about the support for some years, you have the feeling that the problems are trying to solve by "Google" or predetermined standard answers and have no idea what we are talking about. It has nothing to do with Access installation either, we have Office WITHOUT Access installed, the faulty DLL is located in an office shared folder and is always installed with it.

I see that this is already an older ticket, but I am also bumping into a completely similar problem over the last few months, both on my development device and on all client devices. I have created a vb application based on an access database. This of course requires the accessdbengine. What I was able to figure out in the last months is the following: when the accessdbengine is not yet installed, i.e. only office365, the below registry entries have the value “C:\Program Files\Microsoft Office\root\VFS\ProgramFilesCommonX64\Microsoft Shared\OFFICE16\ACEOLEDB.DLL” with version 16.0.17231.20036 but then the application crashes on the connectionstring or sql strings.

-          [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{3BE786A0-0366-4F5C-9434-25CF162E475E}\InprocServer32] -          [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{3BE786A0-0366-4F5C-9434-25CF162E475F}\InprocServer32] -          [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{3BE786A2-0366-4F5C-9434-25CF162E475E}\InprocServer32] -          [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{3BE786A2-0366-4F5C-9434-25CF162E475F}\InprocServer32] After installing AccessDBengine, the above registry entries change to "C:\Program Files\Common Files\Microsoft Shared\OFFICE16\ACEOLEDB.DLL" with as version16.0.5320.1000 and with these registry entries the application does work. But always after several days this registry entry keeps getting reset. Can this be disabled? Did I do something wrong when designing the application? Is this some kind of bug