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
Add your own comment

148 Comments on Windows 11 January 2026 Update Triggers Black Screens, Outlook Failures, and Emergency Patches

#101
trparky
mechtechsmells like AI doing the coding/updates?? ;)
They did say that AI is writing up to a third of their code. Let that sink in...
Posted on Reply
#102
Darmok N Jalad
trparkyThey did say that AI is writing up to a third of their code. Let that sink in...
Which means that many fewer humans in the mix. Can’t wait for the day when it breaks and no one knows how to fix it.
Posted on Reply
#103
trparky
Darmok N JaladWhich means that many fewer humans in the mix. Can’t wait for the day when it breaks and no one knows how to fix it.
Considering how much technical debt is in Windows because of decades of compatibility layers, it may be sooner than anyone may think.

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...
Posted on Reply
#104
Prima.Vera
As I said it many times before, Windows Insider's alfa and beta testing is a complete laughable joke.
By far, the most useless "feature" from MS portfolio.
Posted on Reply
#105
trparky
Prima.VeraAs I said it many times before, Windows Insider's alfa and beta testing is a complete laughable joke.
Yes, because nobody in their right mind would ever run an Insider Build as their main system.

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.
Posted on Reply
#106
Darmok N Jalad
Prima.VeraAs I said it many times before, Windows Insider's alfa and beta testing is a complete laughable joke.
By far, the most useless "feature" from MS portfolio.
At one time, people wrestled for the privilege of being a pre-release Windows tester. Now, I don’t know what the general sentiment is on being part of the “insider” club that MS introduced with 10. I think people got frustrated with the concept and how often the feedback was ignored. I think MS set up something they couldn’t possibly manage. Now, I doubt it actually makes a difference—they just ship their 30% AI code and call it a day.
Posted on Reply
#107
Spacednow1
Just my perception from an old person that's tinkered for many years. Not a pro in coding or anything like that but seems win 98 was an updated and tweaked 95...XP seemed mostly new all around, probably not though. I skipped Vista after it seemed to have to many problem..probably mostly hardware related IMO. THEN you have 7, been told it's just Vista fixed and the hardware has finally getting caught up along with fixes for older hardware. By the end of 7 it sailed along great, and was fairly easy to tweak. Then 10, which I skipped because I was used to 7 and didn't have time to learn tricks to tweak it. I was on 7 until late 2022, workaround's were a pain to get it working on newer hardware, but it wasn't that hard. I finally jumped to 11 (23H2) when it was getting to difficult to keep browsers running. What I've noticed is it seems that everything after 7 is all built on the "bones" of 7. Lines of code added here and there, features added that required more coding or changing good coding just enough to make that feature work. Mostly it's all a bunch of GUI changes and new features added into/onto old code with out ever cleaning out problem coding...just adding more to correct it instead of finding the problem in the code changes to begin with.
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.
Posted on Reply
#108
John Naylor
Dirt ChipDo anyone still update as soon as possible??
It is a self inflicted wound, nothing less, to auto update..

For years now im waiting at a few weeks to month, depends on the update magnitude.
With so many tools that allow people turn it off. I have to wonder why people let it happen. It's like complaining that you get wet when you go outside w/o a raincoat of umbrella. Solution = Don't do that
,
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>
Posted on Reply
#109
Shou Miko
Prime2515102"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."

This has been happening for years (until I recently switched from POP3) on Windows 10.
Outlook in newer times since like 2013 or so have never been working great with POP/IMAP, Mozilla Thunderbird on the other hand just works.

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.
Posted on Reply
#110
FoulOnWhite
EnviousFrogYou know LTSC versions are affected by these bugs as well right?
Just like me i reckon most LTSC users are on 24H2, which i am not sure is affected.
Posted on Reply
#111
Vayra86
razzaQAnd most of ya are raging' to the rest of us win 10 users " OH switch to win11, iz the bezt EVAR!!!" or "keep using a dead obsolete windows"etc.

At this point just give it a break.
Maybe in your head, but I don't see anyone raging about someone else's Windows 10 installation. The only statement being made is that Win 11 is also just fine, IF you get an installation that isn't going to change every odd moment without notice. Win 10 is also just fine, as long as you get security updates, but when you keep reading that security updates bork systems.... honestly, I'd opt out too and just wing it.
AVATARATEach my machine is like that:


I want to receive updates when they are released, is that a problem?
I have no problems with you doing that ;) Some people go bungee jumping, get drunk, go to a movie or just fire up their game ...but hey, you get updates instead. Such fun!

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.
FoulOnWhiteJust like me i reckon most LTSC users are on 24H2, which i am not sure is affected.
You are only affected on LTSC if you manually update your system. Microsoft will not push updates on it.
John NaylorWith so many tools that allow people turn it off. I have to wonder why people let it happen. It's like complaining that you get wet when you go outside w/o a raincoat of umbrella. Solution = Don't do that
,
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>
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.
Posted on Reply
#112
Tek-Check
I downloaded this update on my AM5 system with 24H2 and AMD Adrenaline drivers. No black screens, Outlook works. Have not noticed any major glitches so far.
What is going on? Any definitive diagnosis?
Posted on Reply
#113
AVATARAT
Vayra86I have no problems with you doing that ;) Some people go bungee jumping, get drunk, go to a movie or just fire up their game ...but hey, you get updates instead. Such fun!

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.
If something breaks, I could fix it , or uninstall the update, or I have a backup after all.
So everything is fine ;)
Posted on Reply
#114
Vayra86
AVATARATIf something breaks, I could fix it , or uninstall the update, or I have a backup after all.
So everything is fine ;)
Yeah so while I'm playing games or getting drunk, you're fixing your update woes.

