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).
"But only for a period of time" are the key words here. I have three laptops sharing all word setup files (relocated to Dropbox) and working on the same data files. The three PC are all of different age and power; and run a mix of win 10 and 11. All three started to suffer from problems early February. The problem with writing needed different delays depending on the speed of the cpu. (The fastest never exhibited that particular problem) Ican well imagine that recompiling cleans up the code enough to speed up the process to avoid the timing problem until enough garbage is collected again. 0.2 sec was enough for the fastest (lower limit never tested), 0.4 fixed the medium one, but 0.5 was needed for the slowest.
Exactly this. At least it gets you access to it but isn't permanent
I've certianly been having fewer crashes with the current version. I had just 1 last week. It was 2 or 3 per day before that
Yes, in this version of Excel, the quick fix is to move the file to an untrusted folder, so macros are not enabled in the first place. Before enabling the macros, you need to press F11 and compile the VBA project. Then, save the file and open it again in a folder that is trusted. This fixes the bugs in many cases but only for a period of time.
I have some routines that don't always execute properly, but I'm not prepared yet to blame VBA for that. I have had no office crashes.