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
And I thought about migrating, better not, 10 ltsc is still strong :D
I did not update on purpose my ryzen 7700x/x670e gaming rig and the radeon driver for the radeon 7800xt killed itself, was malfunctioning in w11 pro. Even with metered connection and 5 weeks pause windows 11 pro screws up from working state to defective since ~november 2025. Reinstalling partly fixed the radeon issue. Sound is also broken in "surving the aftermath" after epic game store forced me to update the free game. That game does not start witout epic and the paralax always on crap launcher. Those offline updater packages are also no good. I did not had time yet to publicly download w11 update packages. The main reason why my box is in the november 2025 state for w11 pro 25h2.
I would appreciate to have an outdated windows 11 pro where the radeon 7800xt works flawless with DP audio and my external audio solution and wlan. I can not remember a single time in 2025 where w11 pro worked as it should. I also got a few hours ago the "hey register your windows with an online account pop up message". The fix was to press once the reset button. Much faster as to start reading the full box and bothering with it. I will not bother anymore checking where microsoft hide the button to remove that annoying banner box. When I learnt one stuff with my refurbished notebook, it takes much longer as expected to get rid of the "register now your windows with a windows log in lock screen - which can not be easily skipped". Worst case it triggers windows recovery which needs 2 clicks to force a reboot and it is solved. Note: not updated w11 pro 25h2 since ~november 2025.
T
S
C
Outlook refused to start. After half an hour work everything is all right. I must say that Gemini advised me on the shortest route to do it.
F**k Microsoft and their useless beta testers..
Killing that will allow you to start outlook again.
Somewhere else says Nvidia GPUs also losing performance with the new patch.
I believe the biggest problem with Windows Updates is EBCAK. Folks running God knows what as background services and helper apps, task bar is half as long as the screen is wide, and questionable hardware purchases to save a buck and then wonder why they shit is broke.
Yes, MS has borked a few updates over the years, but get resolved and we move on.
Maybe you shouldn't post unless you are actually a certified technician who knows what they are doing.
In the business world, patches are tested on machines especially made to test new updates to make sure they work before sending them. Maybe you guys 'n gals need a spare machine to test with so you don't bork your main rig.
<rant off>
probable causality ?
Its amazingly fast, kills every process and gets Windows back in line, no matter how badly it is fucked. Well, a bsod is the one thing it can't fix, or a complete system hang.
And the problem isn't MS breaking a few updates, the problem is MS is sending out broken updates more and more often, probably because a lot of their code is written by AI as already pointed out.
Also the fact that MS got rid of their QA team, testing updates and having technicians who know what they're doing to make sure the software doesn't break the OS should be their job, but of course they would rather make their users the free beta testers.
------
we need a competitor to Active Directory for Linux and a stronger push for distros like ZorinOS and whatnot, I am sick of their bullshit all the god damned time
With a mischievous smile,
Fred.
At this point just give it a break.