The real question is, was it not fine without the update?
Posted on Reply
#115
AVATARAT
Vayra86Yeah so while I'm playing games or getting drunk, you're fixing your update woes.

The real question is, was it not fine without the update?
I prefer it that way, and yes you are right here :)
Posted on Reply
#116
EsaT
Spacednow1...but seems win 98 was an updated and tweaked 95...XP seemed mostly new all around, probably not though.
Corect. Win 98 was tweaked and updated here and there Win 95 with all of its problems of keeping it stable with application basically bringing also Windows down like house of cards.
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.
Spacednow1How 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....
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.
Posted on Reply
#117
FR3D1
Ninja Cat
@AleksandarK
Apps might become unresponsive when saving files to cloud-backed storage
learn.microsoft.com/en-us/windows/release-health/status-windows-11-25h2#apps-might-become-unresponsive-when-saving-files-to-cloud-backed-storage
Status Originating update History
Confirmed OS Build 26100.7623
KB5074109
2026-01-13 Last updated: 2026-01-20, 22:11 PT
Opened: 2026-01-20, 22:10 PT
After installing Windows updates released on or after January 13, 2026 (KB5074109), some applications might become unresponsive or experience unexpected errors when opening files from or saving files to cloud-backed storage, such as OneDrive or Dropbox.

For example, in some configurations of Outlook that store PST files on OneDrive, Outlook might become unresponsive and fail to reopen unless its process is terminated in Task Manager, or the system is restarted. In addition, sent emails might not appear in the Sent Items folder, and previously downloaded might be downloaded again.

Workaround:

If you are experiencing this issue, please contact the application developer for possible alternative methods of accessing the files.

For Outlook-specific scenarios, moving the PST files out of OneDrive should resolve the issue. For guidance, please see documentation at How to remove an Outlook .pst data file from OneDrive. In addition, email accounts can still be accessed via webmail, if supported by your email provider.

Organizations and IT administrations who need urgent help with a mitigation, should contact Microsoft Support for business.

Next steps:

We are working on releasing a resolution for this issue as soon as possible. We will provide an update when more information is available.

Affected platforms:

Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019
Server: Windows Server 2025; Windows Server, version 23H2; Windows Server 2022; Windows Server 2019
I have now installed “24H2/25H2 (Build 26200.7627) KB5077744 OOB.” So far, everything is running according to plan.

With a friendly smile,
Fred.
Posted on Reply
#118
Wirko
EsaTWas 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
Co-operative multitasking of DOS and Windows 3.1/95/98/ME vs. pre-emptive multitasking of Windows NT. In the former, system is only stable as long as all running processes are willing to co-operate.
EsaTAnd there would be even less reason to trust anything made from scratch, because it would be AI slop from start to finish.
Good point. M$ (as we called them when they were already rich but still capable of making solid products) isn't currently able to design, implement and test a brand new Windows feature, except AI-related ones. New Run dialog box? Yeah but is's so poorly designed. ClearType for OLED, portrait orientation and landscape+portrait monitor setups? Come on.
Posted on Reply
#119
Prima.Vera
A better explanation of what is happening to the Win 11 disaster:

Posted on Reply
#120
trparky
Pretty much what I wrote about a couple of posts back—Microsoft doesn't care about Windows anymore and it's evident in how the quality of the OS has gone into the toilet.
Posted on Reply
#121
AGlezB
trparkyPretty much what I wrote about a couple of posts back—Microsoft doesn't care about Windows anymore and it's evident in how the quality of the OS has gone into the toilet.
Small correction: MS cares about Windows. What they don't care about is users. 😝
Posted on Reply
#122
Apocalypsee
Prima.VeraA better explanation of what is happening to the Win 11 disaster:

Though the video is informative, the editing is horrible. I really hate those movement from left to right, zoom in and out. God just stay still, let the facts tell its tale not by visual.
Posted on Reply
#123
AGlezB
Yesterday I received another little gem:



That's two in a row. Too much vibe coding it seems. :ohwell:
Posted on Reply
#124
Unregistered
AGlezBYesterday I received another little gem:



That's two in a row. Too much vibe coding it seems. :ohwell:
an OOB fix for an OOB fix, cute.
#125
FR3D1
Ninja Cat
FR3D1So far, everything is running according to plan.
After the last update left its mark (no dark mode in the copy & delete dialog, for example!), I briefly reverted to “Build - 19044.1288” and then ended up back on Windows 11 aka “Build - 26100.1742.” The latter only because I subsequently discovered by chance that “Windows Update” can be bypassed via GPO. Why didn't I know that before? All these useless tricks 17, which are sometimes run-of-the-mill. #Specify internal path for Microsoft Update service #127.0.0.1




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.
Posted on Reply
Add your own comment
Nov 21st, 2026 01:31 PST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts