KB4566782 / KB4565351 breaks MDB file access (Access 2003 / Jet Database Engine)

Copper Contributor

 

After the latest round of Windows updates MDB files can no longer be opened in Access 2003, and trying to open them via Jet gives a 3049 error.

 

Is this accidental, or have Microsoft ended support for MDB?

6 Replies

Hello @davidgmjacobson,

 

I couldn't locate this as known issue with updates you mentioned.

 

Can you try restoring your system before the update was installed. Or try uninstalling the updates and check if issue is resolved with that.

 

Regards.

Hi @Kapil Arya 

 

Uninstalling the update (and pausing updates, so that Windows doesn't immediately reinstall it) resolves the issue, but is not a permanent solution.

 

This may not be a known issue within Microsoft, but I not the only one experiencing this problem:

 

https://www.devhut.net/2020/08/17/access-bug-mdb-jet-broken-by-latest-round-of-updates/

https://www.windowslatest.com/2020/08/14/windows-10-kb4565351-kb4566782-installation-issues/ (see comment by Marty)

https://techcommunity.microsoft.com/t5/access/problem-with-the-msjet40-dll-released-with-the-windows...

 

Thanks for you help,

David

We experienced the same problem, one of PC uninstatll KB4565351, the problem solved!

However, anthoer pc cannot uninstall KB4565351, the uninstall option is hide or disable by the OS!!  MS seem make thing worse after update! Happened many time! Never tested the update fully!!

Hi @Kapil Arya,

 

Uninstalling the update restores functionality. I had to pause updates, though, as Windows immediately reinstalls the update otherwise.

 

I'm not the only one with this issue. See:

 

https://www.devhut.net/2020/08/17/access-bug-mdb-jet-broken-by-latest-round-of-updates/

 

https://techcommunity.microsoft.com/t5/access/problem-with-the-msjet40-dll-released-with-the-windows...

 

Marty's comment in https://www.windowslatest.com/2020/08/14/windows-10-kb4565351-kb4566782-installation-issues/

 

Keep well,

David

 

Hi @Kapil Arya ,

 

This is the third time I tried replying. The other two replies posted without a problem, but didn't appear in the thread; perhaps this is because they contained URLs, so I'll leave them out. Suffice it to say that there are other sites on which this bug has been reported.

 

Uninstalling the update did resolve the issue (though I had to pause updates to stop Windows immediately reinstalling it). Needless to say, this isn't a good permanent solution.

 

Keep well,

David

Okay @davidgmjacobson,

I do recommend you to report this via Feedback hub app, so it gets addressed in upcoming updates.

 

Regards.