Forum Discussion

hlau_msd's avatar
hlau_msd
Tin Contributor
Aug 20, 2026

Print to PDF and crashing issue - Access Version 2607 and 2608

Multiple customers are reporting crashing and print to pdf issues after updateing to Access version 2607 and 2608.    Versions with the issue: Version 2607 (Build 16.0.20228.20190), Version 2608 (...
access
Good_SC's avatar
Good_SC
Tin Contributor
Aug 24, 2026

I raised this with MS last week. For us only rolling back to 2604 resolves it. 

I’ve tried every build after it (2605/2606/2607/2608) and it has the same issue. 
also tried changing default printer to adobe pdf/microsoft print to pdf

  • Karl_Donaubauer's avatar
    Karl_Donaubauer
    MVP
    Aug 26, 2026

    Hi,

    We are collecting further information for our bug documenting AFo article and for discussions with the Microsoft Access team.

    Today I updated the article with new information from Microsoft. Since crashes have been reported here, I'd like to point out that the Access engineering team is requesting reproduction files for crashes. This could help speed up things. If anyone here is able to provide such a file or repro information, please read the details in the Status section of our article.

    Servus
    Karl
    ****************
    Access Forever News DevCon
    Access-Entwickler-Konferenz AEK

  • Good_SC's avatar
    Good_SC
    Tin Contributor
    Aug 25, 2026

    Hi  Karl,

    1. It's crashing during batch print>pdf  jobs
    2. The 2606 build i tried was 16.0.20131.20206 ( montly enterprise)

    Faulting application name: MSACCESS.EXE, version: 16.0.20131.20206, time stamp: 0x6a76673a
    Faulting module name: MSACCESS.EXE, version: 16.0.20131.20206, time stamp: 0x6a76673a
    Exception code: 0xc0000005
    Fault offset: 0x00000000000377e4
    Faulting process id: 0x9AC
    Faulting application start time: 0x1DD3161FC9A5D26
    Faulting application path: C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE
    Faulting module path: C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE
    Report Id: e97f9168-3292-443e-862e-25d2037137fd
    Faulting package full name:
    Faulting package-relative application ID: 
    • Karl_Donaubauer's avatar
      Karl_Donaubauer
      MVP
      Aug 25, 2026

      Hi,

      Thanks for the details! Yes, the Monthly Enterprise Channel (MEC) builds are different again.

      I asked specifically about the last Current Channel (CC) 2606 build 20131.20154, because that one should not contain a change that is a potential culprit. 20131.20206 in MEC came later and probably already has it.

      Servus
      Karl
      ****************
      Access Forever News DevCon
      Access-Entwickler-Konferenz AEK

      • Good_SC's avatar
        Good_SC
        Tin Contributor
        Aug 25, 2026

        Hi Kar,

        I just switched to Current channel 16.0.20131.20154, and can confirm that does seem to fix the issue printing>pdf.

        So It's only working on Enterprise Channel 2604 or Current channel 2606 (16.0.20131.20154)