Office version 2608 causing issues with VBA using ActiveX Objects

Eric H 0 Reputation points
2026-08-29T18:47:02.4833333+00:00

Using VBA with certain ActiveX controls is displaying the following errors:image User's image

This seems to affect any applications that use VBA, but the simplest steps to reproduce are:

  1. Copy this very old control to C:\Windows\SysWOW64 folder: ExtLVCTL.ocx.txt
    1. Remove the txt extension.
    2. Register it: Regsvr32 ExtLVCTL.ocx
  2. Open Excel to a new workbook.
  3. Enter VBA using Alt+F11
  4. Insert a UserForm.
  5. Right Click the Toolbox and select "Additional Controls..."
  6. In the Available Controls find "Extended Listview Control", check it, and Press OK.
  7. Drag and Drop this new Ext LV control to the UserForm.
  8. Close the Form.
  9. Open the Form again.
  10. If on Office 365 Version 2608, observe the above errors.
  11. If on Version 2607, the errors do not occur.

I have also tested disabling office updates, reverting from 2608 to 2607, and found the error no longer occurs.

This seems to be happening for various controls, such as the above and iGrid control from 10Tec, which others have reported here: "https://10tec.com/forum/Posts/t7361-32-bit-ActiveX-iGrid-Issue"

Here are a few other links recently reporting this issue or at least a similar issue:

"https://learn.microsoft.com/en-us/answers/questions/5985986/since-latest-excel-release-a-form-on-my-excel-proj"

"https://learn.microsoft.com/en-us/answers/questions/5985192/our-excel-add-in-process-runner-glsu-fails-to-load"

"https://www.reddit.com/r/microsoftoffice/comments/1vtv5zh/recent_office_update_broke_vba_macro_emailer/"

I had a backup from a user exhibiting this issue restored to a bare metal Hyper-V system so I could research and test on, so if you need to me to test something, let me know.

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

2 answers

Sort by: Most helpful
  1. 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

  2. Ryan-N 15,295 Reputation points Microsoft External Staff Moderator
    2026-08-29T19:21:45.16+00:00

    Hi Eric,

    Welcome to the Microsoft Q&A forum.

    Thank you for providing such detailed information about this issue.

    Based on your description, the clear reproduction steps you provided, and similar reports from other users, it appears that Version 2608 may be causing an issue related to VBA and certain ActiveX controls.

    In this situation, I recommend submitting feedback directly to the Excel product team through the Feedback feature (Help > Feedback) so that they can investigate and determine whether this is a regression issue introduced in Version 2608.

    If you have any questions or need further assistance, please feel free to share them in the comments on this post so I can continue to support you.

    I look forward to continuing the conversation.


    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. 

     

    Was this answer helpful?

    0 comments No comments

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.