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).
Hello !!!
Another Excel CRASH followed by a Windows Reporting Error. Next, the events as reported by Windows:
Cheers,
Ed
Hello !!!
Another Excel CRASH !!!! just a few minutes ago !!!
Cheers,
Ed
Arrrgh. I need to ask my IT department. Seems like it's rolled back a LONG way:
Arrh, not good. Version 2402 has been the most stable version I've ever tried. I haven't had any crashes for the last few months or so. I'm on version 2403 now, and it is still stable with no crashes.
I can find the following on the internet regards the exception code: "The exception code 0xc0000374 indicates a heap corruption error. Heap corruption errors often occur due to bugs in the application code or issues with the system memory management."
How did it happen? And where you able to get the crash again?