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).
Hi Gregory Klein,
We face the same kind of issue in our organization. It's correct that the signature, in some cases, will break, but we found two cases where it happened in our solution.
When we used VBA to copy and delete sheets, the signature would break at some point. The "funny" thing is, it's only sometimes when you execute those commands. So, you can't test and expect it to break, which took us some time before we managed to locate what caused the signature to break.
Our workaround was, of course, not to use those commands. Instead, we implemented the following workaround:
Copy:
Add a new sheet, and then copy all elements, text, ListObjects, shapes, etc., to the new sheet.
Deleting:
Rename the sheet to "Deleted_<A unique code of 6 digits>", and then remove all elements from this sheet, and finally make the sheet VeryHidden.
After this workaround, we have not had any issues.
Alex
Alexander,
We attempted to employ code signing at our organization. However, users would not be able to save some of these documents without stripping the document of its signature. In our experience we have found that adding sheets to a workbook will in turn change the vba project. Because of this, this digital signature has to be reapplied on save, if the user does not have the certificate with the private key in their store they cannot sign it. When this happens the user is prompted and they continue without the signature. Have you found a way around this?
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 requested this from our IT department. I've been ignored. We have around 15 or 20 of us that access the files but anyone in the organisation (>500) has access.