Monday, January 19th 2026
Windows 11 January 2026 Update Triggers Black Screens, Outlook Failures, and Emergency Patches
Microsoft's first Patch Tuesday of 2026 has become a troubleshooting nightmare for Windows 11 users. The KB5074109 update is causing widespread issues, affecting everything from home PCs to enterprise servers. Released on January 13 for versions 24H2 and 25H2, this cumulative patch was intended to deliver about 100 security fixes, including three critical zero-day protections and an NPU fix. Instead, it has left many systems struggling with black screens, locked Outlook installations, and broken connections to Azure Virtual Desktop. One of the most noticeable problems is sudden black screen episodes, which freeze the desktop for one or two seconds before returning to normal. This glitch affects machines with both NVIDIA and AMD graphics cards, though the exact cause remains unclear.
Some users found relief by adjusting their monitor's DisplayPort settings, temporarily switching from version 1.4 to 1.2 and back. Others discovered their desktop backgrounds had reset to solid black after the update, requiring them to manually reapply their wallpaper or Spotlight settings through the personalization menu. On the productivity front, Outlook Classic users with POP email accounts face a weird and frustrating bug. The update causes Outlook to appear closed while the outlook.exe process continues running in the background, preventing any attempts to restart the application. Users either see nothing happen when they click the Outlook icon or receive an error stating the program is already open. The only temporary solution is to open Task Manager and forcibly end the process, though this must be repeated each time Outlook is closed. Microsoft has confirmed the issue but has not yet released a fix.Enterprise environments have been hit even harder. Azure Virtual Desktop and Windows 365 customers experienced complete authentication failures when trying to establish remote connections. The January 2026 update disrupted the credential prompt flow, causing immediate sign-in failures with error code 0x80080005. Microsoft responded quickly to this crisis by issuing a Known Issue Rollback (KIR) that disables the problematic feature and releasing emergency out-of-band (OOB) updates on January 17. These patches, designated KB5077744 for 24H2 and 25H2 and KB5077797 for the older 23H2 version, require manual installation from the Microsoft Update Catalog. For organizations unable to apply these fixes immediately, Microsoft suggests using the web client at windows.cloud.microsoft as a temporary workaround.
Sources:
Windows Latest #1, #2
Some users found relief by adjusting their monitor's DisplayPort settings, temporarily switching from version 1.4 to 1.2 and back. Others discovered their desktop backgrounds had reset to solid black after the update, requiring them to manually reapply their wallpaper or Spotlight settings through the personalization menu. On the productivity front, Outlook Classic users with POP email accounts face a weird and frustrating bug. The update causes Outlook to appear closed while the outlook.exe process continues running in the background, preventing any attempts to restart the application. Users either see nothing happen when they click the Outlook icon or receive an error stating the program is already open. The only temporary solution is to open Task Manager and forcibly end the process, though this must be repeated each time Outlook is closed. Microsoft has confirmed the issue but has not yet released a fix.Enterprise environments have been hit even harder. Azure Virtual Desktop and Windows 365 customers experienced complete authentication failures when trying to establish remote connections. The January 2026 update disrupted the credential prompt flow, causing immediate sign-in failures with error code 0x80080005. Microsoft responded quickly to this crisis by issuing a Known Issue Rollback (KIR) that disables the problematic feature and releasing emergency out-of-band (OOB) updates on January 17. These patches, designated KB5077744 for 24H2 and 25H2 and KB5077797 for the older 23H2 version, require manual installation from the Microsoft Update Catalog. For organizations unable to apply these fixes immediately, Microsoft suggests using the web client at windows.cloud.microsoft as a temporary workaround.

