Blog Post

Access Blog
2 MIN READ

Fixes in Microsoft Access - Version 2610 (Build 16.0.20527.20088)

Shane Groff's avatar
Shane Groff
Icon for Microsoft rankMicrosoft
Oct 23, 2026

Here's a summary of the issues fixed in Version 2610 of Access, including improvements to Zoom, Big Forms, forms and controls, and stability.

 

Known issue in the initial Version 2610 release

Some databases may display an incorrect "There isn't enough memory or disk space" message when opening a report or exporting a report to PDF. A correction is planned for the next Version 2610 update.

UPDATE: This issue is now fixed in build 16.0.20527.20112. Use 'Update Now' to update to the new build.

Zoom

IssueFix
Datasheet subforms did not zoom with Ctrl+mouse wheelUsing Ctrl+mouse wheel over a subform displayed in Datasheet View now changes its zoom level as expected.
Context menus appeared in the wrong location on zoomed formsRight-click menus now open at the selected location regardless of the form's zoom level, including near the lower-right edge of the form.
A form divider line could stop halfway across at 50% zoomThe divider between form sections now spans the full form width at 50% zoom and other supported zoom levels.
Rapid Ctrl+mouse-wheel input could jump from 10% to 1000% zoomZooming out quickly now stops at the 10% minimum instead of wrapping to the maximum zoom level.

Big Forms

IssueFix
Horizontal scrolling could snap very wide forms back to the leftDesign View and Form View can now scroll to controls positioned far to the right without the form unexpectedly returning to its left edge.
Text formatting remained limited to 22 inches in wider controlsText can now be formatted and displayed across the full width of fixed-size text controls wider than the former 22-inch form limit.

Forms and controls

IssueFix
ControlTip text could remain visible after typing beganControlTips now close when keyboard input begins, preventing the tip from covering the form during data entry.
Property Sheet text could become unreadable after changing the Office themeThe Property Sheet now refreshes both its foreground and background colors immediately after a theme change, without requiring Access to be restarted.

Queries and data

IssueFix
Bracketed object and control names could occasionally be read incorrectlyAccess now reliably preserves a name when removing its surrounding brackets.

Stability

IssueFix
Opening forms with grouped control layouts could cause Access to close unexpectedlyAccess no longer closes unexpectedly while determining the bounds of grouped layouts when affected forms open in Form View.
Changing a subform's SourceObject could cause Access to close unexpectedlyChanging a subform's source from VBA during an event now completes without causing Access to close unexpectedly.
Updated Oct 29, 2026
Version 4.0
access
office 365

5 Comments

  • MikeTyrrell's avatar
    MikeTyrrell
    Copper Contributor
    Nov 05, 2026

    We're seeing repeated Access crashes on Version 2610 at several of our customers, on both 16.0.20527.20088 and 16.0.20527.20112 (64-bit, Microsoft 365 Apps, Current Channel).

     

    Symptom: Access closes when a form opens. Our application is a large VBA accdb started with /runtime. The Windows Application log shows Event 1000 for MSACCESS.EXE, exception c0000005, with the faulting module either VBE7.DLL or "unknown". At two separate customers, the VBE7.DLL crashes are at the same offset, 0xf0b38. One site logged about 140 crashes in a week.

     

    What the full dumps show: a DEP fault (execution of a non-executable address). The address comes from a VBE7!EVENT_SINK vtable slot and points to a VBE7-generated stub in PAGE_READWRITE memory, while a sibling stub on the same stack is PAGE_EXECUTE_READWRITE. Our code isn't on the stack. MSACCESS, mso and ACECORE are dated 2026-10-20 in the dumps, and VBE7 is 7.1.11.58.

     

    Timeline: at one site, the crashes started 2 minutes after Office updated to 2610. Rolling back to 16.0.20430.20182 (2609) and pausing updates has stopped the crashes. The same application runs without problems on 2609.

     

    I've also logged this on the Feedback Portal: https://feedbackportal.microsoft.com/feedback/idea/7f3db0ea-5dd4-f111-aad1-7c1e528b5f2c

     

    We have full MSACCESS.EXE dumps and can share them through a secure channel. Is this a known issue, and is a fix planned for a 2610 or 2611 build?

    • Shane Groff's avatar
      Shane Groff
      Icon for Microsoft rankMicrosoft
      Nov 05, 2026

      Hello Mike,

      Thank you for the detailed report. Can you please try updating to Version 2610 build 16.0.20527.20150. The issue you are reporting should be resolved in that build. If you are still seeing any problems, we can follow up with your crash dumps.

      Shane

       

      • MikeTyrrell's avatar
        MikeTyrrell
        Copper Contributor
        Nov 09, 2026

        Thanks Shane,

        I looks like 16.0.20527.20150 has fixed the crashing issue after getting some early reports back from the customers.

  • Shane Groff's avatar
    Shane Groff
    Icon for Microsoft rankMicrosoft
    Oct 28, 2026

    This issue is now fixed in build 16.0.2052.20112. Use 'Update Now' to update to the new build.

  • andybentley52's avatar
    andybentley52
    Copper Contributor
    Oct 27, 2026

    Incredibly annoying that this latest version has re-introduced the 2004 bug that was fixed at the beginning of the month!
    Whatever happened to quality control?