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

157 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2024-03-01T01:40:29+00:00

    Hello Piotr !!!!

    Could you please let me know the alternatives you are considering about switching out of Microsoft? I would really very much like to hear from you, what are they.

    I am developing an App for a customer that is paying me for it. My deadline to deliver it is end of March. Past end of March, implementation should start. With this unstable crashing, hangable, Excel, I am afraid I might end up having to pay my customer because this piece of garbage does not work. And to make things worse, I have not found a way to go back to version 2310 because I am using a Home edition of Microsoft 365. NONE of the procedures shared here or in any other web site, including Microsoft's, on the Internet, work.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-02-29T20:18:39+00:00

    You're right, I've already spent a tremendous amount of hours on this issue. I'm fed up with Excel and am convincing clients to switch. Not just Excel but also Microsoft.

    At the moment, what I suggest:

    • Download the Excel version from February 28, 2024 - they removed some of the issues like "critical error", etc.
    • Restore the version from October, it supposedly helps (I didn't downgrade because things calmed down a bit).
    • Create a file that retrieves data from the damaged one and overwrites it (it worked for me - I named these files "Emergency Launch").
    • Change in the code - declaring (dim wb as workbook, set wb = thisworkbook, dim ws as worksheet, set ws = wb.sheets(x), etc.) - a lot of work but there's less memory leak when saving.
    • If Excel wants to repair the file, let it do so and save (but this is a no-brainer that soon becomes relevant again).

    Overall, it seems to me that files saved with the faulty Excel version (from December to the penultimate update) must be saved in the latest version of 28.02.24, but I'm not 100% sure.

    The problem is in the memory leak, where errors are saved and then Excel can't handle opening those errors.

    Was this answer helpful?

    0 comments
  3. 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
  4. 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