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:
- Sign in to the Microsoft 365 Apps admin center with Cloud Update permissions.
- Open Cloud Update → Monthly Enterprise.
- Select Pause updates and verify that Rollout information changes to Paused.
- Select Actions → Roll back devices.
- Choose the previously working version/build.
- Target the affected device names, or a Microsoft Entra group containing user objects. Cloud Update maps those users to their eligible devices in Inventory.
- 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:
- In Group Policy Management Console, open
Computer Configuration → Policies → Administrative Templates → Microsoft Office 2016 (Machine) → Updates.
- Enable Target Version and enter the complete working build number.
- If immediate containment is required, also configure Enable automatic updates appropriately for the affected pilot group.
- On a test device, run this from an elevated Command Prompt:
gpupdate /force
- Confirm that policy processing completes successfully.
- 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:
- The affected workbook.
- A new blank workbook with a small calculation.
- 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
- Pause and rollback
- Configure update settings for Microsoft 365 Apps
- Microsoft 365 Apps for enterprise
- Configuration options for the Office Deployment Tool
- Fixes or workarounds for recent issues in Excel for Windows | Microsoft Support
- November 2026 updates for Microsoft Office | Microsoft Support
- How to troubleshoot "available resources" errors in Excel