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

Hi,

thanks for rolling known issues out to production MS!

The default setting Current Channel is susceptible to update bugs, as we have already seen in many cases. If possible, you should switch to a slower channel for productive purposes.

The monthly and semi-annual channels are less frequently affected. When they are, they are usually caused by security updates that are so important to Microsoft that they are quickly delivered to the slower channels too.

This AFo article describes how to set and change channels: Demystifying Microsoft 365 Update Channels

Servus
Karl
****************
Access Forever News DevCon
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

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:

1. Try tu use Trusted Locations
2. 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 for them too.

Servus
Karl
****************
Access ForeverNewsDevCon
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

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:

1. Try tu use Trusted Locations
2. 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 ForeverNewsDevCon
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?

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.

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/