Blog Post

Access Blog
3 MIN READ

Bug fixes in Microsoft Access - Version 2606 (Build 16.0.20131)

lindalu-MSFT's avatar
lindalu-MSFT
Icon for Microsoft rankMicrosoft
Jun 16, 2026

Here's a summary of bug fixes available in the latest Current Channel build of Access:

 

 

Bug Name

Issue Fixed

German keyboard: AltGr key combinations triggered zoom shortcuts instead of typing characters

On German and other keyboard layouts that use AltGr for common characters (such as ~, }, and others), pressing AltGr+key combinations triggered the zoom keyboard shortcuts instead of inserting the expected character. These keyboard layouts now correctly distinguish AltGr from Ctrl+Alt so that character input works as expected.

Zoom was disabled for all ACCDE and MDE files

The new zoom feature was incorrectly disabled for ACCDE and MDE files. Zoom now works correctly in these file types.

Default zoom value in Access Options validated per-keystroke

When entering a custom default zoom percentage in the Access Options dialog, the field validated the value after every keystroke, which blocked multi-digit entry (e.g., typing "15" triggered a validation error after "1"). The field now validates on commit rather than per-keystroke.

Display issues when extending laptop to a large external monitor

When a laptop was extended to a larger external monitor, certain controls such as checkboxes and option buttons did not zoom correctly. These controls now scale properly when the form is displayed on a monitor with different DPI or resolution than the primary display.

Date selector control showed truncation and ghosting at certain zoom levels

At certain zoom levels, the date selector control displayed truncated text and visual ghosting artifacts. The date selector now renders cleanly at all zoom levels.

Screen reader did not announce zoom level changes via keyboard shortcuts

When using keyboard shortcuts (Ctrl+Alt+Plus / Ctrl+Alt+Minus) to adjust the zoom level, screen readers did not announce the updated zoom percentage. The zoom control now exposes the updated value to assistive technology after each change.

Screen reader announced incorrect context for zoom controls

When navigating to the zoom split button on the Home tab, screen readers announced it as "Print Preview Zoom" instead of reflecting the current zoom context. The control now announces the correct context.

Zoom button on Home tab did not respond to keyboard activation

The Zoom button on the Home tab did not perform any action when activated via Enter, Spacebar, or mouse click. The button now opens the zoom dropdown as expected.

Added 125% and 175% zoom levels to the ribbon

The zoom dropdown on the Home tab now includes 125% and 175% as preset zoom levels, making it easier to select commonly used zoom percentages without typing a custom value.

Tab header font rendered incorrectly when zoomed

When zooming was enabled, tab control headers could render with an incorrect font size or style. Tab headers now render with the correct font at all zoom levels.

Dropdown list detached from its control when form was scrolled

When a form was scrolled while a dropdown list was open, the dropdown could become visually detached from its parent control and appear at the wrong position on screen. The dropdown now repositions correctly when the form scrolls.

Query with IS NULL predicate could return incorrect data

When a query used an IS NULL predicate on certain field types, the query could return incorrect results or trigger an internal error. The query engine now evaluates IS NULL predicates correctly in all cases.

Linked Table Manager showed a confusing dialog when re-linking tables

When using the Linked Table Manager to re-link tables, a confusing dialog appeared asking if you wanted to use new names from the source for the linked tables. If you choose a new source, we now skip the dialog, and use the existing table names from the remote source.

Reduced unnecessary repainting during horizontal scroll in Form view

When scrolling horizontally in Form view, Access was repainting the entire form window instead of just the newly visible area. This caused visible flicker and unnecessary CPU usage. Horizontal scrolling now repaints only the region that has changed.

 

Updated Jun 26, 2026
Version 3.0

