Forum Discussion

hlau's avatar
hlau
Copper Contributor
Oct 15, 2026
Solved

Crashing Issue - Access Version 2610 (Build 20527.20054)

We have multiple customers reporting crashing issue when navigating tab control with Access Version 2610 (Build 20527.20054). For now we have customer rolling back their Office to version 2609. 
access
  • George_Hepworth's avatar
    George_Hepworth
    Oct 15, 2026

    I believe that is the Current Channel (Preview), correct?

     If so, you should advise your customers that running a production application in the Preview channel means they are more exposed to bugs. It's probably out of your control, but advising them would still be a good idea. 

     

    If you can provide a database that displays this behavior, that would be helpful in reporting it to Microsoft. Thanks.

     

     

George_Hepworth's avatar
George_Hepworth
Silver Contributor
Oct 15, 2026

I believe that is the Current Channel (Preview), correct?

 If so, you should advise your customers that running a production application in the Preview channel means they are more exposed to bugs. It's probably out of your control, but advising them would still be a good idea. 

 

If you can provide a database that displays this behavior, that would be helpful in reporting it to Microsoft. Thanks.

 

 

  • hlau_msd's avatar
    hlau_msd
    Tin Contributor
    Oct 16, 2026

    According to some customers, they never signed up for the preview channel but was some how updated to this version. I can't provide the database that can reproduce this issue, but here is the ProcDump file. 

    https://www.dropbox.com/scl/fi/6x1xseiiyx0xg05sa77du/MSACCESS.EXE_261014_154744.zip?rlkey=ys9w1mp0tz04qgykmf27d0tcd&st=pyhm9kls&dl=0

    • George_Hepworth's avatar
      George_Hepworth
      Silver Contributor
      Oct 16, 2026

      I can only repeat what I found on the update pages.  Access Version 2610 (Build 20527.20054) is a preview channel. How your customers ended up on that channel, only they would know. It's never wise to run production software in a preview environment. The whole point of preview is to give developers, like you, a chance to try things out before it gets to the production user. In other words, you should have a machine on a preview channel for testing before releasing anything to your customers. That can help minimize problems like this one from reaching them, or at least give them a heads up.

       

      You also probably should suggest all of your customer switch to a slower channel, one intended for production deployments.

      Demystifying Microsoft 365 update channels

      I'll pass this along to Microsoft.