The post argues that Microsoft’s new Outlook for Windows is dramatically slower than classic Outlook at basic tasks like opening notifications, switching views, and general mailbox interaction. It frames the culprit as the move to a WebView2 shell around Outlook’s web app, and points to much higher idle memory use as a visible symptom. Readers did not really dispute that the new client feels bad. They piled on with examples from Windows 11, Teams, search, Notepad, Calculator, and File Explorer, all reinforcing the same complaint: modern Microsoft software now burns vastly more hardware for worse responsiveness.
The more useful conclusion was that the browser stack is not the real explanation. Several people pointed out that Fastmail, Gmail,
VS Code,
Tauri apps, and even Outlook in a normal browser can feel faster than the packaged desktop client. The failure looks organizational. People described bad load order, too much preloading, excessive rendering, feature accretion, and desktop shells that behave as if the UI must wait for updates, ads, telemetry, or remote checks before becoming interactive. That same pattern showed up in meeting reminders, typing lag when replying, broken browser navigation in Outlook Web, and search flows that reload or jump unpredictably.
A big chunk of the pain also comes from the enterprise stack layered on top. Multiple comments said Windows itself is often merely mediocre until
Defender,
CrowdStrike, app control, VPN, DNS filtering, and other endpoint tools turn app launches into multi-second waits. One game studio example claimed Unreal Editor started in 30 seconds with Defender disabled and nine minutes with it on, even after exclusions. That sharpened the thread’s broader point. Users blame Outlook, but a lot of modern desktop misery is the combination of heavy client software plus mandatory security middleware plus cloud-first product assumptions.
The practical consensus was bleak. Classic Outlook is still preferred because it has critical features the new client still lacks, from Public Folders and richer templates to
COM,
VBA, custom dictionaries, better offline workflows, and long-tail enterprise automations. Yet few expect Microsoft to fix the new client enough before retiring the old one. For many, that means more browser use, a move to Thunderbird or other mail clients where possible, or a broader shift to Linux or macOS for personal machines while tolerating Microsoft only where corporate infrastructure forces it.