Opening some reports in Access 2010 ADP crashes after KB5064081 (1 Viewer)

[rsocol]

Hello,

After installing the Windows updates published in 29 August 2025 or in 9 September 2025 (KB5064081 or KB5065426, maybe also others), Access 2010 crashes when opening some reports. More specifically, those reports are using a non-standard grouping interval (e.g. month or year) instead of "by entire value". In other words, there is a non-zero value for the GroupOn property of the GroupingLevel object.

In Event Viewer we can see the following details:
Faulting application name: MSACCESS.EXE, version: 14.0.7256.5000, time stamp: 0x5f125152
Faulting module name: msjtes40.dll, version: 10.0.26100.5074, time stamp: 0x5eef5084
Exception code: 0xc0000005
Fault offset: 0x0000f414
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE
Faulting module path: C:\Windows\System32\msjtes40.dll

This problem is somewhat similar to the one mentioned in by NikBab in another recent thread on this site. However, I was unable reproduce the problem with a supported version of Access, to report it to Microsoft.

Considering the crash is in MSJTES40.DLL (not in MSACCESS.EXE), I'm still hoping that Microsoft will see the crash reports in the telemetry and develop a fix at some point. Is there any hope for a such a fix in a reasonable timeframe? Or should I redesign those reports avoiding the non-standard grouping interval?

Thanks,
Razvan

 

[GPGeorge]

Given the fact that Access 2010 is long out of support, and that ADPs have been deprecated for a few years, and that the faulting dll is related to JET 4.0, which has been supplanted by ACE, I doubt there's a high likelihood of a fix.

 

[tvanstiphout]

There have been other reports in this forum about that DLL, such as this one so there is a chance the issue is more universal (read: more likely to get fixed) than that property in ADP reports.
I would start with rolling back the latest updates.
And long-term staying with technology that has been DEAD for more than a decade is not a good idea.

 

[rsocol]

It's strange that Microsoft recently updated MSJTES40.DLL, probably to fix a vulnerability, but without documenting that a vulnerability was fixed.

 

[tvanstiphout]

It's strange that Microsoft recently updated MSJTES40.DLL, probably to fix a vulnerability, but without documenting that a vulnerability was fixed.

You're right. I first thought "es" in the filename stood for "Espana", but it is "Expression Service". Mine is v6.2 from 2025-09-09. In an obscure folder is a v4.0 from 2024-04-01.
I think your chances for a fix just went up. If only we could make it crash with current A365.

I just tried, but it is not possible to set a Reference to JET Expression Service Type Library. "Error in loading DLL" will occur.

 

[isladogs]

You're right. I first thought "es" in the filename stood for "Espana", but it is "Expression Service". Mine is v6.2 from 2025-09-09. In an obscure folder is a v4.0 from 2024-04-01.
I think your chances for a fix just went up. If only we could make it crash with current A365.

I just tried, but it is not possible to set a Reference to JET Expression Service Type Library. "Error in loading DLL" will occur.

Following your prompt, I just successfully added the Jet Expression Service Type Library as a reference in 64-bit Access 365:

Perhaps it worked for me because in Win 10, I have an older version v4.00.9801.0 dated 07/12/2019.
There isn't a newer version of the file anywhere else on my system

 

[tvanstiphout]

Following your prompt, I just successfully added the Jet Expression Service Type Library as a reference in 64-bit Access 365:

View attachment 121480

Perhaps it worked for me because in Win 10, I have an older version v4.00.9801.0 dated 07/12/2019.
There isn't a newer version of the file anywhere else on my system

Very curious. DLLs in the SysWow64 folder are usually 32-bit (on 64-bit Windows).
I was using 32-bit Access for my test, and selected the one in SysWow64. Just for grins I also tried the one in the system32 folder (which should be 64-bit), and got "Can't add a reference to the specified file". I don't have 64-bit A365 handy here.