This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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?
A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data
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.
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).
Yes, thanks for the heads up !!! I have updated from 2402 Build 17328.20108 to 2402 Build 17328.20142. I will spend most of the day (today) testing and refining VBA code, so I will have a good idea about this update later today. I will post then.
The update from today, 01.03.2024, fixed all my files. I had a folder with 10 different errors, and it didn't detect errors in any of them.
Yesterday's update didn't fix anything (29.02.2024), and I don't see a new one on the website, so please click update because even though I have automatic updates enabled, it didn't do it by itself.
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.
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!