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.

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

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

I'm on Current Channel Preview, and today's update has removed the two issues I had, not closing and running out of databases. I currently have the following versions: C:\Program Files (x86)\Microsoft Office\root\Office16\MSACC.OLB Version: 16.0.17830.20056 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\ACEDAO.DLL Version: 16.0.18025.20024 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\MSO.DLL Version: 16.0.18025.20024 Well done to all for reporting and keeping this issue on top of the agenda.

Could it be that the users not having the issues experienced are still using an earlier update of Office? As I mentioned in another Post, I reverted to the previous version of Office and now no longer experiencing the problems discussed in this thread.

This is the version I'm running and am unable to duplicate the error. Version 2408 Build 16.0.17928.20114 32-bit Looks like I was updated 8/26.

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-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-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-04T14:03:05+00:00
I'm on Current Channel Preview, and today's update has removed the two issues I had, not closing and running out of databases. I currently have the following versions:
- C:\Program Files (x86)\Microsoft Office\root\Office16\MSACC.OLB Version: 16.0.17830.20056
- C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\ACEDAO.DLL Version: 16.0.18025.20024
- C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\MSO.DLL Version: 16.0.18025.20024
Well done to all for reporting and keeping this issue on top of the agenda.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2024-09-04T14:22:37+00:00

Could it be that the users not having the issues experienced are still using an earlier update of Office?

As I mentioned in another Post, I reverted to the previous version of Office and now no longer experiencing the problems discussed in this thread.
Was this answer helpful?

0 comments No comments
Anonymous

2024-09-04T14:53:39+00:00

This is the version I'm running and am unable to duplicate the error.

Version 2408 Build 16.0.17928.20114 32-bit

Looks like I was updated 8/26.
Was this answer helpful?

0 comments No comments