This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 92%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMH%3C/text%3E%3C/svg%3E)
Just 2 days ago, all my databases were running just fine, up til yesterday! I did a recent Microsoft365 update a couple of days ago. When I launch any of my databases, it runs slow, updates and refreshes very slow. I haven't dont any changes to these databases to cause this. I tried Compact and repair databases, changed the passwords via re-decrypting, etc. No luck at all. Any ideas?
A family of Microsoft relational database management systems designed for ease of use.
Microsoft® Access® for Microsoft 365 MSO (Version 2606 Build 16.0.20131.20012) 64-bit
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 10%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have had a similar issue.
I have a relatively small database, file size is 2.62MB and backend is Sharepoint. A dynamic search that filters based on keywords is now very slow compared to a few days ago. Used a backup version of the file and same issue.
Version 2606 (Build 20131.20044)
Hi,
What about updating to a newer build with the fix for this problem or changing to a production update channel, i.e. to a version/build that never had the problem - as I mentioned in several replies here?
Servus
Karl
Hi Karl,
Thanks for the suggestion, but when I try to update through Access, it says I am already up to date.
Hi,
when I try to update through Access, it says I am already up to date.
You didn't provide the information about your update channel with the methods discussed earlier in this thread, but I suppose that you are in the Current Channel. In this case:
We recently learned from Microsoft, that even the default Current Channel is "subject to experimentation", which means that a part of the systems in this channel get builds which are listed to be in the Preview Channel.
This explains why some people got the buggy build and can't update, as in their channel there's no newer build available. They can a) switch to a different channel or b) wait for a fixed build or better actively choose File - Account - Update Options - Update Now as often as possible to get a fixed build as soon as Microsoft has released it.
Servus
Karl
Yes, I am in Current Channel. I just checked and updated, and the problem is now resolved.
Hi,
A heads up for people who are on Current Channel Preview and have this problem:
You should now be able to use File - Account - Update Options - Update Now to pull Current Channel Preview version 2606 build 16.0.20131.20050 that contains a fix for this bug.
Edit 2026-06-18: Microsoft has changed the build number with the fix to 16.0.20131.20052
Servus
Karl
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 88%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJR%3C/text%3E%3C/svg%3E)
Hi,
I have the same problem and the same version: Microsoft® Access® per Microsoft 365 MSO (Versione 2606 Build 16.0.20131.20012) a 64 bit
But If I try to "update now" the answer is: "The system is apdated"
Why can't I update to the **build 16.0.20131.20050 ?
**Jacopo
Hi,
Microsoft® Access® per Microsoft 365 MSO (Versione 2606 Build 16.0.20131.20012) a 64 bit
This looks like you took it from the "About Access" screen. This screen doesn't always show your current version of Office/Access. The real version+build you have, is what you see on the right side of the File - Account screen, or what you get when you press Ctrl+G in Access and paste this in the Immediate Window of the VBA editor, followed by Enter:
?SysCmd(acSysCmdGetFullVersion)
If you copy the result of this in your next reply, we can see the build number and update channel.
Sometimes there are problems with pulling the latest update where complex workaroundsmight help. However, if you are in the Current Channel Preview, then the first question is, if you really want/need to be in that test channel. If not, you should switch to the Current Channel, which is meant for production use and doesn't have the bug we discuss here.
Servus
Karl
From VBA: ?SysCmd(acSysCmdGetFullVersion) => Microsoft Access (Version 2606) Build 16.0.20131.20044 Canale corrente 64-bit
but Access is still slow
I have a Microsoft 365 Family, so it's possibile that I can't choose the channel?
Thank you for your help
Jacopo
Hi,
Your build number and the channel info don't fit together. This build is from June 12 in the Current Channel Preview (CCP, Canale Corrente Anteprima), NOT in the Current Channel (CC, Canale Corrente) and contains the bug.
In the CCP build list you can see that there are 2 newer builds (which contain the fix). If you are not able to pull one of these newer builds, because you are told to be "up-to-date", then it's probably one of the not so unusual errors/mixups that happen in the channel organisation of M365.
I have a Microsoft 365 Family, so it's possibile that I can't choose the channel?
On the right side of the File - Account screen, do you see "Microsoft 365 Insider" as the second button? It should look like the picture in item 1. of our channel article. However, I'm not sure if you can leave the Insider (=tester) program with this button and change to the Current Channel.
Servus
Karl
Hi,
I don't have the 2nd button. I'm NOT in the Microsoft 365 Insider.
And, as you wrote, I can't pull the newest build because the system is "up-to-date".
Maybe if I agree with the Insider program I will have the two newer build?
Thank for your help,
Jacopo
Hi,
If you have the family version you should have a button under File - Account that allows you to join the Microsoft 365 Insider program, which allows you to get the fix that has been made available in Current Channel Preview. For further details see https://www.accessforever.org/post/demystifying-microsoft-365-update-channels point 1.
If you do NOT see the button, check the same link, point 2.
Peter
Hi,
Microsoft® Access® for Microsoft 365 MSO (Version 2606 Build 16.0.20131.20012) 64-bit
Yes, this build in Current Channel Preview is affected by the problem I mentioned.
Maybe perhaps I should remove this latesy update. The Date of this latest update shows June 9th.
You have 3 options:
Servus
Karl
Access Forever, News, DevCon
Access-Entwickler-Konferenz AEK
Managed to revert to Version 2605 Build 20026.20168 following your suggestions. I also disabled Microsoft Insider Preview, so the I only download production products in the future. This fixed the problem. Thank you so much. Now my databases are running at fast normal speed. Again, thank you for your help.
Hi,
You should always mention which update channel, version and build number of Office/Access you are using. You can see this information on the right side of the File - Account screen or you can press Ctrl+G in Access and paste this in the Immediate Window of the VBA editor, followed by Enter:
?SysCmd(acSysCmdGetFullVersion)
Currently there is a known problem with this kind of effect on forms. It affects version 2606 build 20131.20012 and 20024 in the Current Channel Preview. If you have one of these builds then 1) be aware that this update channel is for testing purposes and b) Microsoft's Access team will fix the problem before version 2606 arrives in the Current Channel, i.e. for production use.
Servus
Karl
Maybe perhaps I should remove this latesy update. The Date of this latest update shows June 9th.