148 Comments on Windows 11 January 2026 Update Triggers Black Screens, Outlook Failures, and Emergency Patches
Just download the corresponding KB from
[ICODE]https://www.catalog.update.microsoft.com/Search.aspx?q=KB5077744[/ICODE]
and install it manually or by running
[ICODE]DISM /Online /Add-Package /PackagePath:C:\Users\YourUser\Downloads\Windows11.0-KB5077744-x64.msu[/ICODE]
NOTE: Those instructions assume you're on Win 11 24H2 or 25H2, if youre on and older version or on Win 10 replace the KB with the correct one.
Don't forget to use the correct path to the update if you're using DISM.
now I'm wondering, is there even anyone at all working on an AD linux competitor? I can't imagine that the huge distro availability makes things easy to build that up for but I also imagine that someone who would undertake such a project would just pick a few "business oriented" distros to support with?I don't get it, I have the anomalous update installed, why do I have to look up myself the KB with the fixes instead of getting it directly by running the auto updater, it's like they enjoy having pissed off users
They are down the drain , the sink is empty.
I wish Linux ran as good on Intel and NVIDIA as it does with AMD.
The uncomfortable truth is that Windows is no longer Microsoft’s business—it’s just the bait.
Azure, Microsoft 365, OneDrive, and the rest of the cloud empire are the real profit engines now. Windows is just the storefront, the funnel they use to herd people into subscriptions and services. That’s why Microsoft is perfectly happy letting Office live on the web, OneDrive live on MacOS, and Teams run on anything with a screen. They don’t need Windows to win anymore—they just need you paying rent inside their ecosystem.
And I think Microsoft knows something a lot of Windows diehards don’t want to admit: Windows is dying. Not overnight, not dramatically—but death by a thousand cuts. Decades of legacy baggage, technical debt stacked on technical debt, and an architecture that was never designed for a modern threat landscape are finally catching up.
What we’re seeing now isn’t evolution—it’s maintenance mode. Microsoft will keep Windows breathing, sure. They’ll patch it, wrap it in virtualization, slap more “AI features” on top, and call it innovation. But they’re not rebuilding the foundation because the foundation doesn’t matter to them anymore.
Windows isn’t the product — you are. And Windows is just the delivery vehicle.
Brother's laptop is AMD CPU and GeForce RTX 2060 GPU, black screens.
Mom's laptop is Intel 10th gen i3-1005G1 int. graphics
Both rolled back via safe mode.
Edited: wording.
no bugs ;)
Yes, Windows is still a massive product. But it’s no longer the center of the Microsoft universe the way it was in the 90s and 2000s. Back then, everything existed to make Windows stronger. Today, Windows exists to make Azure, Microsoft 365, and OneDrive stronger.
And the idea that “the ecosystem fails without Windows” just isn’t true anymore. Microsoft has spent the last decade proving the exact opposite. For instance...
- Office works perfectly on MacOS, iOS, Android, and the web.
- OneDrive is a first-class citizen on MacOS. It even has On-Demand files much like OneDrive has on Windows.
- Teams runs better in a browser than on Windows.
- Azure doesn’t even run on Windows internally... It runs on Linux!
If Windows were truly indispensable, Microsoft wouldn’t be working so hard to make sure people can live entirely inside their services without it.As for “there’s no drive to use Office 365 over Google Docs on another OS”, millions of Mac and iPad users already do exactly that. Enterprises choose Microsoft 365 because of Exchange, SharePoint, compliance tools, and integration with Azure AD... not because they love Windows.
Windows used to be the product, now it’s the on-ramp for their cloud services.
That doesn’t mean Microsoft wants Windows to die, it just means they no longer need Windows to dominate in order for Microsoft to dominate. And that shift in incentives explains a lot about the direction Windows has taken in the last few years.
Is it powershell.exe or ps.exe or cmd.exe?wget, curl or something else is not yet invented on windows?
with wget or curl you can directly download files from the internet in a terminal, e.g. bash in the gnu userspace with the linux kernel without using a www-client
package manager does not exists on windows?
emerge KB502342134
-- My windows 11 pro gaming rig "windows update" graphical user interface security updates from 06/30/2025 and windows updates (multiple sections) from 11/14/2025. Staying longer away from windows update is also not a solution. It screws itself with the same not touched amd gpu driver.
edit2:Nothing wrong with using the ignore button. Sometimes it was wrong, 80% it was correct. Endless discussions will lead to warning, e.g. pcgh.de a few days ago with my user there // one comment is quite often a reason for warning on several german tech forums // ignore is the better option for all participants. Even using a wrong smiley below a hard fact statement or serious statement justifies an ignore in my point of view. The freedom to not read the posts. Too bad, smileys are still shown even when the user is no the ignore list.
Those ignored will be read a bit on my android tablet where I am not logged in.
-- Guys focus on windows - else we get the whatabout something else stuff.
Right below is the date!
edit:U contradict yourself with "Never have a problem. - I had to hunt down a bitlocker key."
I think you want to say, you could not use windows and had the urge to look up the bitlocker key to unlock your bitlocker locked windows. I would call that a problem, an issue with not being able to instantly use windows after an update. Maybe my language comprehension is flawed.
No ads.
No feature-of-the-month experiments.
No Copilot shoved into every corner.
Just an OS that does its job and stays out of the way.
And the crazy part is: I would happily pay real money for that. Not $10 gray-market keys — I mean an honest, consumer-available license that says:But Microsoft won’t sell that to normal users because it conflicts with their actual goal: keeping Windows as a living funnel for subscriptions, telemetry, and cloud services.
So instead, the version of Windows that respects the user is locked behind enterprise contracts, while the consumer editions become ad platforms with an OS attached.
If Microsoft offered LTSC to regular people at a fair price, I’d buy it tomorrow. A lot of us would. That alone should tell them something.
I’m not judging anyone for using them — Microsoft created this situation by refusing to sell normal users a clean LTSC option. But legally speaking, those grey-market keys live in a very murky zone, and Microsoft can revoke them at any time.
If they offered a real consumer LTSC license, most of us wouldn’t even be having this conversation.
It should not matter if you use PowerShell.exe (v5) or ps.exe (v7+)We know. Now try it on the MUC and see what happens. Good luck finding the specific update you need without using the web search because every version of windows and hardware architecture combination uses the same KB number. You'll have less trouble using WSUS.It's called Windows Update and you don't need a command line to use it. Also: DISM, winget, PowerShell and whatever else you think is a Linux-exclusive you'll probably find out it isn't.
:ohwell:
At least those from the EU/EEA can legally acquire/use certain “licenses.”
With a friendly smile,
Fred.
UPDATE: Well, look at that. My work PC just did the monthly patch updates (the timing of which are not under my control), and now Excel has turned into a mess. Once I try to open more than 2 spreadsheets, Excel just becomes unresponsive. This, of course, was not a problem pre-update last Friday, nor had it been a problem before today. Maybe it's not even an Excel issue. Maybe it will work tomorrow. One thing is for certain, I never look forward to the monthly "quality" and security updates.