KB5065426 on Windows 11 with Program MS Access

Question

I would like to report an issue with a connection in MS Access 2010, I know it's old but it must run like this because of compatibilities with our other soft in our industry.

This is how my connection is declared : "Public MyAccessConnexion As New ADODB.Connection"

When I do a query in the vba code to take datas in a another MS Access Database on the LAN on a Network disk. MS Access close immediatly.

In the same program, I call a lot of other query to Oracle or SQL server with ADODB.Connection without problem.

I uninstall this Update yesterday and it works. this morning, the update was automatically installed by Windows Update. Problem comes again. I uninstalled again : No problem.

Other Computers with Windows 10 runs without problem.

Answer 1

Hi,

We understand that you're using MS Access 2010 due to industry-specific compatibility requirements, and that the application crashes when executing ADODB queries against another Access database on a network disk.

Based on recent reports, this behavior may be linked to the KB5064081 Windows update, which has caused similar crashes in environments using the Microsoft.Jet.OLEDB.4.0 provider. While connections to Oracle and SQL Server remain stable, Access-to-Access queries via ADODB may fail due to this update.

As a temporary workaround, you can continue uninstalling the update or switch to the Microsoft.ACE.OLEDB.12.0 provider, which has shown more stability in affected environments. We also recommend submitting feedback via the Feedback Hub to help our engineering teams prioritize a resolution.

We appreciate your patience and will continue monitoring this issue for any official fixes or guidance.

If my answer is useful for you, please vote for it.

Best regards,

Quinnie Quoc.

Answer 2

I can also confirm that there is a problem with this update, as well as with the KB5064081 update (which was released a few days earlier).

It disrupts some critical database access functions. Uninstalling this major update temporarily resolves the issue. See also the discussion on Reddit:

https://www.reddit.com/r/sysadmin/comments/1nhkr59/ucrtbasedll_crash_after_kb5064081_update_in_older/

Answer 3

YES, I can confirm this as well. Using Microsoft.ACE.OLEDB.12.0 instead of Microsoft.Jet.OLEDB.4.0 seems to work at a first view. In my case even Microsoft.Jet.OLEDB.4.0 worked as long as the SQL-SELECT was just on ONE Table. (SELECT * FROM MyTable) In case to extend the SELECT to have a INNER JOIN it crashed with Microsoft.Jet.OLEDB.4.0 and worked with Microsoft.ACE.OLEDB.12.0

Answer 4

是否会出补丁修复这个问题呢