Microsoft has slashed the time it takes for the New Outlook app to open an email when you click a Windows notification. In a quiet performance update, the delay dropped from around 10 seconds to about 5 seconds on version 1.2026.713.100, as confirmed by testing from Windows Latest. The fix is welcome, but it still falls far short of the near-instant response users get from the decades-old Classic Outlook client.

What Actually Got Faster

The improvement is not a flashy new feature. There’s no banner in the app, and Microsoft’s public changelog offers only vague references to “various fixes to functionality and performance” for July 2026. But the difference is measurable. When you click a new email alert in Windows, the New Outlook app now launches, displays your inbox, and then navigates to the relevant message in about five seconds—half the time it took just weeks ago.

Windows Latest’s June tests had shown a painful 10-second wait, during which the app would first load the main window before finally jumping to the email that triggered the notification. In some cases, it was actually faster to open Outlook manually from the Start menu and click the message yourself—a workflow that completely undermined the purpose of a notification.

Now, at five seconds, the experience is less maddening, but it’s still not good. Classic Outlook opens the correct message immediately, with no preamble. For an interaction that should feel instant—you tap a notification to see what just arrived—any delay beyond a second or two disrupts your flow.

Why Speed Matters More Than You Think

Notifications are an interruption mechanism. They promise a shortcut: see the alert, click it, and jump straight into the relevant context. When that jump takes five seconds, your brain has already switched tasks. You’ve glanced away, you’ve lost your place—maybe you’ve even forgotten why you clicked. That cognitive disconnect is the real cost here.

For home users who check email casually, a five-second wait might be an occasional annoyance. But for professionals handling dozens or hundreds of emails a day, the cumulative effect is substantial. Salespeople, support teams, executives, and anyone who relies on real-time alerts will notice the lag. And the underlying architecture suggests it may never truly go away.

New Outlook is built on a web-based foundation, using Microsoft Edge WebView2 to render much of its interface. It runs as multiple processes in Task Manager—sometimes ten or more—consuming 490 MB to 636 MB of RAM at idle, compared to Classic’s 117 MB to 148 MB. That web app ancestry gives Microsoft flexibility to roll out updates rapidly and unify the experience with Outlook on the web, but it also introduces overhead that a native Win32 application simply doesn’t have.

A Month of Quiet Fixes and Feature Catch-Up

The notification speed bump didn’t happen in isolation. Over the past several weeks, New Outlook has quietly addressed a range of pain points that had kept users clinging to the classic client. PST file support, for instance, is now functional—though with an important caveat. You can open .pst archives in New Outlook, read their contents, and even drag messages between folders, but you still need Classic Outlook installed on the same machine to actually load the file. That dependency won’t disappear until Microsoft ships a bulk import tool, which is planned but not yet available.

Offline access has also improved. New Outlook can now cache email, calendar items, and contacts for use when you’re disconnected. You can read, draft, and search messages, and even work with attachments. The default sync window is 12 months, but you can tweak it—bearing in mind that a longer cache means longer startup times.

Quick Parts, the reusable text snippets feature beloved by power users, arrived in early July. And Planner integration started rolling out in mid-July, letting you manage tasks without switching to Teams. These additions make New Outlook more viable for daily use, but they don’t address the core performance problem that the notification delay exemplifies.

The Looming Migration

Here’s the timeline you need to know. Microsoft’s published roadmap says that Classic Outlook will be supported until at least 2029, so you’re not being forced off it tomorrow. But the company’s migration strategy is already in motion. In an opt-in phase, users can try New Outlook voluntarily. Next comes an opt-out phase, where New Outlook is enabled by default but you can switch back. Finally, a cutover phase will make the switch permanent—and Microsoft has signaled that this will start for some users as early as March 2027.

For IT administrators, the tools to manage this transition are already live. Group policies can control whether New Outlook appears, and a separate policy can set a retry interval if users keep reverting to Classic. You can also prevent the automatic migration entirely for now. But the clock is ticking, and Microsoft’s direction is clear: New Outlook is the future.

What Should You Do Now?

If you rely on instant notification response—especially in a fast-paced job—stick with Classic Outlook for the time being. It’s fully supported, it’s fast, and it doesn’t have the WebView2 overhead. Microsoft hasn’t announced any immediate plans to force a switch, and the support commitment through 2029 gives you breathing room.

For organizations, now is the time to pilot New Outlook with a small group and gather real feedback. Test exactly the scenario described here: click a notification and measure the delay. Test on hardware that reflects your fleet—lower-memory laptops, busy CPUs, older machines. If your help desk gets complaints about sluggishness, you can adjust your migration timeline accordingly.

Individuals who want to try New Outlook can toggle it on via the “Try the new Outlook” switch in the top-right corner. If you don’t like it, you can flip back to Classic just as easily. Keep an eye on the app’s version number—the notification improvement arrived in version 1.2026.713.100, but as a service-driven update, it may appear without fanfare.

The Bigger Picture

Microsoft is investing heavily in Copilot integration across Outlook, and many of the features that made Classic great—Meeting Insights, for example—are being retired or replaced by Copilot-powered alternatives that require a paid license. Meanwhile, New Outlook is steadily absorbing the productivity capabilities that Classic users expect. It’s a tale of two clients: one in maintenance mode, the other rapidly evolving but still missing that crisp, native feel.

The notification delay fix is a genuine improvement. It shows that Microsoft is listening and that the New Outlook team can deliver performance gains without a full architectural overhaul. But as long as clicking an email alert feels like a loading screen rather than an instant response, the new app will feel like a downgrade to people who depend on speed. For now, Classic Outlook remains the standard-bearer for responsiveness—and it’s not going away yet.

Outlook: Keep Watching the Changelog

Microsoft’s fast service-delivery model means that improvements can appear overnight. The notification fix wasn’t announced; it just started working faster. For Windows users, that means you should occasionally test New Outlook’s performance, even if you’re using Classic day to day. The gap is closing. Whether it closes entirely is an open question—but for many workflows, five seconds might already be good enough. For the rest, Classic is still there, and it’s still faster.