Microsoft
Microsoft Rolls Out Second Emergency Windows 11 Update to Fix Outlook Crashes
Microsoft emergency Windows 11 update has been released once again as the company responds to a critical issue causing Microsoft Outlook to crash on affected systems. The out-of-band patch follows last week’s emergency update and addresses problems linked to cloud-stored files after the January 2026 security update.
Microsoft Emergency Windows 11 Update Fixes Outlook Crashes
Microsoft confirmed that the latest issue was introduced after its January 2026 security update. The bug primarily impacted apps that open or save files in cloud-backed locations. Among the worst affected was Microsoft Outlook, which either crashed unexpectedly or failed to launch altogether when PST files were stored in services such as OneDrive.
Users reported Outlook freezing, displaying error messages, or becoming completely unresponsive while accessing cloud-synced files. Given how critical Outlook is for both personal and enterprise communication, Microsoft classified the issue as severe enough to bypass its regular monthly update schedule.
What the Out-of-Band Update Fixes
Out-of-band updates are rare and are only released when a problem cannot wait for the next Patch Tuesday cycle. According to Microsoft, this emergency Windows 11 update resolves:
- Outlook crashes linked to PST files stored in cloud locations
- App freezes when opening or saving cloud-backed files
- Error messages triggered by OneDrive-integrated storage
Microsoft said the Microsoft emergency Windows 11 update is designed to immediately stabilize Outlook and prevent crashes when working with cloud-backed files.
The company also noted that this update is cumulative, meaning users do not need to install the previous emergency patch separately. Installing the latest update will automatically include all fixes released earlier in January.
A Rocky Start to January Updates
This marks the second major issue tied to Microsoft’s January 2026 security updates. Earlier in the month, users experienced problems where Windows 11 systems failed to shut down or hibernate properly. Additionally, some Windows 10 and Windows 11 devices faced login issues when using remote desktop connections.
Users affected by Outlook crashes should install the Microsoft emergency Windows 11 update as soon as possible to avoid further disruptions.
What Users Should Do Next
Microsoft strongly recommends that affected users install the latest emergency update as soon as possible through Windows Update. Doing so should restore Outlook stability and prevent further disruptions when working with cloud-stored files.
Also Read: iPhone Air Price Slashed Worldwide as Apple’s Slim Phone Fails to Impress Buyers
Windows 11 shutdown bug has pushed Microsoft into rapid damage control after January’s Patch Tuesday update broke one of the most basic system functions—turning a PC off. The company has now released an out-of-band emergency update, KB5077797, to fix the issue affecting systems running Windows 11 version 23H2.
The problem surfaced shortly after January’s cumulative security update was installed. Instead of shutting down, restarting, or entering hibernation as instructed, affected systems either ignored the command or appeared to shut down briefly before powering back on. For users, this meant laptops draining battery overnight and office desktops consuming power long after working hours.
Windows 11 shutdown bug: What went wrong after Patch Tuesday?
Microsoft traced the bug to System Guard Secure Launch, a boot-time security feature designed to protect systems from low-level attacks. In certain configurations—particularly where Secure Launch is enabled by default—the January update conflicted with this feature, causing shutdown and hibernation processes to fail.
The Windows 11 shutdown bug quickly became a serious concern for IT teams, as affected machines ignored shutdown commands despite repeated attempts. In enterprise environments, the Windows 11 shutdown bug increased power usage and raised compliance concerns.
Given the severity and scale of the issue, Microsoft opted not to wait until February’s Patch Tuesday. Instead, the company pushed KB5077797 on January 17 as an unscheduled fix. According to Microsoft, installing this update restores normal shutdown, restart, and hibernation behavior without impacting security protections.
How the Windows 11 shutdown bug impacted users and enterprises
The out-of-band update also addresses another frustrating bug introduced in January’s patches. Some users were unable to sign in via Remote Desktop due to repeated or looping credential prompts. This authentication issue affected both client and server environments, complicating remote work and IT administration.
However, not all Patch Tuesday problems have been resolved yet. Microsoft has also acknowledged an issue where classic Outlook POP account profiles may freeze or hang after the January update. A fix for that particular bug is still pending.
A reminder about Patch Tuesday risks
January’s Patch Tuesday was one of Microsoft’s largest in recent months, delivering over 100 security fixes across Windows and related components. With at least one vulnerability already under active exploitation, delaying the update was not a safe option for most users or organizations.
By releasing KB5077797, Microsoft aims to fully resolve the Windows 11 shutdown bug without waiting for the next Patch Tuesday cycle.
Microsoft is advising anyone experiencing shutdown or Remote Desktop issues to install KB5077797 immediately. The incident serves as another reminder that even critical security updates can introduce unexpected side effects, often only discovered once patches are widely deployed.
Also Read: Google App Voice Search Redesign: 7 Powerful Improvements Coming to Android
Windows 11 NVMe driver tweaks are making the rounds because they can unlock big gains in random SSD speed—especially random writes—by forcing Windows 11 to use a newer, native driver path that Microsoft already ships in Windows Server 2025.
Windows 11 NVMe driver: Why this change can boost speed
Most Windows 11 systems talk to NVMe SSDs through an SCSI translation layer instead of using fully native NVMe instructions end to end. That translation step can add overhead, which often shows up in small, random read/write tasks—the kind that influences boot behavior, app launches, and system “snappiness.”
Microsoft introduced a native NVMe driver in Windows Server 2025, but it isn’t enabled by default on typical consumer Windows 11 installs. Enthusiasts found that specific registry edits can trigger a driver switch (often described as a pseudo driver injection), allowing Windows 11 to load the native NVMe driver.
Benchmark results: Random writes see the biggest jump
Early testing suggests the Windows 11 NVMe driver switch can materially improve random performance, though the size of the gain depends on the SSD model, firmware, and device platform.
- On an SK Hynix Platinum P41 2TB running Windows 11 25H2, benchmark screenshots showed higher random read and notably higher random write results after enabling the driver.
- On a Crucial T705 4TB inside an MSI Claw 8 AI+, one user reported random write performance improving by up to 85%.
These improvements won’t always translate into dramatic real-world changes for every workflow, but they can be meaningful for systems that frequently hit storage with random I/O.
Important warning before you try it
This Windows 11 NVMe driver hack involves editing the registry, which can be risky. Some users reported losing access to a drive’s file system after applying the changes, then recovering access after reverting them. If you experiment, back up important data first and expect possible instability until Microsoft enables the driver officially.
Also Read: Samsung Galaxy Z TriFold Durability Test: YouTube Hinge Stress Run Nears 150,000 Folds