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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2024-08-30T17:03:50+00:00

    Consider switching to the Semi-Accual enterprise channel and avoid bugs like this in the future, more information here:

    BUG ALERT: Access not closing on exit in build 2408 - Access developer (accessexperts.com)

    Juan Soto

    14x Access MVP

    AccessExperts.com

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-08-30T17:03:08+00:00

    Consider switching to the Semi-Accual enterprise channel and avoid bugs like this in the future, more information here:

    BUG ALERT: Access not closing on exit in build 2408 - Access developer (accessexperts.com)

    Juan Soto

    14x Access MVP

    AccessExperts.com

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-08-30T16:59:18+00:00

    Hi John

    Consider switching to the Semi-Accual enterprise channel, more information here:

    BUG ALERT: Access not closing on exit in build 2408 - Access developer (accessexperts.com)

    Juan Soto

    14x Access MVP

    AccessExperts.com

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-08-30T16:56:26+00:00

    Everyone,

    If you're not aware, Office365 software has a series of update channels for new features and bug fixes. The most common and bug-prone being the default: Current Channel. If your company is on this channel you get the latest features, and the latest bugs.

    Instead of rolling back to another version, consider changing your update band to Semi-Annual Enterprise. Reasons why:

    1. You will only get updates that have been vetted for six months already.
    2. Your mission critical application is not subject to bugs that easily make it in to the current channel

    For instructions on how to change the channel please refer to this blog post:

    BUG ALERT: Access not closing on exit in build 2408 - Access developer (accessexperts.com)

    Juan Soto

    14x Access MVP

    AccessExperts.com

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2024-08-30T16:00:41+00:00

    Seeing the same problem in my company. It seems to have started on Wednesday this week. I have about 40 users, some on Win10, some Win11, and some also on Windows Server 2016. Running Office 365. MSACCESS.EXE does not drop from Task Manager after closing the window. Users are all using personal copies of a FE that has not changed in months.

    I have confirmed with multiple users that they have the FE file location in their Trusted Locations, along with C:\Program Files\Microsoft Office\root\Office16. This does not fix the problem.

    This cascades to other errors because next day the user starts a new window for Access, then opens the same FE file, and now some tables are locked, files are in use, etc. and my users swear that the error messages are wrong. Once we close all the Access tasks and start over, everything works again.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments