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.

I'm in the same boat as Karl. I cannot duplicate on my machines but have numerous clients having the issue. I have been unable to determine why it works for some and not others. Would be very helpful if we knew. Scott

Roberto, I'm glad you found the article useful. I had hoped Microsoft would have published something on the official Fixes and Workarounds page, but when nothing was coming I decided to try and help out and published my own article grouping together all the information I could collect from various online sources and my own experiences with this latest bug. Hopefully we will see a fix in the Patch Tuesday, but since Karl is requesting repo steps/databases that has me very worried that the issue hasn't been fully diagnosed yet. -- Roberto, Me alegro de que hayas encontrado útil el artículo. Tenía la esperanza de que Microsoft hubiera publicado algo en la página oficial de Correcciones y Soluciones Alternativas, pero cuando no llegaba nada, decidí intentar ayudar y publiqué mi propio artículo agrupando toda la información que pude recopilar de varias fuentes en línea y mis propias experiencias con este último error. Con suerte, veremos una solución en el parche del martes, pero dado que Karl está solicitando pasos de repositorio / bases de datos, eso me preocupa mucho que el problema aún no se haya diagnosticado por completo. -- Traducción de Google Translate

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 have just updated the status section in our documenting article . The bad news is that the fix in the Current Channel is to be expected only next week. The good news is that it has been available in the Current Channel Preview (CCP) since yesterday. That is the (beta) channel for which it was first mentioned in the initial posting of this thread and elsewhere. See the AFo article for details. As written there, fix reports from CCP are welcome. Servus Karl **************** Access Forever, News , DevCon Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

You must be immune. I made a mistake in my write up there, the correct response should be Open Databases : 2. The affected version will increase and increase until it explodes. At least there is an acid test now that can be done reliably.

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-04T13:46:30+00:00

I'm in the same boat as Karl. I cannot duplicate on my machines but have numerous clients having the issue. I have been unable to determine why it works for some and not others. Would be very helpful if we knew.

Scott
Was this answer helpful?

0 comments No comments
Anonymous

2024-09-04T11:36:27+00:00

Roberto,

I'm glad you found the article useful.

I had hoped Microsoft would have published something on the official Fixes and Workarounds page, but when nothing was coming I decided to try and help out and published my own article grouping together all the information I could collect from various online sources and my own experiences with this latest bug.

Hopefully we will see a fix in the Patch Tuesday, but since Karl is requesting repo steps/databases that has me very worried that the issue hasn't been fully diagnosed yet.

--

Roberto,

Me alegro de que hayas encontrado útil el artículo.

Tenía la esperanza de que Microsoft hubiera publicado algo en la página oficial de Correcciones y Soluciones Alternativas, pero cuando no llegaba nada, decidí intentar ayudar y publiqué mi propio artículo agrupando toda la información que pude recopilar de varias fuentes en línea y mis propias experiencias con este último error.

Con suerte, veremos una solución en el parche del martes, pero dado que Karl está solicitando pasos de repositorio / bases de datos, eso me preocupa mucho que el problema aún no se haya diagnosticado por completo. -- Traducción de Google Translate
Was 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-09-04T09:31:54+00:00

Hi,

I have just updated the status section in our documenting article.

The bad news is that the fix in the Current Channel is to be expected only next week.

The good news is that it has been available in the Current Channel Preview (CCP) since yesterday. That is the (beta) channel for which it was first mentioned in the initial posting of this thread and elsewhere.

See the AFo article for details. As written there, fix reports from CCP are welcome.

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

4 people found this answer helpful.

0 comments No comments
Anonymous

2024-09-04T09:18:45+00:00

You must be immune. I made a mistake in my write up there, the correct response should be Open Databases : 2. The affected version will increase and increase until it explodes. At least there is an acid test now that can be done reliably.
Was this answer helpful?

0 comments No comments