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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-09-05T10:07:11+00:00

    Hi,

    ...'process remains open after exiting' ...

    We found a workaround by reverting to build 2406, which worked perfectly. However, despite disabling updates both within Access settings and the system settings, it automatically updated back to build 2408.

    When reverting to older builds doesn't work, there are other potential workarounds mentioned in our AFo article:

    1. Try tu use Trusted Locations
    2. A permanently running database as mentioned in a comment to our article yesterday:

    Start a "dummy" Access database. Leave this database running throughout the workday, or even until you reboot. You can't just start a "dummy" Access instance, you must actually open a database-a new db is fine. Subsequent instances of Access will then open and close properly.

    This sounds interesting but we haven't yet seen other reports from affected people that it works for them too.

    Servus
    Karl
    ****************
    Access ForeverNewsDevCon
    Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-09-05T03:54:08+00:00

    Our in-house program running on Access experienced the same issue with the 'process remains open after exiting' error after running a single query and trying to run the same query again. This prevented us from performing any function twice, displaying the message 'someone else is using the program or process,' which wasn't accurate. The issue was caused by the locked file Access creates. We found a workaround by reverting to build 2406, which worked perfectly. However, despite disabling updates both within Access settings and the system settings, it automatically updated back to build 2408.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-09-04T18:46:33+00:00

    Can confirm, having this problem on our Windows 2022 terminal server, Access v2048...

    thanks for rolling known issues out to production MS!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-09-04T15:21:07+00:00

    Quick note. We have found 2 clients today that had Macro setting in Trust Center set to disabled. We adjusted to Enabled all macros and also added Trusted location to program location. So far that has helped.

    Will report back if anything changes with the users adjusted.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-09-04T14:53:39+00:00

    This is the version I'm running and am unable to duplicate the error.

    Version 2408 Build 16.0.17928.20114 32-bit

    Looks like I was updated 8/26.

    Was this answer helpful?

    0 comments