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-16T03:02:42+00:00

    There was a mention somewhere in the links below, that somebody actually specified the working folder as a 'Trusted Location' and the problem of the ghost Access went away ... I confirm that I also did that last week, and the problem did go away ... not sure if Microsoft have released any fix at around the same time ... but my problem did go away ...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-09-10T17:32:42+00:00

    Hi,

    > Is it normal for it to show me two different versions/build numbers?

    Yes, the "About Access" build number is rubbish, i.e. from a random dll, which doesn't get updated with every new Office build. Only the Office build number directly in the Account page is meaningful.

    > Should I assume I am on the latest version version 17928.21056,

    Yes, you have the build with the fix.

    Thanks for all your help, Karl. It is much appreciated. :-)

    Was this answer helpful?

    0 comments