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
BilalDev_01's avatar
BilalDev_01
Tin Contributor
Sep 01, 2026

Hi,

Thanks for documenting the affected builds and the specific symptoms. Since the issues are reproducible on Access 2607/2608 and rolling back to 2606 (Build 16.0.20131.20154) resolves them, this certainly looks like a potential Office/Access build regression rather than an issue with the individual databases.

For affected customers, I would recommend:

  • Roll back to the known-working 2606 build as a temporary mitigation if the PDF output or application stability is business-critical.
  • If possible, test the same database on another machine running 2606 vs. 2607/2608. This can help confirm whether the behavior follows the Office build rather than the database.
  • For the PDF issue, test both Print to PDF and Access's Export → PDF/XPS functionality to determine whether the problem is specific to the Access PDF rendering/export engine.
  • For the crashes, check Event Viewer → Windows Logs → Application and collect the corresponding msaccess.exe crash information. The 0xc0000409 exception is useful diagnostic information to include in a Microsoft support case.
  • Make sure the affected Office installations are on the same update channel, since build availability can differ between channels.
  • If this is occurring across multiple customers and databases, I'd recommend opening/adding to a Microsoft support incident and providing a minimal reproducible database if possible.

The combination of PDF layout corruption, form rendering changes after Report Preview, and application crashes across multiple builds makes me hesitant to recommend database-level changes as the primary fix. If 2606 consistently resolves all three symptoms, staying on that build until a fixed Office build is available seems like the safest temporary approach.

It would also be useful to know whether these issues occur with a new blank Access database containing a simple report/form, or only with existing customer applications. That distinction could help isolate an Office rendering regression from something specific to the database objects.