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

Anonymous

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?

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

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

0 comments

157 additional answers

Anonymous

2024-03-01T08:47:37+00:00

Hello, In December, when my files got corrupted, I transcribed one of the sheets into C# for SQL. In another case, JavaScript and also SQL. Every month, I issue over 400 Excel files for clients, and the motivation was high when I saw what was happening with Excel.
Most of my clients are not renewing their 365 licenses because of this issue.
Was this answer helpful?

0 comments No comments
Anonymous

2024-03-01T07:35:00+00:00

The version 2402 fixed the problem for me. Unfortunately its only available in Beta so far...so its not yet possible to install it as a regular update company wide. Microsoft should take an effort to release it asap!
Was this answer helpful?

0 comments No comments
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 No comments
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 No comments