Microsoft’s iOS edition of Excel has been effectively unusable for many users since mid‑October after an update introduced a fresh “Liquid Glass” interface, with widespread reports of freezes, crashes and UI elements that no longer respond to taps — and the company’s public response has been thin at best. Users across Microsoft’s support forums, Reddit and the Apple App Store report the same pattern: Excel for iPhone and iPad started failing after the October 13, 2025 release of version 2.102.1, and follow‑up builds have not, at time of writing, fully cured the problem.
Background / Overview
Apple’s iOS 26 and iPadOS 26 introduced a new visual motif dubbed
Liquid Glass, and Microsoft shipped Excel version 2.102.1 on October 13, 2025 with explicit release‑note support for that design refresh. The App Store listing for Excel confirms the timing and the marketing language: the October 13 update added “an all‑new design with Liquid Glass effects” and promised a “refreshed look and smoother navigation.” Within days users began reporting freezes, rendering glitches and input failures that made the app unusable for routine tasks such as creating a new workbook or searching within a spreadsheet. Microsoft’s own support forum threads show an active stream of bug reports beginning around October 17, 2025, with many users identifying Excel version 2.102.1 as the precipitating change and others confirming that later builds (some users referenced 2.102.2) did not fully restore normal function. Community moderators and independent advisors on the Microsoft Q&A page offered workarounds — notably toggling network connectivity (airplane mode), using Excel through the Microsoft 365 / Copilot preview surfaces, or falling back to Excel Online — but no formal vendor post‑mortem or immediate hotfix timetable was provided in the public thread. What started as scattered user complaints quickly aggregated into large Reddit threads and App Store reviews, giving the appearance of a systemic regression affecting many devices and iOS builds. By the weekend of October 18–20, troubleshooting threads had compiled a range of temporary workarounds and symptoms — blank sheets while scrolling, UI tap targets not responding (notably the “+ Create” template button), and entire sessions freezing a few seconds after opening a workbook.
What users are seeing: symptoms and patterns
Typical failure modes
- The app freezes or becomes unresponsive within a few seconds of opening a file, sometimes leaving the workbook visually blank or partially rendered.
- Touch targets appear to misbehave: users report that the “+ Create” menu does not respond, preventing creation of new spreadsheets from templates.
- Search and scrolling can trigger hangs or crashes, particularly in larger or more complex workbooks.
- Problems appear across both iPhone and iPad hardware and across multiple iOS 26.x builds in user reports; some older devices appear, anecdotally, to be less affected in certain cases.
Common temporary workarounds observed in community reporting
Community troubleshooting has converged on a handful of pragmatic but crude workarounds that
can restore limited functionality temporarily:
- Toggle network connectivity: switching to airplane mode or disabling Wi‑Fi while the app is frozen and then re‑enabling it can unstick the UI for a session. This trick is repeatedly reported and appears to work for a subset of affected users.
- Use the Microsoft 365 / Copilot preview surface or Excel Online in a browser as a functional fallback until the native app is repaired. Several users found the Copilot application can open Excel files without freezing.
- Reset cloud settings for the Excel app (Settings → Excel → Reset → Reset Cloud Settings) or reinstall the app; reports on these were mixed — some users saw transient relief, others saw no change.
These are stop‑gaps, not fixes; for users who depend on Excel on mobile for daily record‑keeping or field work, the disruption is real and immediate.
Verifying the timeline and technical facts
- App Store release notes verify that Excel version 2.102.1 was published on 13 October 2025 and explicitly advertised the new Liquid Glass home experience and UI polish. That App Store listing is the canonical public evidence for the release date and the UI changes.
- Microsoft’s customer forum threads include multiple posts dated October 17–23, 2025 reporting freezing on devices running Excel v2.102.1 and later builds such as 2.102.2. The threads show both symptom descriptions and suggested mitigations, but no vendor‑published fix timeline in those posts.
- Independent reporting aggregated by outlets such as The Register tracked the same sequence: October 13 release → user reports mid‑October → community troubleshooting and App Store reviews highlighting widespread failures.
These three independent traces — App Store metadata, Microsoft Q&A threads, and third‑party reporting — paint a consistent picture on dates, versions and the onset of the problem.
Why this likely happened (analysis and hypotheses)
There is no official engineering post‑mortem available in public channels, so the following are informed hypotheses grounded in how complex mobile app rollouts typically fail:
- UI/OS compatibility regressions. iOS 26 introduced new visual and UI plumbing for Liquid Glass effects. Re‑theming, layout changes and animation pipelines can expose subtle timing and rendering bugs, especially on cross‑platform or shared UI stacks where pixel shaders, gesture recognizers and layout invalidation behavior changed between OS versions. The App Store notes explicitly tied the Excel change to iOS 26 visual features, which makes a compatibility regression a plausible primary vector.
- Rendering or resource exhaustion. Reports that scrolling or searching in larger files triggers the app to go blank or hang suggest a rendering or memory‑pressure bug. Mobile spreadsheet renderers are performance‑sensitive; a regression in view invalidation, cell virtualization, or asynchronous paint pipelines can cause the UI thread to stall and the app to appear frozen.
- Network/channeled telemetry interactions. The fact that disabling network connectivity or using airplane mode sometimes unblocks the app suggests a race or deadlock involving network I/O, cloud sync, or online content fetching. If the UI waits (synchronously or poorly guarded) on a network operation, a misbehaving endpoint or changed API contract could stall the UI. Community posts that Excel unfreezes after a Wi‑Fi toggle make this hypothesis credible in at least a subset of cases.
- Rapid release cadence and integration complexity. Modern Office mobile clients are not monolithic; they embed multiple engines (renderers, sync, AI/ML components, telemetry), share code across platforms, and are tested across a matrix of OS builds and device models. Any slip in integration testing — for example, if a UI refresh was merged late and not fully validated on iOS 26 devices — can hit production users quickly because mobile rollouts are typically staged but still reach large numbers of phones fast. Community chatter about staged previews and Copilot tie‑ins in broader Microsoft mobile strategy suggests that feature velocity may be prioritized, increasing regression risk.
These are
probable causes rather than confirmed facts. Without Microsoft’s internal bug reports, crash telemetry or a formal fix note the root cause(s) cannot be established definitively. Where claims are speculative, they are labelled as such.
What Microsoft has said (and what it hasn’t)
Publicly, Microsoft has not posted a detailed incident report on the Excel for iOS regressions in the channels where community posts are most active. The company’s App Store release notes for 2.102.1 contain the marketing copy about Liquid Glass and performance, but not engineering details or known issues; Microsoft has not published a visible, authoritative timeline for a fix in the public threads sampled by journalists and users. The Microsoft Q&A threads show community‑level responses and moderator advice but no official engineering post‑mortem in the same thread. A measurable response is visible in the community: Microsoft Q&A moderators and some advisors advised users to try standard remedies (reinstall, reboot, use Excel Online), and some users reported intermittent improvement after later app updates or server‑side changes — but those are user reports, not company acknowledgments of a root cause or permanent fix.
Practical guidance: what affected users should do now
For users who rely on Excel on iPhone or iPad, the immediate goal is continuity of work while a vendor fix arrives. The following steps are compiled from community reporting and official forum suggestions; they are pragmatic mitigations, not guaranteed cures.
- Try Excel Online (browser) as the first fallback. Mobile Safari or any modern browser can open and edit spreadsheets; this is slower but avoids the native app regression in many reports.
- If the native app freezes, toggle network connectivity: enable airplane mode (or switch off Wi‑Fi) while the app is frozen; wait a few seconds and then re‑enable the network. This trick has been repeatedly reported to restore functionality for some users.
- Use the Microsoft 365 / Copilot preview app to open files as a temporary path — multiple community posts report the Copilot surface can open and allow editing without freezing. This is a workaround where Copilot is installed and available.
- Reset Excel cloud settings in iOS Settings → Excel → Reset → Reset Cloud Settings; several community posts report that this can stop repeated freezes for some users. Results are mixed.
- Reinstall the app (delete + re‑download) after rebooting the device. Some users saw a temporary benefit; others did not.
- If you manage enterprise devices, instruct users to use the browser-based Excel or deploy a message via your MDM channel warning users to avoid the native app until the vendor resolves the issue. Consider temporarily blocking the app from managed devices if workarounds are insufficient.
If the app is business‑critical, prepare to escalate via Microsoft support channels and capture logs/crash reports to aid vendor triage. Public community threads also sometimes reveal per‑device or per‑iOS‑build idiosyncrasies; include device model, iOS build, Excel version and a concise reproducible summary when reporting.
Broader context and risks for enterprises
This incident is more than a consumer annoyance. Mobile productivity apps like Excel are embedded in enterprise workflows: field engineers, sales teams, logistics staff and many other roles use Excel on phones and tablets as part of daily operations. A widely distributed regression that breaks mobile editing or sync can have cascading operational impacts — missed data, delayed invoices, failed reconciliations and unnecessary support overhead.
There are two explicit enterprise‑level risks here:
- Operational disruption: Organizations that assumed mobile access parity may find workers offline or forced onto slower browser flows, reducing responsiveness and increasing support costs. Large‑scale rework or process changes may be needed for teams that rely on on‑device Excel editing.
- Trust and governance: When vendor updates disrupt business processes repeatedly, IT teams face pressure to micro‑manage app updates (pin versions, disable auto‑update policies) and to build fallback communication plans. These measures increase administrative overhead and erode user trust in default update policies.
IT leaders should monitor Microsoft’s support channels and the official Message Center for tenant‑level advisory updates, and consider an urgent communications push to users about temporary mitigations and safe workflows.
What this episode says about software quality at scale
The Excel regression has re‑ignited debates about modern software engineering: fast release cadences, large shared codebases, AI‑assisted coding, outsourcing, and reduced test coverage are often cited as causes for higher regression rates. Public commentary has speculated about the role of AI‑generated code and organizational decisions (staffing, testing) in recent high‑profile incidents. Those arguments have merit as hypotheses, but they remain speculative without vendor telemetry.
Two points are important to separate:
- Shipping faster and shipping safely are tradeoffs that can be managed with investment in automation, robust test harnesses and conservative staged rollouts. The industry trend toward continuous delivery heightens the need for thorough platform compatibility testing on major OS shifts (like iOS 26).
- Claims about the proportion of code authored by AI are difficult to verify and are not direct proof of regression causality. Reported percentages or executive comments may be anecdotal, aggregated and contextualized in many ways; without explicit engineering data from a vendor, such claims should be treated as unverified indicators rather than proof. Where public outlets repeat such figures, they should be presented with caution. (In this incident, press coverage has echoed various theories; a formal Microsoft statement detailing root‑cause and mitigation is the only way to move from hypothesis to fact.
How Microsoft should respond (best practices)
To restore user trust and limit operational fallout, the vendor response should follow a clear incident‑management playbook:
- Publish an incident advisory that acknowledges the regression, lists affected app versions and OS builds, outlines known workarounds and gives an expected timeline for a hotfix or rollback. Transparency matters for enterprises and power users.
- If a simple rollback to a known‑good build is feasible and safe, consider staging an App Store reversion (or expedited hotfix) rather than incremental patching that may leave users in limbo. Community posts indicate that multiple incremental updates did not immediately resolve all issues.
- Publish a post‑mortem once the issue is resolved explaining root cause, corrective actions and steps to prevent recurrence. This builds trust and provides signal to enterprise engineers about the depth of the problem and the fixes applied.
- Improve canary‑release testing and expand device/OS coverage for visual/UX changes, ensuring new platform motifs like Liquid Glass receive targeted render and gesture tests on representative hardware.
These are standard engineering hygiene steps but matter more than ever when a single mobile client is used by millions of people.
What we verified and what remains unverified
Verified:
- Excel for iOS version 2.102.1 was released on 13 October 2025 with Liquid Glass UI changes, per the App Store release notes.
- Widespread user reports of freezing and crashes began surfacing mid‑October and have been aggregated on Microsoft’s support forums, Reddit and App Store reviews.
Unverified / cautionary:
- Any single definitive root cause for the regression (e.g., “AI‑generated code” or “testing layoffs caused the bug”) cannot be substantiated from public evidence. These remain plausible hypotheses but require internal vendor telemetry and confirmation to be treated as fact. Public circulation of uncorroborated claims should be labelled accordingly.
Final assessment and recommendations
The Excel for iOS outage is a textbook example of how a UI refresh tied to a new OS can ripple into a production incident, especially for complex, data‑heavy apps like spreadsheets. The symptom set — rendering hangs, search/scroll freezes and unresponsive template buttons — points to a likely combination of rendering and network‑interaction regressions, and community workarounds (airplane mode, Copilot app, Excel Online) provide short‑term relief but are not substitutes for an engineering fix.
For individual users: use Excel Online, try the documented network toggle and Copilot workarounds, and report detailed bug logs to Microsoft if you rely on Excel for critical workflows. For IT leaders: push a firm communication to end users, consider temporarily restricting the native client via your MDM if disruption is severe, and prepare to support browser‑based editing as the default while the vendor resolves the issue.
Transparency and a rapid, clearly articulated remediation plan are the keys Microsoft must deliver now. Users deserve an explanation, a timeline and — most importantly — a tested fix. Until Microsoft publishes its engineering findings and a robust patch, community threads and user reports remain the best real‑time signal of the problem’s scope and the efficacy of interim workarounds.
Quick checklist for affected users
- Open the spreadsheet in Excel Online (browser).
- If native app freezes: toggle airplane mode → wait 10s → re‑enable network.
- Try opening the file via the Microsoft 365 / Copilot app if installed.
- If you’re an admin: communicate fallback options and capture device/OS/version details for escalation.
The situation remains fluid. Users and administrators should monitor Microsoft’s official channels and the App Store for a patched build or an advisory that confirms root cause and remediation.
Source: theregister.com
Microsoft Excel for iOS is DOA for many after shoddy update