KB5094126 Office Launch Issue: Verify the July Fix

If Word or Excel opens normally from Start but not from Zotero, accounting, audit, or dental software, test the launch path before repairing Office. Microsoft identifies an OLE Automation issue after Windows updates released on or after June 9, 2026, and says it is resolved by July 14 updates such as KB5101650.

1. Confirm the narrow symptom

Microsoft describes third-party applications that use OLE Automation to start Word, Excel, PowerPoint, Access or open their documents. The Office window or document can fail silently. Reported workflows included CCH Engagement, Workpaper Manager, Dentrix, Softdent and Zotero, though a listed product name does not prove every failure has the same cause.

Open Word or Excel directly from Start. Create a small local test file, close the app, then open that file from File Explorer. Finally repeat from the third-party workflow. Record all three results and the time. Direct success plus integration failure is the useful signature.

2. Verify the Windows version and update history

Press Windows+R, run `winver`, and record the edition, version and OS build. KB5094126 applies to Windows 11 24H2 and 25H2 builds 26100.8655 and 26200.8655. Open Settings > Windows Update > Update history and confirm what was installed rather than relying on the date the problem was first noticed.

Do not download a similarly named package from a third-party site. Windows Update should offer the cumulative update suitable for the device’s version and architecture. Managed computers may receive updates on a staged schedule, so send the build and KB list to IT.

3. The current fix is a newer Windows update

Microsoft now marks the Office launch issue resolved in Windows updates released on and after July 14, 2026, including KB5101650 for Windows 11 24H2 and 25H2. Install the latest cumulative update offered, not merely a random package with that number, because a newer cumulative update should include earlier fixes.

Restart Windows after installation. Then fully exit the third-party application and open it again; Microsoft’s July notes say restarting the affected app can typically complete recovery. Re-run direct, File Explorer and third-party launch tests in the same order.

4. What to do before the fixed update is available

The official temporary workaround was to open the Office application or document directly instead of launching it from the affected third-party app. Preserve the file in its expected location and follow the vendor’s workflow rules; do not move a database-managed document merely to bypass the integration.

For organizations, Microsoft offered a business-support mitigation. Do not apply registry snippets, replacement DLL files or scripts from forums. Do not uninstall a security update as the first action, especially on accounting and healthcare systems.

5. If Office also fails directly

If Word or Excel will not open from Start, the evidence no longer matches the narrow OLE scenario. Start Office in Safe Mode, disable add-ins one at a time, and use Apps > Installed apps > Microsoft 365 > Modify for Quick Repair or Online Repair according to Microsoft guidance. Back up templates and business data first.

A single damaged file needs a separate test. Create a new document, save it locally and reopen it. If only one file fails, keep copies before using Open and Repair. For Windows Update installation failures, use the relevant code guide rather than repairing Office.

6. Third-party application checks after Windows is current

Update the affected accounting, dental, reference or document-management application from its vendor. Confirm its exact version and whether it uses 32-bit or 64-bit Office integration. Avoid changing Office architecture during production hours; add-ins and database connectors may depend on it.

If the integration still fails, collect Event Viewer timestamps, the app log and a short reproduction: direct launch succeeds, File Explorer succeeds, third-party launch fails. Send this to the vendor and IT. This is stronger evidence than reinstalling both products without knowing which bridge failed.

7. Business rollout checklist

• Test the July or newer cumulative update on one representative device.
• Restart the device and the affected application before judging the fix.
• Test Word, Excel and the actual document workflow, not just app icons.
• Keep the June build, July build, app version and result in the change record.
• Preserve security updates and escalate through Microsoft business support when policy requires it.

For a Windows update that loops into recovery, use the WinRE and BitLocker recovery ladder. For `0x80070643`, follow the WinRE update repair. The repair guide hub covers unrelated symptoms.