As reported by BleepingComputer, Microsoft continues to investigate a persistent bug causing Copilot and Copilot Chat buttons to vanish from Classic Outlook for Windows after upgrade to build 20026.20182 and higher. While this may read as a minor UI inconvenience, Shield53 views it as a meaningful signal of the operational fragility introduced when AI capabilities become deeply embedded in mission-critical productivity software.

Key Takeaway: While this may read as a minor UI inconvenience, Shield53 views it as a meaningful signal of the operational fragility introduced when AI capabilities become deeply embedded in mission-critical productivity software.

Why This Matters Beyond a Missing Button

The root cause Microsoft identified — Outlook's inability to locate the MAPI property PR_PROFILE_USER_SMTP_EMAIL_ADDRESS_W within the null profile section — is instructive. This is not a cosmetic rendering issue. It is a profile-level identity resolution failure that prevents the Copilot component from persisting settings. In practical terms, Outlook cannot determine which user identity to bind the Copilot experience to, so it silently removes the entry point rather than risk operating in an ambiguous context.

For security teams, this pattern should sound familiar. When identity-bound features fail silently rather than degrading visibly, users adopt workarounds that may bypass governance controls. An executive who cannot access Copilot in their desktop client may pivot to the web version, a personal device, or an unsanctioned AI tool — each representing a different data exposure profile.

The absence of a security feature is itself a security event, even when the vendor frames it as a product bug.

The Kaspersky Conflict Deserves More Attention

BleepingComputer also notes a separate but concurrent issue: Classic Outlook crashes on systems running Kaspersky Antivirus, tied to the Mail Checker module mcou.dll and logged as Event 1000 in the Application log. This is the more operationally significant item for defenders.

Endpoint security products that inject into email clients occupy a privileged position. When that integration causes instability, organizations face a forced choice between email availability and endpoint protection coverage. Shield53 has observed this pattern repeatedly across major EDR and antivirus vendors — the MAPI hooking layer is fragile, and Microsoft's frequent Outlook updates regularly break third-party integrations that rely on undocumented or semi-documented extension points.

Who Is Affected

The Kaspersky Conflict Deserves More Attention
Enterprise M365 Copilot license holders using Classic Outlook for Windows on build 20026.20182+
Organizations with mixed Outlook deployments where policy has not standardized on New Outlook or OWA
Kaspersky-protected endpoints running Classic Outlook, particularly in regions where Kaspersky remains widely deployed
IT support teams facing duplicate ticket volumes from two distinct Outlook bugs landing simultaneously

Shield53 Recommendations

  • Apply the documented workaround now: Enable Show Apps in Outlook via File > Options > Advanced > Outlook panes. This restores Copilot entry points without requiring a profile rebuild.
  • For affected power users: Create a new Outlook profile rather than repeatedly toggling settings. Profile corruption at the MAPI property level rarely self-heals.
  • Accelerate New Outlook evaluation: Classic Outlook is on a finite support timeline. Each successive bug like this strengthens the case for migration planning rather than reactive patching.
  • Instrument the Kaspersky crash: If you operate Kaspersky-protected endpoints, query Application log Event ID 1000 for Outlook faulting modules. Do not wait for user reports — proactive detection of mcou.dll-related crashes lets you engage Kaspersky support with data in hand.
  • Communicate Copilot fallback paths: Explicitly direct users to OWA or the standalone Copilot app rather than leaving them to find their own alternatives. Unsanctioned AI tool adoption accelerates precisely when sanctioned tools silently fail.
  • Track build-level regression risk: Add Outlook build numbers to your change management telemetry. The transition from 20026.20182 should be flagged in your environment inventory so future regressions can be correlated quickly.

Broader Implication

Microsoft is embedding AI into the deepest layers of its productivity stack — MAPI, profile sections, identity resolution. That integration surface is now a dependency for both user experience and, increasingly, for security features like Copilot-mediated phishing analysis and content scanning. When that surface breaks, the impact is not just lost productivity. It is lost detection capacity and user drift toward unmanaged channels. Defenders should treat AI feature availability as an operational metric, not a cosmetic concern.