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).
I have a rolled back version of Excel on 1 computer and the newest version on another. My file works on the reverted version and on the new version. The issue is, if you do a Save or a Save As, when you close and reopen the file, you get the corrupted file error on the new version. I can manually copy and paste the file to a different location and it works fine, but if I open then do a save or Save as to that file and try and reopen, you get the error. This is on a specific file that has VBA code in it, contains a data model, and has many pivot tables in it. so not on every file nor even with others that have VBA and Data model, so not sure what is specifically in this one that Excel no longer likes when saving.
I don't think so. I was able to open, execute the code, save and close the Workbook several times today in the morning, before Excel crashed. I have not found a pattern that allows me to replicate the crash. After a crash, I reboot windows, do an online repair of Office, reboot the PC again and try to continue developing/testing. Sometimes I can continue and sometimes I can't. Reason why? I don't know. Since the problems started, I open my workbooks in safe mode and disable monitor 1 of 2 prior to opening a workbook to continue developing/testing.
After a crash, (before doing the online repair and rebooting) I start Excel in normal mode and Excel recognizes and opens the workbook that was opened when it crashed. Excel asks me if I want to start in safe mode. I choose NO. Excel starts, opens the workbook that was opened when it crashed and I proceed to do a "Save As" with a different filename... this way I don't loose code or ActiveX controls.
Seems improved to me. Only had 1 crash this week.
Previously it was daily.