MS Access Database Instantly Crashes on Version 2512 Build 19509.20000

Daniel Needemyer 40 Reputation points
2025-11-12T19:07:23.1366667+00:00

I have an Access file that worked on Version 2512 (Build 19504.20000), but instantly crashes on Version 2512 (Build 19509.20000). It appears to be a small update 19504 to 19509. From what I can tell, the database locks, then crashes. I can create new databases, but this database crashes.

I have tried:

Compact and Repair the database

Quick Office Repair

Online Office Repair

Microsoft 365 and Office | Access | For business | Windows
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Tammy-Ng 5,585 Reputation points Microsoft External Staff Moderator
    2025-11-13T01:24:11.7833333+00:00

    Dear Daniel Needemyer
    Welcome to Microsoft Q&A Forum!

    Thank you for reaching out. If you're experiencing problems with Microsoft Access after a recent update. You're currently using the Office Insider Beta Channel, specifically Version 2512 Build 19509.20000. This is a preview release that provides early access to new features and updates. However:

    • Preview builds may include changes that are not yet fully refined, especially in applications like Access, which can be sensitive to updates involving forms, queries, VBA, or database locking mechanisms.
    • Your current setup may affect how certain databases open or behave.

    -Rolling back to a release in the Current Channel offers several advantages:

    Provides a more consistent and predictable experience across Office applications.

    Supports smoother operation in production environments.

    Helps maintain optimal performance and compatibility with existing databases.

    -Please follow these steps:
    -Disable Office Updates:

    • Open any Office app (e.g., Outlook, Word or Excel).
    • Go to File > Account > Update Options > Disable Updates.

    This prevents Office from automatically updating again after rollback.

    -Use the Office Deployment Tool:

    -Open Notepad and paste the following XML:
    <Configuration>

    <Updates Enabled="TRUE" TargetVersion="16.0.xxxxx.yyyyy" />

    • Replace xxxxx.yyyyy with the version number you want.
    • Save the file as config.xml in the same folder as setup.exe.
    <Configuration>
      <Add OfficeClientEdition="64" Channel="Current">
        <Product ID="O365ProPlusRetail">
          <Language ID="en-us" />
        </Product>
      </Add>
      <Updates Enabled="TRUE" TargetVersion="16.0.19238.20190" />
      <Display Level="None" AcceptEULA="TRUE" />
    </Configuration>
    

    -Run the Rollback command:

    • Open Command Prompt as Administrator.
    • Navigate to the folder: cd C:\ODT

    -Run the command: setup.exe /configure config.xml

    • Office will now be rolled back to the specified version.

    -Confirm the Version: After installation:

    • Open Access or any Office app.
    • Go to File → Account → About Access.
    • Check the version line, e.g.: Version 2510 (Build 19328.20190)

    I hope this information can help you in this case. Wish you a pleasant day!


    Update: The customer has confirmed that he uses BetaChannel . Here are some suggestions that may help resolve the issue.
    Thank you for sharing your configuration file. I noticed that you are currently using Beta Channel, which is intended for testing early builds and can sometimes include versions that are less stable. This is why the rollback attempt did not work as expected, the Beta channel will continue to push the latest beta build (16.0.19509.20000) even if you specify a previous version.

    To ensure stability, I recommend switching to the Current Channel, which provides more reliable builds for production use. Here’s what you can do:

    • Update your config.xml to use Channel="Current" instead of BetaChannel.
    • Keep the TargetVersion="16.0.19504.20000" setting if you want to roll back to the last stable version.
    • After installation, you can temporarily disable updates until the issue is resolved.

    This approach will help you maintain a consistent and stable environment while Microsoft continues to improve the Beta builds. I hope this information can help you in this case. Wish you a pleasant day!


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".     

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Daniel Needemyer 40 Reputation points
    2025-11-13T19:25:14.1033333+00:00

    I created the following config.xml to roll back to 16.0.19504.20000 - the last version that worked, but it keeps installing 16.0.19509.20000.

    <Configuration>

    <Add OfficeClientEdition="64" Channel="BetaChannel">

    <Product ID="O365ProPlusRetail">
    
      <Language ID="en-us" />
    
    </Product>
    

    </Add>

    <Updates Enabled="FALSE" TargetVersion="16.0.19504.20000" />

    <Display Level="None" AcceptEULA="TRUE" />

    </Configuration>


  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.