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).
Rebuild the entire tool? Sounds like a crazy suggestion. I could understand if they wanted you to recode part of the code, and write it in another way or something. Have you tried to export all modules, delete them, and import them again?
Also, can you say which version of Excel you are working?
Exactly. I am in Excel 365. I have exported the modules, just haven't imported back in, will try that tonight. I did try and save as an .xlsx so it wipes all the code out, but same issue. I will try tonight to convert on my rolled back computer and see if the new version can open it. Something tells me it may be an i conflict with PowerPivot. I will post an update if I find anything out.
I have the same problem as everybody else on this thread. I just installed 2402 and my workbook that crashed before the update worked perfectly afterwards. But that doesn't necessarily mean anything because the problems come and go. Which makes me think it's caused by background code updates or something due to its cloud based nature.
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...