19 Comments

  • JonGeo's avatar
    JonGeo
    Copper Contributor

    Hi Microsoft,

    We have also experienced out MS Access charts rendering have broken across multiple Windows11 AVD.

    Affected build: 16.0.20131.20152

    Working build: 16.0.20026.20236

    Rolled back to known-good build restored charts

     

  • JonGeo's avatar
    JonGeo
    Copper Contributor

    Hi Microsoft,

    We have also experienced our MS Access chart rendering has broken across multiple AVD (win 11 VMs).

    Seemed to have occur after the "Zoom update" implemented that has caused this issue.

    Workaround - roll back to 16.0.20026.20236 until fix has 

    • Faulty build: 16.0.20131.20152
    • Known-good build: 16.0.20026.20236
    • Rolling back to the known-good build restored the charts.

      Problem screenshot - post update chart render broken!

       

    • Roll back working chart renders
    •  

  • Forester's avatar
    Forester
    Copper Contributor

    I have noticed two additional issues:

    Combo box in a subdatasheet:

    - If a form in Datasheet View contains a child subdatasheet with a Combo Box control, selecting a value in the combo box for a new record leaves the combo box empty, and the drop-down list disappears. In this scenario, the only event that fires is the control's On Dirty event.

    - Text Box "Enter Key Behavior":

    If the subdatasheet described above is created by dragging a table onto the parent form in Design View, the Enter Key Behavior property of the Text Box control is set by default to "New Line in Field" instead of "Default". As a result, pressing Enter causes just typed text to disappear, since a new line is inserted within the field instead of moving to the next control or record.

     

    Both issues are resolved after rolling back to the previous version 20026.

  • OL123456's avatar
    OL123456
    Copper Contributor

    Big problem with resize of various forms after Update.
    Seems changes also in event sequence, so subform not accessible at point in open sequece as before.
    Seeme we need to inform all our customers world wide not to do this update.
    On form open you can now see subforn, pictuer first in small size, then after a few seconds adjusting.to normal size.
    Hourglas stand longer than before.
    Big problem for our application

    • George_Hepworth's avatar
      George_Hepworth
      Silver Contributor

      Please provide details, and if possible, supply an accdb demonstrating the problems.

      You have responded to a blog regarding Version 2606 (Build 16.0.20131).  Please confirm that is the build which displays this reported problem in your environment. 

      Please describe the runtime environment for your users as well. e.g. are they running the full Access application or the runtime with your database application.

      Thank you.

       

      • OL123456's avatar
        OL123456
        Copper Contributor

        Hello George_Hepworth,
        meanwhile I did some investigation and found the cause is the combination of this office 2606 version and the HP with AMD processor.
        Before Office Update behaviour was normal.
        I could compare to an older surface. Using the same accde file from repository on both computers (both with full version started with /runtime). On surface behaviour is as usual.
        I made short videos and embeded them into a power point with comments.
        Error happens, when "Me.painting = false". Seems on the AMD at that point the subform isn't available. However on the surface it is. Code section is over a long time as it is. Version of accde is from February 2026.
        Very starnge.
        Hope you can watch the pptx. It is in a public folder on our web-site

        https://www.pro-plantool.de/videos/Office_2606_AMD_problem.pptx

        AMD unexpected sizes

        suface usual sizes

         

  • aeddon's avatar
    aeddon
    Copper Contributor

    Hey there,

    We are experiencing the same major slowdown of our Access databases. 

    Continuous forms appear to be the main culprit. We are experiencing a roughly ~6-10 second delay upon opening, and they appear to be repainting themselves several times over before finally settling. Other forms suffer a similar startup delay, but function with negligible performance loss after loading. 

    Waiting to revert back to the previous version to confirm on our end.

    • aeddon's avatar
      aeddon
      Copper Contributor

      Can confirm after reverting back versions the slowdown is resolved!

      • brepp's avatar
        brepp
        Copper Contributor

        Good to hear.  I wonder what the mechanism is to report the bug to MS.  Last time they broke Access for my clients was 2022 so that's pretty ok.  Still stressful though.

  • brepp's avatar
    brepp
    Copper Contributor

    I'm tracing a slow down of an Access to SQL Server app that just started with Version 2606.  Build 20131.20044.  Has anyone else encountered this?  It is a pretty hefty app but slowdown is just starting to show up on certain pcs.

    • George_Hepworth's avatar
      George_Hepworth
      Silver Contributor

      What channel are your users on?  All on Current Channel? Any on Current Channel Preview Version or Beta where this problem has been reported?

      Does your IT manage Office Updates?  Can you force updates on any PCS with CCP Preview? 


      As I understand it, build  20131.20052  in the Current Channel Preview should have the fix, or will  have it soon.

      • brepp's avatar
        brepp
        Copper Contributor

        Reverting to a prior version solved the issue.  This confirms an MS bug with the Version 2606 Build 20131.20044.