Visual Glitches and Format Problems (Fixed)
Updated: 9 hours ago
Description
In version 2607 and later there are different types of visual and formatting errors mainly with reports, but also in forms:
Labels, button captions etc. and even the text in the property pane "randomly" are displayed with white backgrounds and big, old fonts
Lines in reports get printed in a wrong size or position
Some report pages are printed in a fraction of the correct size
Report margins are changed, which alters the page layout or can cut off text
The Access crashes mentioned in forum posts and comments here are a separate issue
Some of many forum threads:
August 2026 RDP font display glitch TechCommunity
Darstellungs-Bug seit 20228.20188 donkarl forum (German)
Cause
The culprit for the display/print errors is an Office-wide security update.
Status
Microsoft has released fixes with version 2608 build 20326.20132 in the Current Channel on Sep 1. In the Monthly Enterprise Channel (for versions 2608 and 2607) the fixes are in the builds from Sep 8.
The fixes should resolve both issues, the display errors and the crashes. Please let us know if there are still any unresolved cases.
The culprit security updates were distributed not only to Office 365 but also to all other supported versions of Office/Access (2024, 2021). In addition, Office 2019 and even 2016 MSI, which are no longer supported, were blessed with them. We don't have any information about planned fixes for the older versions.
An indication of a workaround for Access 2016 MSI comes from poster Andreas Summer:
The following updates must be uninstalled: KB5002813, KB5002912 Then the problem will be resolved in Access 2016 as well.
As always, when uninstalling security updates, you do so at your own risk.
Workaround 1
According to many reports and our tests, rolling back to Current Channel version 2606 build 16.0.20131.20154 resolves the problems.
If you are on the Monthly Enterprise Channel: some posters report that they had to roll-back to version 2605 or 2604 to get rid of the problems, especially crashes.
Workaround 2 (from the Microsoft Access engineering team)
The issue is triggered by printing or previewing a report that renders an Image control or a bound/unbound Object Frame (OLE object), including controls inside subreports. If feasible, temporarily removing or hiding those controls from affected reports may be the quickest mitigation. Restarting Access clears the corrupted display state, but it may recur after printing or previewing.
Microsoft® Access® LTSC MSO (16.0.14334.20848) 64-Bit has this problem as well.
Perhaps good news - we got version 2608 Build 16.0.20326.20132 delivered this morning and at first sight it appears to have solved our issues. We are a bit confused about the numbering, as the beta is at version 2609 Build 16.0.20425.20000 but keeps crashing like before.
Exactly same problem here, I have a few front-end MS Access apps with SQL server back-end without problem but the single big front end still using access db's as back-end (busy rewriting for sql-server) keeps crashing randomly but systematically on vbe7.dll, kernelbase.dll and ntdll.dll errors 0xc0000005 or 0xc0000028.
Rollback to Version 2607 (Build 20228.20124) solved the problem. We had issues with reports longer than 1 page. 2nd and further pages were miniatures only.
Oh what a week it's been! We've been fielding calls as these updates get rolled out. Last week it was the line rendering issue which seemed to be with version 2608 before it should have officially rolled out to Current Channel. This week with the "official" 2608 rollout we've had calls primarily related to Access crashes. We've been rolling back to Version 2607 (Build 16.0.20228.20124) to resolve it AND turning off updates so it doesn't continue to unfix itself. We have applications in over 60 counties in Arkansas, so I'm just waiting for the next call.