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.

In our PCs the problem occurs with the 32-bit version. It started end of August.

I think you're spot on. For me it shows 499 databases open even though I am setting each to none after being used. :(

We're hopeful for a fix on Patch Tuesday. Have you reverted your Office installation. It will remedy the situation in the mean time. Instructions can be found at: https://www.devhut.net/another-msaccess-exe-process-not-closing-properly-bug/

Também estou com esse mesmo problema. E reverter para a versão 2407 é bastante trabalhoso, principalmente por termos as vezes a instalação para uma mesma pessoa em mais de uma máquina. Microsoft precisa lançar logo a versão com a correção desse problema.

Hi, ...'process remains open after exiting' ... We found a workaround by reverting to build 2406, which worked perfectly. However, despite disabling updates both within Access settings and the system settings, it automatically updated back to build 2408. When reverting to older builds doesn't work, there are other potential workarounds mentioned in our AFo article : Try tu use Trusted Locations A permanently running database as mentioned in a comment to our article yesterday: Start a "dummy" Access database. Leave this database running throughout the workday, or even until you reboot. You can't just start a "dummy" Access instance, you must actually open a database-a new db is fine. Subsequent instances of Access will then open and close properly. This sounds interesting but we haven't yet seen other reports from affected people that it works form them too. Servus Karl **************** Access Forever News DevCon Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg That didn't work for our business. I tried leaving a database running. Any databases opened after that and closed keeps the Access service running until you end it in Task Manager. This is a huge problem for us because we have processes that can't run at night until the Access scripts run and close first. Does anyone know when it will be fixed for sure?

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-06T11:19:27+00:00

In our PCs the problem occurs with the 32-bit version. It started end of August.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2024-09-05T17:36:55+00:00

I think you're spot on. For me it shows 499 databases open even though I am setting each to none after being used. :(
Was this answer helpful?

0 comments No comments
Anonymous

2024-09-05T15:58:19+00:00

We're hopeful for a fix on Patch Tuesday.

Have you reverted your Office installation. It will remedy the situation in the mean time. Instructions can be found at: https://www.devhut.net/another-msaccess-exe-process-not-closing-properly-bug/
Was this answer helpful?

0 comments No comments
Anonymous

2024-09-05T14:56:09+00:00

Também estou com esse mesmo problema. E reverter para a versão 2407 é bastante trabalhoso, principalmente por termos as vezes a instalação para uma mesma pessoa em mais de uma máquina. Microsoft precisa lançar logo a versão com a correção desse problema.
Was this answer helpful?

0 comments No comments
Anonymous

2024-09-05T12:40:12+00:00
Hi,

...'process remains open after exiting' ...

We found a workaround by reverting to build 2406, which worked perfectly. However, despite disabling updates both within Access settings and the system settings, it automatically updated back to build 2408.

When reverting to older builds doesn't work, there are other potential workarounds mentioned in our AFo article:

Try tu use Trusted Locations

A permanently running database as mentioned in a comment to our article yesterday:

Start a "dummy" Access database. Leave this database running throughout the workday, or even until you reboot. You can't just start a "dummy" Access instance, you must actually open a database-a new db is fine. Subsequent instances of Access will then open and close properly.

This sounds interesting but we haven't yet seen other reports from affected people that it works form them too.

Servus
Karl
****************
Access Forever News DevCon
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg
That didn't work for our business. I tried leaving a database running. Any databases opened after that and closed keeps the Access service running until you end it in Task Manager. This is a huge problem for us because we have processes that can't run at night until the Access scripts run and close first. Does anyone know when it will be fixed for sure?
Was this answer helpful?

0 comments No comments