Forum Discussion
Solved
Access doesn't close properly. A remaining background process can only be terminated in task manager
Since yesterday I noticed that in all my Access databases there is a problem when I close them. When I close a database, it leaves a background process that can only be terminated in Task Mana...
- Yes, here also the update available (Europe). Tested en fix the problem. Trusted Location not necessary any more. But I highly recommend it. Otherwise you will have problem starting from April. MS is blocking marcos. Check https://techcommunity.microsoft.com/t5/microsoft-365-blog/helping-users-stay-safe-blocking-internet-macros-by-default-in/ba-p/3071805
close access with a button on your form invoking this event, it always works, of course a non saved record, will not be saved.
x = Shell ("cmd.exe /c TASKKILL /F /IM msaccess.exe")
As Coskerk says "This issue got resolved last year. MS released a bad version of Access. Once the released the fixed version everything was fine and back to normal."
The issue disappeared for me about 8 months ago after MS issued an update. My updated Access installs have been operating without this issue for quite some time.
Karl Donaubaur was correct when he cited an MS update as the source of the problem shortly after it happened. I well remember the panic it created.
- How come I still have the issue then?
- Well now that I look back through my journal. I did an in-place reinstall of windows 11 to clear up other issues like unreliable copy/paste and no sound for 5 minutes after I turned on my earphones. In-place reinstall left all my files and apps as they were. Most of the windows bugs were gone but unreliable copy/paste is still crops up occasionally. A few weeks later, Access was still not closing properly. Suspecting that there might be a bug fix, I downloaded the Office 365 Premium Offline Installer (which includes Access) and used it to reinstall office. Problem gone. A few days later when I opened Access again, it started closing properly. No hidden background process. I checked using Sysinternals Process Explorer. So I am not sure whether the Windows or Office reinstalls fixed the problem or subsequent updates automatically installed fixed the problem but have not experienced the problem for several months.