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

Anonymous
2024-08-20T05:08:41+00:00

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:

  1. Create a form named Form1.
  2. On Form1, create a command button named Command1.
  3. 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.

Microsoft 365 and Office | Access | For home | Windows

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

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-08-28T14:24:00+00:00

    The latest update seems to only update the MSO.DLL, while the ACEDAO.DLL is still at 16.0.17928.20018 where the problem may be located.

    I'm on Current Channel Preview.

    List of references and version in my system currently:

    • 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.17928.20018
    • C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\MSO.DLL  Version: 16.0.17928.20114

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-08-28T11:32:50+00:00

    Similar problem here with Windows 10 Pro in the last few days
    Access version 2408 build 17928.20080

    Current Channel.

    I cannot close Access without forcing shutdown from Task Manager.

    Also as soon as I open a file, Access seems to create extra locks on the database. E.g., if I open an Access file and immediately click Compact and Repair it tells me that I cannot do this because a user (Me) has a lock on the file.

    VB code that used to be fairly quick now takes forever to run.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-08-23T19:02:23+00:00

    Hi,

    > 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

    Have you taken into account that these are two different update channels? The first one is in Current Channel Preview, The other one is in Current Channel. I'm not sure if this works without switching to the according channel.

    I personally do not use a config file but have (for testing)

    1. Added a button to change the update channel, as Peter describes here in point 2. I first change the channel there if necessary.
    2. After that I pull the desired build via the command line, as Peter describes here in method 1.

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

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-08-23T18:52:35+00:00

    I had to go back to 16.0.17726.20126 to solve the problem. The two interim updates, 17830.20166 and 17830.20138, both cause an error in the update module, so I assume they have been removed for the server somehow.

    Was this answer helpful?

    0 comments
  5. 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