Issues with VBA after upgrading to Version 2311 (Build 17029.20108)

Anonymous
2023-12-18T11:06:31+00:00

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?

Microsoft 365 and Office | Excel | For business | Windows

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.

0 comments
Answer accepted by question author
Anonymous
2024-01-10T18:50:07+00:00

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).

Was this answer helpful?

6 people found this answer helpful.
0 comments

157 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-02-05T07:25:48+00:00

    Yes.

    The issue is definitely some form of macro security bug,

    This fixes the issue for a while:

    1. Close Excel completely.
    2. Open and disable macros in the Trust Center settings
    3. Close Excel Completely
    4. Open the file that is having trouble
    5. Recompile the VBA
    6. Save the file
    7. Close excel COmpletely
    8. Open Excel and re-enable Macros
    9. Close Excel
    10. Now your file should work when opened

    The fact that this works means it must be some corruption in the security?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-02-05T07:27:36+00:00

    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.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-02-05T08:01:57+00:00

    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?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2024-02-08T19:25:08+00:00

    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?

    Was this answer helpful?

    0 comments