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
Compared to that of MacOS and Linux, Windows is a house of cards. Both Linux and MacOS have never been afraid of saying "Nope, we're not going to do it this way from now on. Either you fall in line or your stuff breaks." Windows, however, bent over backwards for just about anyone laying compatibility layer upon compatibility layer. Well, the bill's due...
By far, the most useless "feature" from MS portfolio.
Unless, of course, you're a straight-up masochist and you hate yourself and you love pain. Or you just love looking at BSODs and your data being corrupted.
That's just my opinion and I'll stick with it. How can anybody not expect just about any update not to break something at this point after so many people having their hands in it. Someone adds bad code in an update, and they can't figure it out so they have a slightly better coder write more code that fixes the problem caused by the previous code because it's easier than finding the problem in the previous code. They need to go back to the drawing board and start from scratch, but with so many companies relying on the current windows evolution they would never go along with writing new software and/or firmware to make products that would work with a windows version from scratch. Many wont write drivers even to work with older windows versions, or they've been forced to install blocks to keep it from installing. Crap, wasted all this time when it would be put to better use learning my way around Linux.
,
Step 1 - Install WAU Manager and turn WAU to "Normal - Search for Updates but do not install them"
Step 2 - When the search finds updates, read the list. Install security related updates as toy see fit and ....
Step 3 -Use any of the various sites that track problems, Ask VG / Ask Woody, elevenforums, etc and check status once and a while.
Step 4 - Chill, think about how much long you'll be able to see the characters on your keyboard from not complaining. Might even consider taking the same approach with hardware and weigh the advantages of being the "1st person on your block" as opposed to waiting till the early adopters on the "bleeding edge" have rooted out the problems.
<== <taking tongue out of cheek now>
I changed to Outlook like 2 years or so ago at work because in my position I need to be aware of things that changes in Outlook and if I am not using the program it's hard to see and notices changes when you don't use the program.
Would I do it myself? Not a million years, never have and never will. Every update pushed is really a token of incompetence on the part of the company releasing it, because you know what? They could have made a better version from the get go, or they need to update something that's broken.
There is no rhyme or reason to updating your system when you experience no issues in its usage. You're really only moving towards a worse situation. Every change on a system you perceive as stable, hurts that stability after all, because something changed.
This perspective is very healthy. Keeps ya sane, and out of an update hell. I think I've earned about 4 years of my life now not updating all kinds of random bullshit I never asked for.You are only affected on LTSC if you manually update your system. Microsoft will not push updates on it.So much effort lol
Just postpone shit for a few months at least and you're golden. Last time I waited a full year before revising security definitions and getting those updates. Its whateverland really, choose your poisonous risk to mitigate: Microsoft fucking up your system, or a virus.
If you had indeed installed security updates shortly after this KB was out, you'd be fucked by the moment you executed step 2.
What is going on? Any definitive diagnosis?
So everything is fine ;)
The real question is, was it not fine without the update?
Was just best to Ctrl+Alt+Del from the first illegal operation error because Windows was going to crash anyway soon requiring reaching for the reset button of case...
Windows ME was continuation of that line.
XP again was in a sense truly new Windows on consumer space being based on Windows NT previously used only by corporations and organizations.
(which used to show in version numbering just continuing from that of NT)
It pretty much removed all the OS crashing issues.Problem is MBA scammer Satya, or Satiainen (crab louse in Finnish) like I call him, firing all the testers and in general basically making all the experienced coders leave over time, if not straight away firing them.
(basically same disaster recipe as how Boeing's quality was driven into smoking impact crater)
www.theregister.com/2018/10/23/microsoft_windows_10_crisis
arstechnica.com/information-technology/2014/08/how-microsoft-dragged-its-development-practices-into-the-21st-century/
arstechnica.com/gadgets/2018/10/microsofts-problem-isnt-shipping-windows-updates-its-developing-them/
And there would be even less reason to trust anything made from scratch, because it would be AI slop from start to finish.
Also if compatibility chain breaks, might as well switch to Linux whose developers aren't actively aiming to screw users into every orifice.
With a friendly smile,
Fred.
That's two in a row. Too much vibe coding it seems. :ohwell:
Build - 26100.1742; I love it!😍
Enclosed;
Next bug in Windows 11: January update prevents some computers from starting up
ComputerBase (de)
With a friendly smile,
Fred.