New Outlook for Windows (olk.exe) v1.2026.317 / 1.2026.325 Crashes Linked to olkmain.dll

April 14, 2026 • ID: CUA-2026-006
Severity: Medium  •  Impacted Organizations: 400+ •  Vendor: Microsoft  •  App: New Outlook for Windows
Description:

Status: 🟢 Resolved • Fix Released (April 1, 2026)

We have identified an increased rate of crashes affecting the olk.exe process in New Outlook for Windows, specifically versions 1.2026.317 and 1.2026.325. This behavior began emerging at the end of March and is now visible across a growing number of environments, consistently faulting in olkmain.dll.


What is the Impact:

The crash has been observed across more than 400 organizations and is classified as medium severity. Given Outlook’s role as a primary, user-facing communication tool, instability in this process is likely to disrupt daily workflows and impact end-user productivity.


Advised Resolution:

The issue has been resolved in newer Outlook builds. Organizations should ensure that affected endpoints are upgraded to a version released after early April 2026.

Upgrading Outlook has been shown to eliminate the crash pattern associated with olkmain.dll. Earlier mitigation steps, such as clearing the local cache (olk.exe --clearLocalState), are no longer required once systems are updated.


Additional info:

This issue was traced to a race condition introduced in early March builds of New Outlook for Windows. The fix was released on April 1, 2026, and subsequent versions no longer demonstrate the crash behavior.

This finding highlights how ControlUp’s global telemetry can detect emerging issues early, often before root cause and resolution are formally communicated, and then track their resolution across real-world environments.


Vendor Response:

Update (April 2026)

Microsoft has confirmed that the olkmain.dll crash affecting New Outlook for Windows was resolved on April 1, 2026.

The issue was caused by a race condition introduced in early March. The majority of crashes were associated with olkmain.dll versions 1.2026.317.100 and 1.2026.325.600, with the last observed affected version being 1.2026.401.100.

ControlUp telemetry also confirms that newer Outlook builds no longer exhibit this crash pattern, indicating the issue is no longer widespread.