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).
Sounds really good Ed. Looking forward to have an update.
We are still running on Version 2312 (Build 17126.20190), but I have to say, that this version is far better than 2311. Of cause it's not the best version Excel have ever released, but when we have issue I just export all code and import it again, which helps on the problem for now.
Alex
Hello !!! today was no different than yesterday. As you will see I started Excel 87 times in Safe Mode to either type VBA code or test VBA code.
Out of those 87 starts, I got ZERO Excel crashes. Looking good. Now I need to return to start Excel in Normal Mode to continue coding and testing. I still have a lot of things to do.
I am going to try to find a way to count the number of times I start Excel in normal mode.
Perhaps create a .BAT file that appends a msg to a text file with "Starting Excel at date time..." and use that as a counter.
I will continue with this, tomorrow Saturday and Sunday and will post again Monday afternoon.
Have a good weekend.
Cheers, Ed
Okay, that sounds really good EOutlook! Looking forward for your update
That sounds promising - thank you for the update