Our Excel add-in, Process Runner GLSU, fails to load after Microsoft Office updates from Version 2607 to Version 2608. This started August 17, 2026 and is actively growing in scope

Question

Our Excel add-in, Process Runner GLSU, fails to load after Microsoft Office updates from Version 2607 to Version 2608. This started August 17, 2026 and is actively growing in scope

Vrushali Pawale 5

Our Excel add-in, Process Runner GLSU, fails to load after Microsoft Office updates from Version 2607 to Version 2608. This started August 17, 2026 and is actively growing in scope.

Error messages:

Excel: Cannot run the macro 'onLoad'
VBA: System Error &H80004005 (-2147467259). Unspecified error
VBA: Compile error in hidden module: ThisWorkbook

Gosper, Collin 0 Reputation points

2026-08-26T02:21:40.6266667+00:00

Having the same issue. You can roll back to Version 2607 and disable updates for the time being as a workaround.
Cameron Spencer 5 Reputation points

2026-08-26T12:14:44.9+00:00

We have a number of users experiencing this same problem
Alexander Christensen 0 Reputation points

2026-09-01T10:30:53.4+00:00

We have experienced similar issues with our VBA solutions following Microsoft 365 updates released after Version 2605 (Build 20026.20182).

The problems have affected multiple VBA-based workbooks, including unexpected compile errors and failures when loading or running macros.

As a temporary workaround, we have therefore decided to roll back Microsoft 365 Apps to Version 2605 (Build 20026.20182) and pause further Office updates for the time being.

Since rolling back to this version, our VBA solutions have been significantly more stable.

It would be helpful if Microsoft could investigate whether any changes introduced after Version 2605 are affecting VBA compatibility.
Hendrix-V 19,035 Reputation points Microsoft External Staff Moderator

2026-09-02T04:19:11.32+00:00

Hi,

I can understand how challenging this situation is, especially when both your internal testing and customer reports consistently point to the same behavior after upgrading Office.

At this stage, no alternative workaround has been identified in this discussion that reliably allows affected VBA solutions to run normally on Version 2608. While rolling back is understandably not the preferred option for many organizations, it appears to be the only consistently successful mitigation reported by users at this time.

Please note that I can provide suggestions and share any potential workarounds that might help while the issue is still being reviewed. In addition, I don’t have visibility into the internal workflow of Microsoft’s backend teams, so I’m unable to provide a timeline or guarantee when a fix or improvement will be released.

I hope you understand this limitation. I’m in the same position of waiting for updates, and I’ll continue to support you with any new information or alternative solutions I can provide in the meantime.

1 answer

Your answer

Gosper, Collin 0 Reputation points

2026-08-26T02:21:40.6266667+00:00

Having the same issue. You can roll back to Version 2607 and disable updates for the time being as a workaround.
Cameron Spencer 5 Reputation points

2026-08-26T12:14:44.9+00:00

We have a number of users experiencing this same problem
Alexander Christensen 0 Reputation points

2026-09-01T10:30:53.4+00:00

We have experienced similar issues with our VBA solutions following Microsoft 365 updates released after Version 2605 (Build 20026.20182).

The problems have affected multiple VBA-based workbooks, including unexpected compile errors and failures when loading or running macros.

As a temporary workaround, we have therefore decided to roll back Microsoft 365 Apps to Version 2605 (Build 20026.20182) and pause further Office updates for the time being.

Since rolling back to this version, our VBA solutions have been significantly more stable.

It would be helpful if Microsoft could investigate whether any changes introduced after Version 2605 are affecting VBA compatibility.
Hendrix-V 19,035 Reputation points Microsoft External Staff Moderator

2026-09-02T04:19:11.32+00:00

Hi,

I can understand how challenging this situation is, especially when both your internal testing and customer reports consistently point to the same behavior after upgrading Office.

At this stage, no alternative workaround has been identified in this discussion that reliably allows affected VBA solutions to run normally on Version 2608. While rolling back is understandably not the preferred option for many organizations, it appears to be the only consistently successful mitigation reported by users at this time.

Please note that I can provide suggestions and share any potential workarounds that might help while the issue is still being reviewed. In addition, I don’t have visibility into the internal workflow of Microsoft’s backend teams, so I’m unable to provide a timeline or guarantee when a fix or improvement will be released.

I hope you understand this limitation. I’m in the same position of waiting for updates, and I’ll continue to support you with any new information or alternative solutions I can provide in the meantime.

Answer 1

Hendrix-V 19,035 Microsoft External Staff Moderator

Hi Vrushali Pawale,

Based on the reports shared, the issue appears to be affecting some users after Microsoft 365 Apps updated from Version 2607 to Version 2608, resulting in errors such as "Cannot run the macro 'onLoad'" and VBA-related loading failures.

As a temporary workaround, you may want to try the approach mentioned by Gosper, Collin:

Roll back Microsoft 365 Apps to Version 2607.
Temporarily pause or disable Office updates to prevent reinstallation of Version 2608.
Verify whether the GLSU add-in loads correctly after the rollback.

Since this appears to involve a third-party Excel add-in, it may also be helpful to check with the Process Runner GLSU vendor for any compatibility updates or guidance related to Version 2608.

If you continue to experience the issue after rolling back, please share your Office build number and any additional error details. This information may help identify whether the behavior is related to the Office update or a specific add-in configuration.

Let me know if you need further assistance, feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Vrushali Pawale 5 Reputation points

2026-08-26T07:57:36.4166667+00:00

The Excel Addin is developed by us only. GLSU works prefectly fine with 2607. We have customers for this addin and they have upgraded their office version to 2608 and facing the issue. And we can also internally reproduce the same. Problem here is our customers say that they dont want to downgrad to 2607. Is there a workaround for this until next patch from Microsoft is released.
Hendrix-V 19,035 Reputation points Microsoft External Staff Moderator

2026-08-27T06:55:34.0066667+00:00

Hi Vrushali Pawale,

Thank you for the additional details. Since you've confirmed that GLSU is internally developed, works correctly on Version 2607, and the behavior is reproducible on Version 2608 across multiple environments, this helps establish a consistent compatibility issue with the newer Office build.

At this time, we are not aware of a documented workaround that allows the add-in to operate normally on Version 2608 without either modifying the add-in or reverting to Version 2607. The only workaround currently reported in the discussion is rolling back to Version 2607 while further investigation continues.

Please note that I can provide suggestions and share any potential workarounds that might help while the issue is still being reviewed. In addition, I don’t have visibility into the internal workflow of Microsoft’s backend teams, so I’m unable to provide a timeline or guarantee when a fix or improvement will be released.

I hope you understand this limitation. I’m in the same position of waiting for updates, and I’ll continue to support you with any new information or alternative solutions I can provide in the meantime.