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

Hi,

Microsoft has now released a fix for this in the Current Channel. Details can be found in our AFo article.

Please report if all issues, especially the crashes, are resolved for you.

Servus
Karl
****************
Access Forever, News, DevCon
Access-Entwickler-Konferenz AEK 10./11.10. Nürnberg

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.

Hi Karl,

I can confirm I had a serious problem with version 2608, build 16.0.20326.20112. The problems arose progressively (first I noticed restarts when closing Access apps) but last week things started to run amok.

I had a few light front-end db's - 5 forms, 10 linked tables to SQL server back-end, minimum code, working perfectly.

The one crashing randomly but systematically is a heavier front-end for asset management linked to access .accdb back-ends I did not transferred to SQL-Server yet. It opens normally, runs as long as you only make consults/data retrievals but crashes randomly when storing data. When I added some logging to a text file to pinpoint the problem I even noticed a crash in the middle of a single line write # statement.

Event viewer shows exceptions 0xc0000005 and 0xc0000028 in mostly VBE7.dll but also ntdll.dll and RPCRT4.dll.

Access references I use, library is a code library (.accda)
The only special reference is outlook redemption from dimaster.com, and Adobe Acrobat version 10 API, but ... during the crashes they where not accessed.

Addins are Git's joyfullserve Version control, and for vba: MZ tools and code vba.

I saved the event log with errors but don't know how to attach it to this message. If you need it or other info please let me know.I saved the event log with errors but don't know how to attach it to this message. If you need it or other info please let me know.
Reverting to version 2606 solved the issue.

Yes, Access builds 2607 and 2608 are confirmed unstable, causing both startup crashes and corrupted PDF exports. And believed the only way is to roll back to build 2606 for now. 

https://learn.microsoft.com/en-us/answers/questions/5981574/ms-access-printing-bug-after-17-08-2026-updates

https://learn.microsoft.com/en-us/answers/questions/5977884/version-2607-not-working-with-microsoft-access-to

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

I can confirm problems with multi page reports in Version 2607 (Build 16.0.20228.20190), Version 2608 (Build 16.0.20326.20072), and Version 2608 (Build 16.0.20326.20100) and problems with rendering of forms as mentioned above.

I can confirm Working version is version 2606 (Build 16.0.20131.20154), rolling back to this will resolve these issues. 

Everything said is true although many of my listboxes and comboboxes would randomly convert to a large and bolded font. Every computer with v2607 is showing the deleterious effects of the regression. Currently only fixed by downgrading to v2605.

I was unable to repro the crash using Build 16.0.20326.20100 (32-bit).
Can you please try to repro it with the Northwind 2.5 Dev edition, the Catalog report (under Reports). That one worked fine for me,