Microsoft has acknowledged a known issue in its June 2026 cumulative update for Windows 11 that prevents Office applications from opening when launched through certain third-party apps, leaving enterprise users and IT administrators scrambling for a workaround.
On June 9, 2026, Microsoft released KB5095051 (OS Build 28000.2269), the monthly cumulative update for Windows 11, version 26H1.
The update was designed to bundle the latest security patches from the June 2026 Security Update cycle, alongside quality improvements previously introduced in the May 12 (KB5089548) and May 26 (KB5089570) preview releases.
Microsoft Office Apps Fail to Launch
However, shortly after deployment, users began reporting that Microsoft Office applications, including Word, Excel, Outlook, and PowerPoint, failed to launch when invoked via third-party applications, such as document management platforms, ticketing systems, and enterprise workflow tools.
Direct launches from the Start menu or desktop shortcuts appear unaffected, isolating the issue to inter-process or shell-based launch mechanisms.
Microsoft has officially listed the bug in the Known Issues section of the KB5095051 release notes, confirming awareness of the problem. No patch or resolution timeline has been announced as of this writing.
KB5095051 introduces several notable changes beyond security fixes. Among the most significant is a security hardening modification to how Windows processes desktop.ini files, which control folder customization behavior.
While this change is unrelated to the Office launch failure, it reflects Microsoft’s broader effort to tighten low-level Windows shell security in this update cycle.
The update also refreshes AI components bundled with Windows 11, including Image Search, Content Extraction, Semantic Analysis, and Settings Model, all updated to version 1.2604.515.0.
Additionally, a servicing stack update (SSU KB5101277, Build 28000.2263) is bundled to improve the reliability of future Windows Update deployments.
A separate deployment advisory warns that dynamic update installations must include the boot.stl file used during Secure Boot validation or risk triggering error code 0xc0430001 on startup.
The Office launch failure primarily affects enterprise environments where Office applications are routinely triggered by third-party platforms such as CRM tools, help desk software, and custom business applications.
In such environments, productivity disruption can be significant. IT teams relying on automated deployment pipelines should consider pausing the KB5095051 rollout until Microsoft issues a resolution.
Administrators managing custom Windows images should also use the Update WinPE script or manually copy the boot.stl file from Windows\Boot\EFI to prevent Secure Boot validation failures during deployment.
IT administrators are advised to audit any third-party integrations that invoke Office apps via shell commands or COM automation, and to test deployments in a staging environment before a broader organizational rollout.
Organizations with a high level of dependence on third-party Office integrations should consider deferring the update entirely until Microsoft confirms a fix. Microsoft has not yet confirmed a root cause or issued an out-of-band patch.
Affected users can monitor the Windows Release Health Dashboard at learn.microsoft.com/windows/release-health/ for real-time status updates.
Follow us on Google News , LinkedIn and X to Get More Instant Updates. Set Cyberpress as a Preferred Source in Google.