Microsoft Access not closing

Question

When I start the Access program it opens fine but then when I close, about 90% of the time it hangs on a blank screen. I need to use task manager to end the task. This even happens with a blank new database with nothing in it. I am using Office 365, windows 11.

Answer 1

Hi,

The build number 19822.20086 indicates that you are probably in Current Channel Preview which is an "Insider" (i.e. almost beta) channel with more bugs than the productive update channels. You could try to switch to one of the productive channels to see if the builds there don't show the problem.

Servus
Karl

---

Access Forever, News, DevCon = Access online conference April 16+17

Answer 2

SO - my problem is hopefully resolved - here is what I've learned (maybe)! The ultimate fix was to do a regedit, renaming the Office 16 folder, allowing it to get recreated. How did the office profile get corrupted in the first place? The guess is that about a week ago I decided to ADD the Outlook program to my 365 apps (64 bit). Of interest - and dismay - Copilot states that the build I had, as well as a subsequent one that was reinstalled under copilot's direction, both STILL have the "Access not closing" bug but Copilot thinks the chances of it becoming a problem again are slim because the profile is now more stable. (?) Copilot reported that both builds (under the Microsoft family plan) are on a VERY slow rollout, only twice a year, and even though they found the fix in September of 2024, I don't have it yet. My original foray led me to a wide range of potential culprits: printer drivers, hardware acceleration, accessibility settings, com add-ins. None of those were the issue. Running access in safe mode successfully helped to rule out some of this. For what it's worth, I'm now on Version 2602, Build 19725.20190 Click to Run/Current Channel (installed at the direction of copilot, needing a Microsoft Office Deployment Tool).

Answer 3

Coincidentally, I've been experiencing a similar problem today, although I think in my case, there's a specific reason; I messed something up.

This AccessForever.org Bug Article is older, but check it out anyway. https://www.accessforever.org/post/hanging-instance-of-access-after-closing-a-database Since you are already on a later version and build than the one mention, the most relevant part of blog post might the workarounds described, which you could try.

You mentioned a build, but not a version number. Also, do you have 32 bit or 64 Access installed.