Microsoft's latest optional cumulative update for Windows 11, released on June 23, 2026, carries a known issue that may prevent third-party applications from launching Microsoft Office programs via OLE automation. The preview update, tracked as KB5095093, affects the most recent feature updates—versions 25H2 and 24H2—pushing OS builds 26200.8737 and 26100.8737, respectively. The bug, acknowledged in the update’s release notes, means that certain line-of-business tools and productivity add-ons that rely on programmatic control of Word, Excel, Outlook, or other Office apps may encounter errors or fail silently. For IT administrators managing Windows fleets, this could translate into disrupted workflows and unexpected support calls.

While the update is not security-critical and therefore not installed automatically for most users, those who manually check for updates or deploy previews in test rings will see it offered. Microsoft typically releases these non-security preview updates in the third or fourth week of the month to allow a head start on testing before the following month’s Patch Tuesday. KB5095093 is no exception, arriving as the June 2026 preview and containing a mix of quality improvements that will later be bundled into the July 2026 mandatory update—unless the OLE regression forces a change in plans.

Understanding OLE Automation and Why It Still Matters

Object Linking and Embedding (OLE) automation has been a cornerstone of Windows desktop integration since the 1990s. It allows one application to programmatically control another through Component Object Model (COM) interfaces. In practice, this means a customer relationship management (CRM) system can open a Word document, populate a template, and email it to a client without any user interaction. Accounting software might export data directly into an Excel spreadsheet, and custom scripts can generate Outlook calendar invitations from database records.

Despite the shift toward cloud-based APIs and Office add-ins built with web technologies, OLE automation remains deeply embedded in enterprise environments. Thousands of third-party applications—from legacy ERP systems to modern desktop utilities—still instantiate Office applications via CreateObject() calls in VBA, .NET, or C++. The breakage introduced by KB5095093, therefore, has the potential to ripple across procurement, finance, legal, and healthcare sectors where document automation is critical.

Which Systems Are Affected

The known issue is limited to Windows 11 version 25H2 (build 26200.8737) and version 24H2 (build 26100.8737) after installing KB5095093. These are the current and previous feature updates of Windows 11, representing the newest hardware and software configurations. The original Windows 11 release (21H2), as well as versions 22H2 and 23H2, are not impacted because the update does not apply to those builds. Additionally, Windows 10 is entirely unaffected.

For context, version 25H2 is the latest major Windows 11 refresh, offering interface enhancements, AI-powered features, and under-the-hood performance tweaks. Version 24H2, while slightly older, remains widely deployed in corporate settings. The preview update’s broad reach across two principal Windows 11 versions underscores the potential scale of the problem, even if the update is optional.

How the Failure Manifests

According to Microsoft’s known-issue listing, the problem occurs specifically when third-party applications try to launch Office via OLE. Office apps themselves continue to work normally when opened directly by the user. The exact error varies depending on the calling application’s error handling: some might display a generic “automation error” or “class not registered” message, while others could time out or hang indefinitely.

