After updating Access in Office 365 to version 2408, the MSACCESS.EXE process remains after exiting Access.

Anonymous
2024-08-20T05:08:41+00:00

After applying the quality update for the latest channel (preview version) of Microsoft Access (64-bit), version 2408 (build 17928.20066) dated 8/14, the MSACCESS.EXE process won't end even after closing Microsoft Access application.

The reproduction steps are as follows:

  1. Create a form named Form1.
  2. On Form1, create a command button named Command1.
  3. In the Click event of Command1, write "Application.Quit".

Run the application, click Command1 on Form1 to close the application. Afterward, when you check the Task Manager, MSACCESS.EXE process won't end.

This issue does not occur in the 32-bit version. I believe this is a bug. Can you advise where I should report this?

Rolling back to version 2407 resolved this issue.

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

97 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-08-28T11:32:50+00:00

    Similar problem here with Windows 10 Pro in the last few days
    Access version 2408 build 17928.20080

    Current Channel.

    I cannot close Access without forcing shutdown from Task Manager.

    Also as soon as I open a file, Access seems to create extra locks on the database. E.g., if I open an Access file and immediately click Compact and Repair it tells me that I cannot do this because a user (Me) has a lock on the file.

    VB code that used to be fairly quick now takes forever to run.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-08-28T13:44:12+00:00

    Just installed 2408 Build 16.0.17928.20114 (32-bit) released August 26th, with no improvements.

    I have done a feedback within Office directly to MS.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-08-28T14:24:00+00:00

    The latest update seems to only update the MSO.DLL, while the ACEDAO.DLL is still at 16.0.17928.20018 where the problem may be located.

    I'm on Current Channel Preview.

    List of references and version in my system currently:

    • C:\Program Files (x86)\Microsoft Office\root\Office16\MSACC.OLB  Version: 16.0.17830.20056
    • C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\ACEDAO.DLL  Version: 16.0.17928.20018
    • C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\MSO.DLL  Version: 16.0.17928.20114

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-08-28T14:25:46+00:00

    Today has not been a good day... Also getting the "Cannot open any more databases" error as well as those already mentioned here. Now seems that 2408 is started to be installed widely on the Current Channel and I have a number of clients with one or more of these issues. How did this get out of Preview? Any official confirmation from MS that they are aware?

    Oh, and also showing on 32-bit clients as well as x64.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments
  5. Anonymous
    2024-08-28T16:11:20+00:00

    Same problem

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments