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).
We did a limited rollback to verify and 2310 seems to be working as expected. Planning a larger rollback due to the time-consuming impact to our support teams as you are seeing. Good luck.
Thank you for the info. I've requested my machine at least gets rolled back but it's not as simple as that as many people have access and use the sheets daily so not sure how just my PC will help. At least I'll be able to test.
Here's to MS getting a fix out sometime soon. Other companies who rely on VBA must be having similar issues I'm sure.
I have just upgraded to the new Version 2311 (Build 17029.20140). Looking forward to see if the issue is still there or if it have been fixed. I will keep you all updated.
Sadly not. Somehow I'm in the "Insider" program and get the updates early... I've been on that build and had the issues. I'm currently on 2401 and still have the issues :-(