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: Create a form named Form1. On Form1, create a command button named Command1. 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.

Update resolves the issues for me. No more msaccess.exe left over. Databases called through CurrentDB appear to be cleaned up properly

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. Servus Karl **************** Access Forever News DevCon Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

Hi, I just downloaded the new build from today and updated the status in our documenting AFo article to this text: Microsoft planned a fix for the Current Channel for Patch Tuesday, Sep 10. The update is version 2408 build 17928.20156 *. If you do not receive it automatically, you can retrieve it by choosing* Update Now on File - Account *. If you were affected by the bug, please let us know if the update fixes the problems for you.* Servus Karl **************** Access Forever News DevCon Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

Hi Karl, I have just updated to the new version mentioned in your post (Currently in Preview). Now using : Microsoft® Access® for Microsoft 365 MSO (Version 2409 Build 16.0.18025.20024) 32-bit I can confirm that the bug appears to be fixed. It passes the test above ! And I have briefly tested several client databases - which were previously affected - but now appear to running fine. I'll continue to use it until it hit's the Current Channel next week. Thank you ! Ben

Hi, I've seen a few reports about this with the beta versions 2408 and 2409. Some can and some (like me with your build on Win11) cannot reproduce it. So there seems to be sth else involved. Does the hanging background process hinder you from opening accdbs with a double click in the Explorer or from a link/shortcut? Are there other negative consequences? Servus Karl **************** Access Forever News DevCon Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

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

Anonymous

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:

Create a form named Form1.
On Form1, create a command button named Command1.
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.

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

Anonymous

2024-09-10T22:56:26+00:00
Update resolves the issues for me.
- No more msaccess.exe left over.
- Databases called through CurrentDB appear to be cleaned up properly
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments
Anonymous

2024-09-10T17:29:14+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.

Servus
Karl
****************
Access Forever News DevCon
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments
Anonymous

2024-09-10T14:01:33+00:00

Hi,

I just downloaded the new build from today and updated the status in our documenting AFo article to this text:

Microsoft planned a fix for the Current Channel for Patch Tuesday, Sep 10. The update is version 2408 build 17928.20156*. If you do not receive it automatically, you can retrieve it by choosing* Update Now on File - Account*. If you were affected by the bug, please let us know if the update fixes the problems for you.*

Servus
Karl
****************
Access Forever News DevCon
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments
Anonymous

2024-09-04T10:10:52+00:00

Hi Karl,

I have just updated to the new version mentioned in your post (Currently in Preview).

Now using : Microsoft® Access® for Microsoft 365 MSO (Version 2409 Build 16.0.18025.20024) 32-bit

I can confirm that the bug appears to be fixed. It passes the test above ! And I have briefly tested several client databases - which were previously affected - but now appear to running fine.

I'll continue to use it until it hit's the Current Channel next week.

Thank you !

Ben
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments
Anonymous

2024-08-20T11:25:37+00:00

Hi,

I've seen a few reports about this with the beta versions 2408 and 2409.

Some can and some (like me with your build on Win11) cannot reproduce it. So there seems to be sth else involved.

Does the hanging background process hinder you from opening accdbs with a double click in the Explorer or from a link/shortcut?

Are there other negative consequences?

Servus
Karl
****************
Access Forever News DevCon
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments