Issues with VBA after upgrading to Version 2311 (Build 17029.20108)

Anonymous
2023-12-18T11:06:31+00:00

Hi, after updating to Version 2311 (Build 17029.20108), we face seriously many issues with our Excel Macro solutions. Something we have never seen before (or at least not for a long period of time). Even things like standard commands like thisworkbook fail. We had to change to 'Monthly Enterprise Channel 2310', which fixed the issue.

Also, it happens on different computers, with different workbooks, so it's not a question about reinstall Excel or something like that.

Btw. We have been working with Macros as our Core business for more than 8 years, and have millions of lines of code. So we normally know what we do.

Is there other people in here which get the same kind of errors with VBA using this version?

Microsoft 365 and Office | Excel | For business | 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
Answer accepted by question author
Anonymous
2024-01-10T18:50:07+00:00

All our issue was fixed by rolling back from Version 2311 (Build 17029.20108) to Version 2310 (Build 16924.20180).

We had all kind of weird issue with this Version 2311 (Build 17029.20108).

Was this answer helpful?

6 people found this answer helpful.
0 comments No comments

157 additional answers

Sort by: Most helpful
  1. Anonymous
    2024-02-29T20:01:11+00:00

    Today has been a busy one. Excel has CRASHED 5 times and hang 1 time. It is unpredictable when it will either CRASH or HANG. I am executing VBA code with Excel running in SAFE mode, I have "Break On All Errors" enabled, I have "Compile On Demand" disabled, I DON'T have a single "On Error" statement in my code. I don't have missing References. My code compiles with NO errors. My code executes with NO errors. I guess I am executing VBA code in the cleanest possible environment, yet, Excel CRASHES or HANGS !!!

    This is unacceptable.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-02-28T15:41:36+00:00

    Can anyone help with pointing to the Excel version before this error? I have 365 for companies

    that's right, the amendment changed something, but for me it went from 10 errors per week to 5..., there are still files that reset after running the macro, others have a critical error, and still another forward and backward reference failed...
    terribly irritating 
    there are also files that do not load at all,  Run-time error''-2147417848 (80010108)'' Automation error ect...
    

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-02-28T14:55:50+00:00

    It's definitely improved for me in the last update. I've had 2 crashes this week and have had just 1 on the 2 previous weeks.

    Each time the method of opening the file with Macros disabled, recompiling, saving and thenopening with Macros enabled fixes the issue.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-02-28T12:02:39+00:00

    I have had the same problem with vba errors in my files since the update.... My method to fix it is to open the file by "open and repair" method. It usually works but after a few days the same file is once again crashed.

    Repair a corrupted workbook - Microsoft Support

    I am waiting for updates to fix it but after reading it I have doubts whether Microsoft takes the problem seriously...

    Was this answer helpful?

    0 comments No comments