Windows 11 Slowing Down Database

[CJ_London]

If that was for me, yes definitely a split as I would always do,

so it's not split and all users are opening the file on the server - that way lies corruption.

 

[MagicIT]

In addition to the comments above regarding BIT Locker and Antivirus, there is another overlooked area within access itself that affects performance. If you have compression enabled, that could also lead to performance issues.

As for anti-virus, a lot of System Admins like to blame software for their weaknesses, and a lot them are highly prejudicial on Office Products, especially Access. They will implement Anti-virus and harden it to the point where applications just stop functioning or become terribly slow. Access itself is not the culprit. A trusted application should be placed in a trusted location where there is no pro-active defense. I personally do not run any 3rd party anti-virus software. I rely entirely on built-in windows security. I have had nothing but bad experiences with all the popular 3rd anti-virus software, mainly regarding performance of office products.

Also, if you are running any Emulator Software, make sure your Office components have been updated. Older Emulators like to install office core dll's in the older folder structures. The problem is this cause ambiguity when certain functions are called.

I am not sure why or how upgrading from Windows 10 to 11 would affect this, but it is worth looking into. Make sure the "Name AutoCorrect Options" are disabled in your production application. Thise feature is enabled by default in new Access Databases. This feature tracks name changes to objects and can track in run mode if enabled.

View attachment 119834

No compression that I have found anywhere as yet and all the usual performance issues are already covered including autocorrect, trusted locations, subform datasheets, export and import of all objects, decompile/recompile, persistent BE, indexes etc. For AV, I can only go on what their support provider told me that they had excluded what I told them to for both realtime and scheduled scans, but I might have more on that soon as another provider has been brought in, given how useless and awkward their incumbent one is.

Also suggested getting their cabling infrastructure actually tested given they had some fluctuation and improvement whilst some PCs were moved out of the way for decorating (not unusual to have a good few days though anyway) and some has been added later on. Also want to ensure all the PCs are up to date on NIC firmwares etc.

 

[MagicIT]

so it's not split and all users are opening the file on the server - that way lies corruption.

Sorry, but that's not what I said. I said it IS split. Back end files are on the server and each workstation with its own front end locally on the C: drive just as I would always do.

 

[spaLOGICng]

No compression that I have found anywhere as yet and all the usual performance issues are already covered including autocorrect, trusted locations, subform datasheets, export and import of all objects, decompile/recompile, persistent BE, indexes etc. For AV, I can only go on what their support provider told me that they had excluded what I told them to for both realtime and scheduled scans, but I might have more on that soon as another provider has been brought in, given how useless and awkward their incumbent one is.

Also suggested getting their cabling infrastructure actually tested given they had some fluctuation and improvement whilst some PCs were moved out of the way for decorating (not unusual to have a good few days though anyway) and some has been added later on. Also want to ensure all the PCs are up to date on NIC firmwares etc.

We are reading reports that there was an issue with a recent update to MS Office and specifically Access that are wrecking havoc.

Here is a list of issues. I have had clients reports similar issues but with Access.

I suggest performing an "Online Repair" of your Office Installation.

 

[gemma-the-husky]

I would add code that tests and reports on whatever mechanism you use to maintain a persistent connection to the database.

I add a button to the dashboard to check the position. ie, that the object I use is not nothing.

 

[Shimon]

I am experiencing a very similar result, using Win11 and Office 2021.
I looked through the list that @spaLOGICng noted, but found nothing that describes what we are talking about. Everything seems to work fine, but the response is slow and we have a notice "qureying the .. " or something like it.

 

[mike60smart]

Can you upload a copy of the database so we can test to see if we get the same response.

 

[Shimon]

There are probably legal limitations on sharing the DB. If I don’t find a simple solution, I’ll try to strip the personal data and upload it.

 

[spaLOGICng]

There are probably legal limitations on sharing the DB. If I don’t find a simple solution, I’ll try to strip the personal data and upload it.

Application, both BE and FE are important. I keep everything out of any Folder that is in the Search locations for the User. For instance, the Documents and Desktop Folders are big no-no's. For BE's, I always place them in a local drive folder on a dedicated box at least one that is accessible by everyone in the network with the least amount of traffic.

I never use Mapped Drives. I prefer UNC method over Mapped Drives as they resolve faster if connection fails.

I always turn off Folder/File Indexing. I do not like Windows search anyway. I use AgentRansack for all my file searching needs.

I most cases I will not place the FE on the Desktop unless a client requests it and declines my suggestion. I will typically place the FE in a Folder on the local drive that is not part of the System or User.

