Click a Windows 11 notification for a new email. In Outlook Classic the message appears instantly. In the new Outlook the app launches, the inbox loads, and then users wait. Ten seconds. The contrast is stark. And it highlights deeper architectural choices at Microsoft.
Windows Latest first documented the issue on June 15, 2026. Its tests showed the new Outlook opening from the Start menu at speeds close to Classic. But notification handling told a different story. Ignore the banner, launch the app manually, and find the email yourself. That path finishes in under five seconds. The notification route? A full ten. Windows Latest called it ridiculous. Even for Microsoft.
The reason sits in the code. New Outlook runs as a WebView2 container. It loads Outlook.com inside an Edge browser engine. That brings ten separate processes visible in Task Manager. WebView2 Manager. Multiple utility processes. GPU process. Service worker. Each one must wake from suspension when a notification arrives. Classic Outlook operates as a single native Win32 process. No such overhead.
Memory numbers reinforce the gap. New Outlook idles between 490 and 636 megabytes of RAM depending on mailbox size. Classic sits at 117 to 148 megabytes. CPU at idle runs about 4 percent for the new version and under 1 percent for the old. These figures come from simultaneous runs on the same machine. The differences compound on lower-end hardware or systems with many accounts.
But performance complaints stretch back further. A November 2025 How-To Geek review kept the new app under observation for six months. Load times ranged from eight to twelve seconds for basic startup. Simple clicks to open messages or apply filters introduced one-second stutters. RAM averaged 600 megabytes and peaked at 1.2 gigabytes even without add-ins or heavy calendar use. The fan spun up. Classic stayed in the 300-to-400-megabyte range. How-To Geek described it as a productivity blocker.
Microsoft has pushed updates to close feature gaps. A June 7, 2026 article from Windows Latest detailed 15 productivity additions designed to lure Classic holdouts. Pin emails. Snooze messages. Multiple categories. Sweep rules. Schedule send. Easier folder sharing. Enhanced calendar and meeting tools including RSVP. Save custom calendar views. Meeting filters and search. Access to recordings and transcripts. Hide events. Edit recurring series. Dark mode and theme options. Account renaming. Custom shortcut styles. Many of these already existed in Classic. The company still lists them as reasons to switch. Windows Latest noted that the new version feels slower and buggier. It reported Microsoft had admitted the app was not ready for primetime and delayed forced enterprise adoption until March 2027.
Offline capability reveals the same roots. New Outlook is a web app by design. It reaches servers for most operations. Classic caches aggressively in local OST files. Microsoft rolled out partial offline support in 2025 for reading saved emails and calendar entries. Attachment handling while disconnected arrived for all accounts in April 2026. The app now stores up to 180 days locally with options to extend to one or two years. It uses a local user data folder that consumes extra disk space. Yet the experience still falls short of native caching. A follow-up report on June 18, 2026 observed that Microsoft refuses to rebuild as a fully native application because certain enterprise features demand deeper integration. Windows Latest concluded the architectural commitment limits what updates can achieve.
Developers have seen similar patterns elsewhere. WebView2 wrappers in other apps produce high memory use. WhatsApp on Windows 11 reached 1.2 gigabytes after its transition. Microsoft has tested a Delayed Message Timing API announced in December 2025 to diagnose WebView2 performance. Testers have not observed it applied to Outlook notification flows. Official documentation on WebView2 best practices from Microsoft acknowledges past issues with memory leaks and CPU spikes but notes improvements in newer runtimes. Troubleshooting guides recommend profiling tools and testing with simplified content.
Enterprise customers appear to be voting with their workflows. The 2027 delay for mandatory migration suggests internal recognition that the new client needs time. Power users who triage email from notifications or manage multiple shared mailboxes report sticking with Classic. Microsoft continues to support it through April 2029. Recent Microsoft support pages list ongoing fixes for both versions. Classic receives updates addressing CPU spikes during typing and slow attachment saves. New Outlook sees incremental gains in search and shared mailbox handling.
The notification delay itself is more than an annoyance. It changes behavior. Users learn to ignore banners and open the app directly. Or they keep Classic installed alongside. Side-by-side testing makes the choice obvious for speed-focused tasks. One video from the original report shows the new Outlook launching the inbox and then pausing before displaying the selected message. Another demonstrates the faster manual route. The gap persists even after months of updates that improved startup from the taskbar.
So Microsoft faces a choice. Continue layering features onto the WebView2 foundation while hoping optimizations close the experience gap. Or accelerate the shift toward WinUI native components that the company has publicly committed to developing. A Rudy Huyn-led team focused on native Windows apps surfaced in early 2026. Whether that effort produces a faster Outlook remains unclear. For now the data points to an app that launches quickly enough but stumbles when users expect instant context from the notification center.
Industry observers on X echoed the findings within hours of the report. Posts highlighted the WebView2 process chain and questioned the payoff of convergence if daily friction increases. One developer summarized it simply. Shipping a WebView2 wrapper to replace a native Win32 app goes exactly how you would expect. The conversation continues as Microsoft ships more monthly updates and enterprises prepare migration plans that now extend well into 2027.
WebProNews is an iEntry Publication