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 No comments

97 answers

Sort by: Newest
  1. Anonymous
    2024-08-29T12:54:08+00:00

    Hola a todos.

    Tenía el mismo problema que comentario en todo este foro. Lo soluciones gracias a ustedes y ahora puedo respirar!!! jajajaja

    Seguí los pasos de este link:

    https://support.microsoft.com/es-es/topic/c%C3%B3mo-revertir-a-una-versi%C3%B3n-anterior-de-office-2bd5c457-a917-d57e-35a1-f709e3dda841 Fui a la versión:

    <Configuration>

    <Updates Enabled="TRUE" TargetVersion="16.0.17830.20166" />

    </Configuration>

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-08-28T16:22:26+00:00

    It's very annoying when this happens. Something similar happened a couple of years ago, a bad Access update caused all my clients to break at once. The solution then was to roll back. In the aftermath, I moved most of my clients onto the Semi-Annual update channel so the updates are not as frequent - this decision has really helped to limit the damage this time around, as most clients have not got the bad update published on the Current Channel.

    I still have had to do a few issues though and need this fixing asap.

    For anyone that doesn't know how to roll back, here is the easiest method I have found :

    File->Account

    Disable the updates :

          Dropdown the **Update Options**  and select Disable Updates.
    

    Then, determine your Update Channel by pressing the About Access button, or read next to it.

    It should be one of Current, Monthly Enterprise, Semi-Annual.

    Locate the Click to Run folder, Open a Command Prompt (as Admin) and enter the command :

    cd "C:\Program Files\Common Files\Microsoft Shared\Clicktorun"

    Use the following to update to the July 9th 2024 version :

    If you are in the Current Chanel then use the command :

    OfficeC2RClient.exe /update user updatetoversion=16.0.17726.20160

    If you are in the Monthly Enterprise Channel then use the command :

    OfficeC2RClient.exe /update user updatetoversion=16.0.17628.20188

    If you are in the  Semi-Annual Enterprise Channel (or Preview) then use the command:

    OfficeC2RClient.exe /update user updatetoversion=16.0.17328.20452

    The command should launch the installer and update your Office back to July 9th.

    Once Microsoft have fixed the problem (typically in a couple of weeks), you can re-enable updates.

    https://www.accessforever.org/post/roll-back-to-previous-versions-of-office

    https://learn.microsoft.com/en-us/officeupdates/update-history-microsoft365-apps-by-date

    Was this answer helpful?

    10 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-08-28T16:11:20+00:00

    Same problem

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-08-28T14:25:46+00:00

    Today has not been a good day... Also getting the "Cannot open any more databases" error as well as those already mentioned here. Now seems that 2408 is started to be installed widely on the Current Channel and I have a number of clients with one or more of these issues. How did this get out of Preview? Any official confirmation from MS that they are aware?

    Oh, and also showing on 32-bit clients as well as x64.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments No comments
  5. 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 No comments