For example, a .NET application that uses Type.GetTypeFromProgID(\"Excel.Application\") may return null or throw a COMException. A VBA macro invoking GetObject(, \"Word.Application\") might fail to attach to a running instance. In more severe cases, the calling process could crash if it does not properly handle the exception. IT support desks are already fielding reports from early adopters who installed the preview update on test machines, with symptoms pointing to a breakdown at the COM activation layer.

Microsoft’s Acknowledgment and Investigation

Microsoft included the issue in the release health dashboard for KB5095093, classifying it as a “known issue.” The company states: “After installing this update, some third-party applications may fail to launch Microsoft Office applications when using OLE automation.” No root cause is publicly detailed yet, but early analysis from community experts suggests the update may have altered COM object permissions, changed the server registration for Office’s local server process, or introduced a new security mitigation that blocks certain inter-process activations.

Crucially, Microsoft has not provided an immediate fix, stating the issue is “under investigation.” This is standard procedure for preview updates; the company often gathers feedback and regression data before rolling fixes into the subsequent security release. However, the absence of a workaround in the original advisory leaves affected users with few options.

Available Workarounds

For those who depend on OLE automation and already installed KB5095093, the primary mitigation is to uninstall the update. The process is straightforward:

  • Navigate to Settings > Windows Update > Update history > Uninstall updates.
  • Locate KB5095093 in the list of installed updates, select it, and click Uninstall.
  • Restart the computer when prompted.

IT administrators managing devices through Windows Server Update Services (WSUS), Microsoft Endpoint Configuration Manager, or Microsoft Intune can also decline the update or remove it from deployment rings. For machines enrolled in Windows Update for Business, the Uninstall option should be available for up to 10 days after install, after which the OS may clean up files unless longer deferral periods are configured.

If uninstalling is not feasible—perhaps because the update addresses another critical issue—then organizations may need to isolate the affected applications and explore alternatives, such as using Office’s web-based APIs where applicable, or wrapping OLE calls in robust retry logic that falls back to user prompts.

Historical Context: A Pattern of Automation Breakages

This is not the first time a Windows update has disrupted Office automation. In November 2023, a security patch caused Excel to crash when invoked via COM from .NET applications, leading to emergency hotfixes. In early 2024, a Windows 11 update momentarily broke VBA macro execution from network locations due to a change in attachment manager policies. Even further back, a 2018 Windows 10 update reset DCOM permissions, causing widespread application failures.

These recurring issues highlight the fragile web of dependencies that sustains enterprise workflows on Windows. Microsoft’s rapid release cadence for Windows 11—coupled with its practice of delivering preview updates to test upcoming changes—means regressions can slip through if not caught by the Insiders program or enterprise validation rings. For IT pros, the lesson is clear: treat every optional update as a potential source of disruption, no matter how innocuous the listed improvements.

Broader Impact on Businesses and Workflows

Companies that rely on document automation are particularly vulnerable. Consider a legal firm where a custom case-management system automatically generates letters in Word, or a hospital where lab results are inserted into Excel spreadsheets for analysis. If installs of KB5095093 reach production environments unchecked, the result could be hours of lost productivity and delayed services.

Even businesses that do not directly employ OLE automation might be affected through commercial off-the-shelf software. Many accounting packages, data visualization tools, and report generators integrate with Office under the hood. A silent failure can go unnoticed until a critical report fails to send, creating a cascade of troubleshooting.

Microsoft’s decision to label the update as “optional” mitigates immediate blowback, but the true test will come in July’s mandatory Patch Tuesday, when the same code—potentially unfixed—could be forced onto all supported Windows 11 machines. Enterprises should actively monitor the known-issue page and plan a strategy to block or defer the July update if the regression persists.

Guidance for IT Administrators

  1. Block KB5095093 in production: Use group policy, WSUS, or Intune to prevent deployment immediately. If any machines have already installed it, initiate a rollback.
  2. Test with representative LOB apps: In a sandboxed environment, install the update and exercise all critical third-party applications that interact with Office. Document any failures and report them to Microsoft via the Feedback Hub or support channels.
  3. Communicate with software vendors: Reach out to vendors of key applications to see if they are aware of the issue and whether they have patches or configuration changes that can bypass the bug.
  4. Prepare a fallback plan: Identify which machines absolutely require OLE automation and ensure they stay on the previous build until a fix is confirmed. Consider whether business processes can be temporarily switched to manual operation.
  5. Monitor Microsoft’s release health dashboard: The KB5095093 article (linked below) will be updated with mitigation steps or a resolution timeline. Subscribe to notifications.

Looking Ahead: The Road to a Fix

Microsoft’s typical patch cycle suggests that a correction could arrive in the following month’s cumulative update, or perhaps earlier via a standalone servicing stack update (SSU) or an out-of-band fix if the disruption gains widespread attention. For now, the company has not committed to a date. In the past, critical OLE-related bugs were often fast-tracked, but because this issue is confined to an optional preview, the urgency may be lower.

Users and administrators can lend their voice by upvoting feedback in the Feedback Hub or filing detailed support tickets. Public pressure often accelerates Microsoft’s response. Meanwhile, the Windows Insider community will likely see a fix first, with the potential for it to be backported to 24H2 and 25H2 quickly.

Preview Updates: A Double-Edged Sword

KB5095093 is a textbook example of why preview updates exist—and why they should be approached with caution. On one hand, they give IT staff a chance to validate upcoming changes and catch regressions before they become mandatory. On the other, they can introduce fresh problems that catch early adopters off guard. The balance leans heavily on diligent testing and a robust deployment ring strategy.

For individual power users who habitually click “Check for updates” to get the latest features, this bug is a reminder that preview builds are essentially beta-quality code. Unless you are prepared to troubleshoot or roll back, it may be wiser to wait for the official Patch Tuesday release, where the most egregious issues are usually ironed out.

Conclusion

The Office OLE automation failure in KB5095093 is a significant known issue that could disrupt business operations for Windows 11 users on the 24H2 and 25H2 builds. While the optional nature of the update limits its blast radius, the underlying bug will likely need to be resolved before July’s mandatory update. Organizations should take proactive steps to block the update, test their application ecosystems, and prepare rollback procedures. As always, the adage holds: when it comes to Windows updates, a little caution goes a long way.

Further details and any emerging fixes can be tracked on Microsoft’s official release health page for KB5095093, which will be updated as the investigation proceeds.