Access doesn't close properly. A remaining background process can only be terminated in task manager

CARKIS51
Copper Contributor
Feb 06, 2022
If by now you don't know, the solution is simple: add the folders where the front and backend are located to Trusted Locations. AND You have to do it for every single user in your network, a step I missed doing the first time and the other two users kept having the problem.
- George_Hepworth
  Silver Contributor
  Feb 06, 2022
  Keep in mind, though, that there have been reports where the Trusted Location workaround wasn't effective. See this note, for example, on the MS site:
  
  https://support.microsoft.com/en-us/office/access-is-unable-to-close-and-leaves-lockfile-active-b2dce32b-b8b0-41f1-ba40-7876e524d9da
  
  Note: This workaround will not work if AMSI (Antimalware Scan Interface) is enabled for all documents. More information about AMSI can be found here: Office VBA + AMSI: Parting the veil on malicious macros - Microsoft Security Blog
  
  Also, it's not always clear that people are fully implementing this, but one has to be cautious.
  - CARKIS51
    Copper Contributor
    Feb 06, 2022
    Thanks. I guess I was one of the several fortunate ones. Glad to know that they'll be releasing a permanent fix.
Karl_Donaubauer
MVP
Feb 04, 2022
Hi,

The Microsoft Access team has published a first version of a support article about this update bug: https://support.microsoft.com/en-us/topic/b2dce32b-b8b0-41f1-ba40-7876e524d9da

In it a fix is announced, but so far without a date. Until then, the workaround recommended is to put the database in a trusted location.

Servus
Karl
************
Access News
Access DevCon
- Karl_Donaubauer
  MVP
  Feb 05, 2022
  Hi,
  
  Since we've seen a lot of positive reports about it and the trusted location is now also the officially recommended workaround by MSFT: In order to keep the thread readable, I think it would be good to especially post here when the workaround does NOT help or other new findings.
  
  Servus
  Karl
  ************
  Access News
  Access DevCon
  - BillCQ
    Copper Contributor
    Feb 07, 2022
    Suggested workaround worked on Friday, not today. Only known "change" was a PC restart. Likely something else changed too, don't know. Tried removing and re-adding trusted locations, has not helped. Also don't know if we have AMSI enabled, have question in with IT.
    
    UPDATE - Restarted PC, workaround again seems to be working. Makes very little sense to me.
DavideGD
Copper Contributor
Feb 03, 2022
What about downgrading runtime versions?

Ciao
Davide
- Gommacri
  Copper Contributor
  Feb 03, 2022
  Downgrading Office 365 to previous version solved
  - error 3048 cant open any more databases
  for me!
  I didn't try for Run-time version
  
  Thanks a lot
  Cristian
  - Tiger7663
    Copper Contributor
    Feb 07, 2022
    @lease forward instructions on how to revert to previous Office 365 version. Thanks.
- Karl_Donaubauer
  MVP
  Feb 03, 2022
  Ciao Davide,
  
  I've never done it myself. So, if somebody has been successful with the Runtime, please report/confirm it here for others.
  
  Personally I would assume the same procedure as desribed in the linked articles also for the Runtime, i.e. with
  
  TargetVersion="16.0.14729.20260"
  
  I would expect to revert the installation back to the previous build of the Current Channel.
  
  Servus
  Karl
  ************
  Access News
  Access DevCon
  - DavideGD
    Copper Contributor
    Feb 03, 2022
    I tried the procedure with the target version "16.0.14729.20194".
    It worked fine on every full version, but nothing changed on runtime versions, they still remain 16.0.14827.20158...
    
    I'm searching for any solution
    
    Ciao

Forum Discussion

Access doesn't close properly. A remaining background process can only be terminated in task manager

Resources