I will trust the folder location and exclude that path from any proactive anti-virus to prevent it from being scanned.

In addition to turning off the AutoName Tracking Feature in Access > File > Options > Current Database... I will also turn off "Enable Layout View. Layout View is for Designers. Do not need that in a Runtime or Production Version. Also turn off Enable Design Changes for Tables in Datasheet View. Another one is discretionary, but I recommend using the "preserver source..." for images rather than "Convert all picture data to bitmap...". Bitmap images are huge.

A few more performance tips:
1) Never use a Tables Name or a SELECT Statement as the Record Source to a Form or Report or the Row Source to a Combo or List Box. Always use a Query. Queries are precompiled and do not need to be compiled when the Form opens.
2) For Queries that are the Row Source to a Combo or List Box, always make sure the Query only has the specific Fields that are needed. Also, be sure to set the Recordset Type to Snapshot. Access will render all Dynaset Queries as Updateable by default. Do not need this on a Lookup or Enumeration Query.
3) Make sure Columns are properly indexed.


To be honest, I always recommend SQL Server Express for hosting Data at minimum. A Database in SQL Server Express can be up to 10 GB which can cover most small and mid-size businesses. With SQL Server Express 2025 that changes, it is increased to 50 GB, plus some other added features, like Reporting Services and Full Text Search. In most cases you can solve all of your speed issues with Express.

To best migrate data to SQL Server, I use the SQL Server Migration Assistant for Access (SSMA). It will migrate everything. If you do, a tip from experience, make sure you set your data type conversion defaults correctly. It will set them up default, but it will convert Access Date/Time to SQL Server Datetime2 which will be problematic in Access. I always set the conversion to DATATIME and never DATE.

You will experience other performance issues with SQL Server from Access FE. If you run a lot of Action Type queries, it may be best to convert them to Stored Procedures and execute them through DAO, ADO, or Passthrough Queries.

Lastly, think minimalistic.
1) Use as little VBA as possible. but make any VBA as reusable as possible.
2) Make Queries as reusable as possible. Only use the Fields that are needed in a Query. It is okay to create a second query of other fields are needed for other forms and reports, just be proactive about this
3) Make Forms as reusable possible.
4) Use the Navigation Control instead of the Tab Control.

The big elephant in the room now after resolving all of that will be related to COPILOT or any AI Feature. I would disable all at the local level.

 

[The_Doc_Man]

I never use Mapped Drives. I prefer UNC method over Mapped Drives as they resolve faster if connection fails.

When I started working with Access for the Navy and had a BE file to share, I ALWAYS used Mapped Drives - until the day that one of my new users had 26 drive letters mapped to her PC already - and ALL of them were legit. Some were empty USB slots or the default floppy drive letters or "included" CD drives, all of them automatic boot-time drive letter assignments. Our Navy-provided machines had TWO hard drives because we were not allowed to install stuff under C:\ for security/anti-virus reasons. After this lady came along, my next version of the "big" app had been switched to UNC mapping and I never went back.

 

[Gasman]

There are probably legal limitations on sharing the DB. If I don’t find a simple solution, I’ll try to strip the personal data and upload it.

Use this on a *copy* of your DB.

 

[spaLOGICng]

When I started working with Access for the Navy and had a BE file to share, I ALWAYS used Mapped Drives - until the day that one of my new users had 26 drive letters mapped to her PC already - and ALL of them were legit. Some were empty USB slots or the default floppy drive letters or "included" CD drives, all of them automatic boot-time drive letter assignments. Our Navy-provided machines had TWO hard drives because we were not allowed to install stuff under C:\ for security/anti-virus reasons. After this lady came along, my next version of the "big" app had been switched to UNC mapping and I never went back.

Good stuff there... thanks for sharing!

 

[spaLOGICng]

My Copilot returned this for me today in addition to the other factors mentioned here as it relates to Windows 11

I have not had an issue with the clipboard. Of course, running a Windows 11 PC with 32 GB Ram and a 12th Gen Intel(R) Core(TM) i7-12700 (2.10 GHz) processor on 1TB SSD probably does not flinch. My cheap HP laptop chokes though, which I intentionally have for testing with my low budget clients, so I will test this on that machine.

​

1. Windows 11 24H2 Has a Confirmed Access Performance Bug​

Multiple reports show that Access becomes dramatically slower on Windows 11 24H2, especially compared to 23H2 or Windows 10.
Issues include slow form rendering, slow queries, and UI lag.

• Clients on 23H2 do NOT have the slowness, confirming it’s specific to 24H2.
• Forms load slowly “top-to-bottom” after upgrading to 24H2. [accessexperts.com] [learn.microsoft.com]

