A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data
Hello @Laloux Victor
Thank you for your feedback. First, I would like to clarify that this is a user-to-user support forum. Moderators do not have access to your tenant environment, backend diagnostics, or escalation channels, so we cannot directly confirm whether a specific service incident is affecting your organization.
Regarding KB5095093, Microsoft has acknowledged a known issue where Microsoft Office applications may fail to open when launched from certain third-party applications. However, based on the troubleshooting you've already completed:
- Removal and verification of Office add-ins
- Testing Office applications in Safe Mode
the fact that the crashing/freezing behavior persists suggests there may be another factor involved. Could you help check the following on one of the affected devices?
- Microsoft 365 Apps version and build number
- Update channel (Current Channel, Monthly Enterprise Channel, Semi-Annual Enterprise Channel, etc.)
For comparison, there have been several Microsoft 365 Apps releases in late June 2026, including:
- Version 2606 (Build 20131.20112) - June 30, 2026
- Version 2606 (Build 20131.20090) - June 25, 2026
It would be useful to determine whether the issue is tied to a specific Office build. If the affected devices are not already running the latest build, you may also want to update a small test group and see whether the behavior changes. Conversely, if the issue started immediately after a recent update, consider rolling back a few affected devices to an earlier Office build to determine whether the problem is build-related.
Additionally, since the issue appears to have started around the same timeframe as recent Windows updates, you may also want to test on a small group of affected devices by temporarily reverting the most recent Windows update (where appropriate and in accordance with your organization's change-management policies) to determine whether the behavior is being triggered by an Office build, a Windows update, or the interaction between the two.
Given the scale of the impact across multiple users and devices, I would also strongly recommend opening a Microsoft support case if you have not already done so. Microsoft Support has access to backend diagnostics and can collect crash dumps, analyze telemetry, and determine whether this is related to a broader product issue or a regression in a recent build.
In the meantime, I'll continue to help as much as I can from the forum side. Please try the version/build checks and, if possible, a rollback test on a small group of affected devices, then let me know the results.
Hope this helps.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.