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).
Quick update! I'm currently on Vs 2401 (Build 17231.20194)
I'm first in to the offices so only I was accessing the files.
I have 3 main files that are from templates that are generated each week. I opened 2 of them but the 3rd one failed. I did the fix to get it working.
Then I have a summary Workbook that opens these 3 files to import the data. This time one that had just opened - failed... and I had to do the fix again!
These are files using unchanged code for several years that are suddenly "corrupting" on a regular basis. So frustrating and could well cost me my employment due to us now having a system that is unusable for those who would not be patient enough to do the fix every time a file corrupts (my directors !)
How do we elevate this issue?
I just helped another organization with macro problem. They use version 2311 (Build 17029.20140). They have been using the same Excel file with macros for 4 years without any problem, and not suddenly the file can't save.
"Error where detected while saving..."
Microsoft - please take this seriously.
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.
I can't share a file with the problem, without sharing all my source code. I will try to remove some of the code, and see if I can create a test-file with the error.