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?
I tested last night and still getting the corrupt file if I save or save as. The difference is when I selected fix, it actually did, but basically wiped out all graphics and pivot tables from the workbook. Microsoft Customer Service basically told me to rebuild the entire tool in the new version and it should work. Everything else they had me try failed, i.e. reinstalling office, repair office, etc..., the check the box measures. So now they want me to rebuild it so I can put in all that work and maybe it will work. Very frustrating because it affects my business and my clients.
Yesterday MS released 2402. According to the release notes it does not address this issue. I spent the day (yesterday) coding and testing and had no problems or crashes.
Has anyone had any success with testing the 2401 build that came out around the 13th? I believe this was supposed to include a fix for some of the VBA issues.