Version 2910 (Nov 10, 26) and Version 2911 can't run internal developed excel tool due the "running out or resources....."

Diaz Valencia, Leonardo 0 Reputation points
2026-11-18T07:32:02.4633333+00:00

Come on, Microsoft, really?

A recent Microsoft 365 Office update was installed, and suddenly critical Excel-based tools that have been running reliably for years are no longer functional because Excel reports that it has run out of resources.

We have already rolled back to a previously working build multiple times, but the application automatically updates again after every restart, bringing the issue back. This has now happened several times and is significantly affecting productivity.

Please investigate this issue and provide a permanent solution as soon as possible. These Excel tools are business-critical, and the current behavior is preventing us from performing essential engineering and sales support activities.

At a minimum, we need:

  • A fix for the Excel resource exhaustion issue.
  • A reliable method to prevent automatic reinstallation of the problematic build.
  • Guidance on whether this is a known issue with the current Microsoft 365 release.

We would appreciate an urgent response.

Microsoft 365 and Office | Excel | For business | Windows

2 answers

Sort by: Most helpful
  1. Fahim-Nz 360 Reputation points Independent Advisor
    2026-11-18T09:18:43.03+00:00

    Hello Leonardo,

    I understand how disruptive this situation is, particularly since your internally developed Excel tools are business-critical and have been working reliably for years.

    Since rolling back to an earlier Microsoft 365 build temporarily restores functionality, it is worth investigating whether the issue is related to Excel’s memory management or compatibility with components found in the internal tools.

    I recommend the following checks:

    1/ Check Excel’s architecture and memory limitations

    1. Open Excel and navigate to File > Account > About Excel.
    2. Check whether the installed version is 32-bit or 64-bit.
    3. Note the complete version, build number, and update channel.

    On 64-bit Windows, 32-bit Excel with Large Address Aware (LAA) can access up to 4 GB of virtual address space. This can help with memory-related errors when working with complex workbooks. Reference: Large Address Aware capability change for Excel

    2/ Temporarily control automatic updates

    Since the earlier build restores functionality, you can temporarily prevent the problematic build from being reinstalled while investigating the issue.

    For an individual installation:

    1. Open Excel and navigate to File > Account.
    2. Select Update Options > Disable Updates.
      User's image

    For organisation-managed devices, an Microsoft 365 administrator can use the Office Deployment Tool (ODT), Group Policy, or Intune to control updates or pin devices to a build tested earlier. Configure update settings for Microsoft 365 Apps

    (Please note that disabling automatic updates will also delay important security updates and product improvements)

    To narrow down the cause, could you clarify the following?

    1. Does the error affect all Excel workbooks or only the internally developed tools?
    2. Does the tool rely on VBA macros, COM add-ins, ActiveX controls, or external libraries?
    3. Does the error appear immediately when opening the tool or when performing a particular operation?

    These details will help determine whether the behaviour is specific to the updated Excel build or related to compatibility or resource requirements within the internally developed tool.

    Was this answer helpful?


  2. AI answer

    2026-11-18T07:34:03.6333333+00:00

    A Microsoft 365 administrator should centrally pin the previously working build before rolling back again; otherwise the normal update mechanism can reinstall Versions 2910/2911 after restart.

    Contain the update

    First record:

    • Update channel: Excel → File → Account
    • Full version/build: File → Account → About Excel
    • Last working full build and first failing full build

    If the devices use Cloud Update with a Monthly Enterprise profile

    Cloud Update is the most direct supported option:

    1. Sign in to the Microsoft 365 Apps admin center with Cloud Update permissions.
    2. Open Cloud Update → Monthly Enterprise.
    3. Select Pause updates and verify that Rollout information changes to Paused.
    4. Select Actions → Roll back devices.
    5. Choose the previously working version/build.
    6. Target the affected device names, or a Microsoft Entra group containing user objects. Cloud Update maps those users to their eligible devices in Inventory.
    7. Monitor Devices or Actions → Manage rolled back devices.

    Starting in September 2026, rolled-back devices remain at the selected target until an administrator explicitly resumes them. Rollback can take up to 24 hours. This capability applies only to devices managed by a Monthly Enterprise profile.^1^

    If updates are managed by Active Directory Group Policy

    Configure the target before repeating the rollback that previously worked:

    1. In Group Policy Management Console, open
      Computer Configuration → Policies → Administrative Templates → Microsoft Office 2016 (Machine) → Updates.
    2. Enable Target Version and enter the complete working build number.
    3. If immediate containment is required, also configure Enable automatic updates appropriately for the affected pilot group.
    4. On a test device, run this from an elevated Command Prompt:
    gpupdate /force
    
    1. Confirm that policy processing completes successfully.
    2. Now repeat the previously successful rollback. This time the centrally applied target prevents the same unmanaged update cycle from immediately undoing it.

    Group Policy overrides conflicting Office Deployment Tool settings.^2^

    If updates are managed by Intune

    Create an Intune configuration profile using Settings Catalog—which exposes more Office settings—or Administrative Templates, and configure the Microsoft 365 Apps Target version setting with the complete working build. Assign it first to a small affected-device group, verify policy success, and then perform the rollback.^2^

    Do not add a separate local policy if Windows Autopatch or Cloud Update owns these devices. Cloud Update can take precedence over Intune, Group Policy, and Office Deployment Tool settings; conflicting policies can also make Autopatch-managed devices ineligible.^3^

    For unmanaged Click-to-Run installations

    The Office Deployment Tool supports both TargetVersion and disabling automatic checks. For temporary containment:

    <Configuration>
      <Updates
        Enabled="FALSE"
        TargetVersion="16.0.xxxxx.yyyyy" />
    </Configuration>
    

    Apply it from an elevated Command Prompt:

    setup.exe /configure configuration.xml
    

    Replace the placeholder with the complete working build. With Enabled="FALSE", Office stops checking automatically, although users can still select File → Account → Update Options → Update Now.^4^

    Build pinning is temporary containment, not a permanent product fix, and it delays later security updates. Validate a later build against the engineering workbook before removing the target or resuming updates.

    Known-issue status

    Microsoft’s September 2026 Excel for Windows known-issues list does not identify a Version 2910/2911 “ran out of resources” regression.^5^ The November 2026 Office update information also does not document this specific regression.^6^

    Therefore, the timing and successful rollback are strong regression evidence, but they do not establish a publicly confirmed known issue.

    Isolate and escalate the Excel failure

    Test the failing build on:

    1. The affected workbook.
    2. A new blank workbook with a small calculation.
    3. The affected workbook with nonessential COM/Excel add-ins disabled.

    Excel resource errors are generic. Microsoft specifically identifies recalculation, VBA, excessive formulas, shapes, PivotTables, macros, charts, add-ins, 32-bit Excel, and competing memory usage as possible triggers.^7^

    Have a Microsoft 365 administrator open Microsoft 365 admin center → Support → Help & support and submit:

    • Full working and failing builds and update channel
    • Affected-device count and 32/64-bit Office architecture
    • Exact reproduction steps
    • Sanitized copy of the workbook/tool
    • Screenshot and exact error text
    • Excel/Application events from Event Viewer → Windows Logs → Application
    • Results on a blank workbook and with add-ins disabled
    • Business-impact severity

    Request escalation to the Excel product team if the same workbook consistently works on the pinned build and fails on 2910/2911. Only Microsoft Support and Excel engineering can confirm an unpublished regression and provide or schedule a permanent product correction.


    References

    1. Pause and rollback
    2. Configure update settings for Microsoft 365 Apps
    3. Microsoft 365 Apps for enterprise
    4. Configuration options for the Office Deployment Tool
    5. Fixes or workarounds for recent issues in Excel for Windows | Microsoft Support
    6. November 2026 updates for Microsoft Office | Microsoft Support
    7. How to troubleshoot "available resources" errors in Excel
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.