MS Office 2024 has VB execution failed after 16.0.17932.20976 (included)

Irene Wu 0 Reputation points
2026-11-11T09:45:24.43+00:00

Hello guys,

we have a legacy program are running in MS Access with VB Marco.

it's happen a vb execution issue after office patch 16.0.17932.20976 (included)

some user cannot running VB function with latest patch anymore as below screenshot影像 (5)

we try different patch version like 17932.20996, 17932.21000, 17932.21056.

all of above version reaction same issue, VB cannot open.

this function was working fine on 16.0.17932.20976, but this patch have Excel copy & paste issue.

would you please help to fix this issue or any workaround solution we can fix it ?

Thank you!

Irene

Microsoft 365 and Office | Access | Development
0 comments No comments

2 answers

Sort by: Most helpful
  1. Michelle Nguyen 2,780 Reputation points Independent Advisor
    2026-11-11T11:14:21.8966667+00:00

    Hello @Irene Wu

    Thank you for providing the screenshot of the error. The message:

    “Microsoft Access is unable to load the Visual Basic for Applications dynamic-link library (DLL) Vbe7.”

    indicates that Access is encountering an issue loading the VBA component. Therefore, I would first like to determine whether the problem lies with the Office/VBA installation or with the legacy database itself.

    On one of the affected machines, please try the following:

    -Create a new, blank Access database > Go to "Database Tools" > "Visual Basic" > Check if the same "Vbe7" error appears.

    If the new database also triggers the error, please try performing an "Online Repair" of Office on a test machine and check again.

    If VBA works correctly in a new database but the error only occurs in your legacy database, please first create a backup of that database. One potential workaround for Access issues involving "Vbe7.dll" is to "decompile" and then "recompile" the database. However, as that documentation relates to an older issue with Access 2010, I strongly advise testing this only on a copy of the database, never on your production database.

    Additionally, could you please provide the following information?

    • Is your version of Office LTSC 2024 32-bit or 64-bit?
    • Does the error also occur in a blank database?
    • Does the error appear on all machines following the update, or only on some?

    Since you have confirmed that VBA works on version 16.0.17932.20976 but fails on several newer builds, knowing whether the issue can be reproduced in a blank database would be crucial for distinguishing between a problem specific to your legacy database and an issue with Office/VBA itself following the update.

    Please note that I am a fellow community user, not a Microsoft employee; therefore, I cannot confirm whether this is a known regression that has been officially documented by Microsoft.

    Was this answer helpful?


  2. 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.