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-09-02T19:31:50+00:00

    Kathleen,

    MS365 does not log updates the way the old MSI versions did, none the less if you follow the instruction from

    https://www.youtube.com/watch?v=JROodrU7CEQ

     and/or

    https://www.devhut.net/microsoft-office-uninstall-an-update/ you should be able to roll your build back and get some stability.

    Everything is further detailed in my article about this latest bug: https://www.devhut.net/another-msaccess-exe-process-not-closing-properly-bug/

    Actually, before getting into rolling back your installation, did you ever try creating a Trusted Location for your database folder? It has worked for some people facing this bug, including myself. If you are unfamiliar with how to do so, look at: https://youtu.be/QRWufXhnwpM

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-09-02T18:18:38+00:00

    Can't go back. The versions are not logged on my PC.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-09-02T14:52:34+00:00

    Hi Günter,

    Yes, a SQL Server backend is not necessary but may help to get the error symptoms. ;-) We have dozens of discussions on various forums about this, especially since the issue hit the Current Channel last week.

    I hope the (Office wide) bugfix Microsoft has planned for the next few days will really help. We will see.

    Servus
    Karl
    ****************
    Access Forever News DevCon
    Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

    Was this answer helpful?

    0 comments
  4. Günter Born 49,461 Reputation points
    2024-09-02T14:22:35+00:00

    @Karl: I've described some details at Office 365 Version 2408: Issues with Access when accessing a SQL database - I got several reports from blog readers (German, English).

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-09-01T19:42:19+00:00

    Kathleen,

    PS: Have a look also at Karl Donaubauer's reply on the 01.09.24 just above. He included a link.

    Was this answer helpful?

    0 comments