Microsoft's new Outlook takes more than 10 seconds to open an email via notifications, while Outlook Classic opens instantly on Windows 11!
The funniest part? If I ignore the notification, open Outlook manually, find the email myself, and click it, I can finish faster than the notification flow.
It's all because Outlook for Windows is literally Microsoft Edge running Outlook .com in a browser window.
New Outlook runs through WebView2 with around 10 separate processes: GPU process, service worker, utility processes, manager, and more. It uses roughly 490MB to 636MB RAM while idle, compared to Outlook Classic sitting around 117MB to 148MB.
CPU usage is also worse: around 4% idle on new Outlook versus under 1% on Classic in my testing.
Microsoft shut down Mail and Calendar, keeps pushing enterprises toward this web wrapper, and still wants people to believe it is the future of email on Windows.
SHAME!
Windows 11 June 2026 update, which was supposed to make PCs faster, is crashing some PCs with BSODs, breaking OneDrive integration in File Explorer and custom folder icons, and causing other problems.
We're seeing reports that Windows 11 KB5094126 is causing boot failures on some PCs, mostly HP enterprise hardware.
The worst reports involve BitLocker recovery loops, Black Screen of Death/BSOD failures, Secure Boot signature errors, and error 0xc0430001.
Affected models appear to include HP EliteBook 840 G10, HP ProBook 460 G11, HP Engage One Pro G2 AiO POS, HP ZBook, and some Dell Precision systems.
The likely trigger is Secure Boot certificate handling + EFI partition space. On older images with a 100MB EFI partition, Windows may fail to update Boot Manager because there isn’t enough space, especially on HP systems where firmware recovery files can bloat EFI.
There are also File Explorer cloud integration issues. OneDrive, and in some cases Dropbox or iCloud Drive, may stop opening from the sidebar/tray shortcut after KB5094126.
Microsoft also confirms desktop.ini hardening can break custom folder icons or localized folder names from untrusted sources.
KB5094126 is important, as it fixes 200+ security bugs, but be careful, as it could cause havoc on some PCs.
💥Microsoft is updating the #SecureBoot certificates — Check out this #ViaMonstraMiniCourse JUNE 18, 9:00 - 10:30AM CDT 💻 SECURE BOOT 2026 - WHAT BREAKS AND HOW TO FIX IT with @jarwidmark and @AndrewJNet 👨💻 If you manage Windows endpoints, servers, or imaging infrastructure, you need to understand what these changes mean in practice. #ViaMonstraAcademy
Sign up ➡️ https://t.co/qSTTGbGjcU
This LIVE Online Training is for YOU if you want to:
✅Understand what is changing in Secure Boot in 2026
✅Identify what can break in deployments and recovery scenarios
✅Learn how DB and DBX updates impact imaging and boot media
✅Build detection and monitoring strategies for certificate rollout
✅Ask Johan and Andrew questions directly in a live training environment
#Windows updates can fail if firewalls or proxies get in the way. The page walks through how TLS checks work, what common errors mean and how small tweaks in proxy or firewall settings usually fix the update issues.
https://t.co/C6Nl6UxE7q
New Update | Microsoft's KB5089549 update for Windows 11 25H2 & 24H2 brings 40+ enhancements 💻, fixes Bitlocker issues📌, adds Xbox mode, haptic feedback improvements#️⃣, and boosts startup performance🔖. https://t.co/7b44wzzYDE
Explore the latest networking capabilities in Windows Server 2025, including new announcements and enhancements across host management, physical network visibility, and VM network management. https://t.co/kM3rvZzzgv
This is Part 1 of a new series about getting started with GitHub for Intune and Microsoft 365 admins, specifically geared toward non-developers.
🎥 Watch here: https://t.co/06WMv8UirY
#intune#powershell#github
Deep Dive: Troubleshooting Windows Update Scan Source Behavior
Is scan source actually doing anything in your co-managed environment? I share my testing results, how you should test and touch on the scan source dance across #ConfigMgr, #MSIntune & WUA.
https://t.co/Bf6DBXaiXv
🚨Important Update🚨 - The MDT Integration with #ConfigMgr and Standalone is no longer supported 🚫 with Configuration Manager. Customers should remove MDT TS steps, followed by removing MDT integration, to avoid TS corruption and modification failures.
https://t.co/GGKPirAgIp