✔ Workaround​

Disable Suggested Actions (Clipboard setting).
This has shown significant improvement for many users. [accessexperts.com]

 

[The_Doc_Man]

I must have previously disabled that feature because when I follow Start >> Settings >> System >> Clipboard and try to enable Clipboard History, I do not see the "Suggested Actions." I looked it up online and found a pot-load of stuff about the 24H2 patch, which apparently farkles up the hidden operations of the new clipboard features. Or maybe the new features of clipboard farkles up Win11. TBH, wouldn't surprise me.

 

[AccessBlaster]

I don't see it either:

Edition Windows 11 Home
Version 25H2

 

[spaLOGICng]

I must have previously disabled that feature because when I follow Start >> Settings >> System >> Clipboard and try to enable Clipboard History, I do not see the "Suggested Actions." I looked it up online and found a pot-load of stuff about the 24H2 patch, which apparently farkles up the hidden operations of the new clipboard features. Or maybe the new features of clipboard farkles up Win11. TBH, wouldn't surprise me.

The Windows Learn Link OP commented on using SQL Server as a BE, using Trusted Connection. The Copilot Response to that recommended using Non-trusted DSN-less Connections and certainly no file-based DSN. I did not provide that here as the OP has Access as a BE.

 

[RonPaii]

My Copilot returned this for me today in addition to the other factors mentioned here as it relates to Windows 11

I have not had an issue with the clipboard. Of course, running a Windows 11 PC with 32 GB Ram and a 12th Gen Intel(R) Core(TM) i7-12700 (2.10 GHz) processor on 1TB SSD probably does not flinch. My cheap HP laptop chokes though, which I intentionally have for testing with my low budget clients, so I will test this on that machine.

​

1. Windows 11 24H2 Has a Confirmed Access Performance Bug​

Multiple reports show that Access becomes dramatically slower on Windows 11 24H2, especially compared to 23H2 or Windows 10.
Issues include slow form rendering, slow queries, and UI lag.

• Clients on 23H2 do NOT have the slowness, confirming it’s specific to 24H2.
• Forms load slowly “top-to-bottom” after upgrading to 24H2. [accessexperts.com] [learn.microsoft.com]

✔ Workaround​

Disable Suggested Actions (Clipboard setting).
This has shown significant improvement for many users. [accessexperts.com]

Winver on my computer shows Windows 11 version 25H2. You should be able to update and hopefully fix your problem.

 

[The_Doc_Man]

From what I saw online, this problem has NOTHING to do with Access except insofar as Access tries to use an affected Windows facility related to the clipboard. The DSN or DSN-less connection ALSO is only affected if it would try to use the clipboard.

I suspect some "brilliant" software engineering to make things better for us poor, misguided users.

 

[Albert D. Kallal]

I have a split database that we use with 12 people.
Recently IT "upgraded" two computers from Win 10 to Win 11, mine being one of them.
The performance of the database is significantly slower. Each click taking 5-15 seconds with the database showing "Calculating..." for up to a minute.
Currently running Office Pro 2021.
The other individual is experiencing the exact same issue.

Note however, if no one is in the database and only I open it up, it runs great. The minute someone else opens it, it slows way down. This has always happened but not to this extent. I have another laptop with Win 10 and it runs much faster comparatively.

Can anyone help?

This MUCH sounds like a issue that would/could be fixed with a persistant conneciton.

I mean, the poser ALREADY has shared and stated the application runs speedy and fine with one user. But, with MORE then one user, then it runs slow. This time and time again is thus fixed by a persistent connection.

And the poster can REALLY quick test this. Just open up a form (any form) that is connected to a table (any table in the BE).
Now try some other things that were slow - are they now speedy and fast?

Again: since you WELL NOTED that the application runs fast with one user, then clearly your computer is WELL ABLE to run fast and correctly.

And I doubt VERY MUCH that YOUR computer knows that someone else is working on the database, but yet you see the big slow down.....

Again, 9 out 10 times, a persistent connection will fix this issue......

So, as quick test:
Open up a form - any form that is bound/connected to a table in the BE. Now, try working while that form remains open - if it runs fast and normal, then the issue can be fixed by using a persistent connection. (and note that the form open may well take a LARGE amount of time to open, but once open, now try working and using the application (leave that form open).

You can achieve a persistent connection by having startup code open the database to a global database object, or some even just open a form bound to some table in the BE, but open it with visible = false ......

Try the above quick test - you don't even need code. If it runs ok, then we have a fix......

Once verified, then we can supply more info on forcing your FE to always maintain that open connection to the BE....
R
Albert