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.

Sorry. I'm on build 16.0.17928.20066. Trying to go back to 16.0.17830.20166, but the update process gets broken by this config: <Configuration> <Updates Enabled="TRUE" TargetVersion="16.0.17830.20166" /> </Configuration>

Hi, > I'm having the same issue... > When I try to go back to the previous build,... For our reports to Microsoft we always need the version and build number where people see the problem and if possible a version and build number where they don't see it. Servus Karl **************** Access Forever News DevCon Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

I'm having the same issue, plus it runs out of tables after a while of running, where it opens and closes recordsets properly. When I try to go back to the previous build, the update process is broken, so a full repair is needed to get the updates running again. Only this time it finds no new updates.

having the same issue. VBA code that has been running for years now will not run.

Hi, So you see the usual consequences of a hanging process. I just wanted to make sure. As you tested it with very "distant" Win11 builds, it shouldn't be that what plays a role here. Maybe sth else that's in your environment but not in mine. Several others were able to replicate the problem which was also reported at SO . It's already reported to Microsoft. I'll let you know when there's news. So far, it only happens in the beta versions/channels, not in the Current Channel version 2407. That would be the masses and the point where we would write a documenting article on AFo . 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-08-23T18:12:53+00:00
Sorry. I'm on build 16.0.17928.20066.

Trying to go back to 16.0.17830.20166, but the update process gets broken by this config:

<Configuration>
```
&lt;Updates Enabled="TRUE" TargetVersion="16.0.17830.20166" /&gt; 
```
</Configuration>
Was this answer helpful?

0 comments No comments
Anonymous

2024-08-23T18:03:23+00:00

Hi,

> I'm having the same issue...
> When I try to go back to the previous build,...

For our reports to Microsoft we always need the version and build number where people see the problem and if possible a version and build number where they don't see it.

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

0 comments No comments
Anonymous

2024-08-23T17:47:13+00:00

I'm having the same issue, plus it runs out of tables after a while of running, where it opens and closes recordsets properly.

When I try to go back to the previous build, the update process is broken, so a full repair is needed to get the updates running again. Only this time it finds no new updates.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2024-08-22T19:34:03+00:00

having the same issue. VBA code that has been running for years now will not run.
Was this answer helpful?

9 people found this answer helpful.

0 comments No comments
Anonymous

2024-08-20T13:41:34+00:00

Hi,

So you see the usual consequences of a hanging process. I just wanted to make sure.

As you tested it with very "distant" Win11 builds, it shouldn't be that what plays a role here. Maybe sth else that's in your environment but not in mine. Several others were able to replicate the problem which was also reported at SO.

It's already reported to Microsoft. I'll let you know when there's news.

So far, it only happens in the beta versions/channels, not in the Current Channel version 2407. That would be the masses and the point where we would write a documenting article on AFo.

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

1 person found this answer helpful.

0 comments No comments