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

#51
zenlessyank
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.
I do, but I am a sadomasochist who is a glutton for punishment. I also use myself as a sacrificial lamb so my clients can get a heads up from me if I encounter anything unusual or bad. I mean we are talking about humans here, mostly ;)
Posted on Reply
#52
Dirt Chip
GattI had literally to repair/reinstall the whole Office 365.

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..
It is a known secret that all we are privet users are the beta tester’s for the cooperated secto- those who buy licenses by the thousands.
That’s why we keep getting those winX to winX+1 upgrades for free ;)
Posted on Reply
#53
maxli86
" One of the most noticeable problems is sudden black screen episodes, which freeze the desktop for one or two seconds before returning to normal. "

If Microsoft notice this thread, you almost cause me a set of RAM.
I did notice there was freezing but at that time which was last week the PC did not resume back normally.
I had to force shutdown than the PC work normally.

I assume it was RAM issue but I have run some test and my RAM is fine.
And yes display was glitchy sometimes with flickering.
Guess what I have to do, I did a fresh install of Windows 11 today.

Microsoft updated the Windows installer so there was newer installer being released dated 6 Jan 2026.
I am still monitoring whether does this fix the glitchy and random freezing issue or not.
I have another Windows 11 PC that I will definetely need to reinstall from scratch for sure.

Get your game together Microsoft I feel like dumping Windows 11 for Windows 10.
But on Windows 10 there will always be constant prompt to update to Win 11.
How am I going to revert if I am constantly annoyed by the pop-up?
Posted on Reply
#54
Dirt Chip
zenlessyankI do, but I am a sadomasochist who is a glutton for punishment. I also use myself as a sacrificial lamb so my clients can get a heads up from me if I encounter anything unusual or bad. I mean we are talking about humans here, mostly ;)
More like open heart surgery without general anaesthesia. Life is such a fun :rolleyes:
Posted on Reply
#55
AGlezB
I got this little gem late Saturday:



MS f**ked big this time because OOB updates are very, very rare, to the point where there have been only 4 since 2022. Although there's something interesting if you look at the dates:
  1. June 20, 2022: Out-of-band security update to address an issue with Azure Active Directory services on Arm-based devices.
  2. August 19, 2025: Out-of-band update to address an issue affecting reset and recovery operations.
  3. December 18, 2025: Out-of-band update to address MSMQ service issues leading to queue operations and resource-related errors.
  4. January 17, 2026: Out-of-band update to address issues observed with the January 2025 Windows security update.
3 out of 4 happened in the last 6 months. I'm wondering if MS forgot the first rule of dealers (don't get high on your own product) and are sniffing too much Copilot. :D
Posted on Reply
#57
AGlezB
ShadowizedHate to tell you but you are the beta tester... Microsoft stopped doing QA testing on updates a long time ago probably around the tail end of Win7.
Beta Tester = Home Edition users + anyone who forgot or didn't know how to turn off the "Get the latest updates as soon as they're available" and similar options.
Why pay when you can instead distribute the "preview" update to millions of users and collect analytics on it?
Posted on Reply
#59
katzi
AGlezBI got this little gem late Saturday:



MS f**ked big this time because OOB updates are very, very rare, to the point where there have been only 4 since 2022. Although there's something interesting if you look at the dates:
  1. June 20, 2022: Out-of-band security update to address an issue with Azure Active Directory services on Arm-based devices.
  2. August 19, 2025: Out-of-band update to address an issue affecting reset and recovery operations.
  3. December 18, 2025: Out-of-band update to address MSMQ service issues leading to queue operations and resource-related errors.
  4. January 17, 2026: Out-of-band update to address issues observed with the January 2025 Windows security update.
3 out of 4 happened in the last 6 months. I'm wondering if MS forgot the first rule of dealers (don't get high on your own product) and are sniffing too much Copilot. :D
Oh yea this most Certainly the fault of them huffing their own AI bullshit.
Posted on Reply
#60
phanbuey
Let me guess - it was written and tested by copilot...

Microslop patches are here guys, prepare yourselves.
Posted on Reply
#61
AVATARAT
AGlezBBeta Tester = Home Edition users + anyone who forgot or didn't know how to turn off the "Get the latest updates as soon as they're available" and similar options.
Why pay when you can instead distribute the "preview" update to millions of users and collect analytics on it?
Each my machine is like that:


I want to receive updates when they are released, is that a problem?
Posted on Reply
#63
melkor_unlimited
john_Windows 11 Beta.
As one wise man said: "Windows is usable after 3rd service pack."
May be I could give it chance with 26H2.
Posted on Reply
#65
AGlezB
AVATARATEach my machine is like that:


I want to receive updates when they are released, is that a problem?
You do you.
Me? I want to receive security updates ASAP. The rest I want after they were verified not to cause issues. And some I don't want at all.
For instance: feature updates I only want for compatibility reasons, preferably a year after everyone else got it, which is why I'm still using 24H2 instead of the shinier 25H2.
The result is I read about people having issues with Windows while I keep my installs clean for years without having to repair or refresh.
Posted on Reply
#66
micropage7
the latest version make my wifi unusable
Posted on Reply
#68
TheinsanegamerN
Windows 11 is great for keeping me employed and I thank my lucky stars I dont have to deal with it in my personal life.
TheGeekn°72we 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
You may get your wish sooner then later, because Microsoft is pushing intune cloud HARD and has put AD on maintenance support. They dont want you running local logon management, like they REALLY dont want you to. And if they get their wish.....well there goes a huge reason to keep windows.
Posted on Reply
#69
Gatt
AGlezBBeta Tester = Home Edition users + anyone who forgot or didn't know how to turn off the "Get the latest updates as soon as they're available" and similar options.
Why pay when you can instead distribute the "preview" update to millions of users and collect analytics on it?
I hear you. But when you've been stupid enough to update immediately (like me), what do you do?

Do you risk another mess or do you wait months for the patch that fixes those problems and risk all the other bugs appearing?
Posted on Reply
#70
Grimling
Nothing that an AI-Generated "FIX" could not fix!
Posted on Reply
#71
AVATARAT
AGlezBYou do you.
Me? I want to receive security updates ASAP. The rest I want after they were verified not to cause issues. And some I don't want at all.
For instance: feature updates I only want for compatibility reasons, preferably a year after everyone else got it, which is why I'm still using 24H2 instead of the shinier 25H2.
The result is I read about people having issues with Windows while I keep my installs clean for years without having to repair or refresh.
25H2 here.
Just manage your OS.
Posted on Reply
#72
theouto
Surely they are just pushing boundaries to see what people will put up with right? This has to be intentional, I do not believe that anyone with any level of self-respect would push out such a broken update. I also refuse to believe that proper QA (hell, even minimal QA) would not have seen any of these issues coming.

Microsoft, what are you doing? You want people to call you Microslop, right? How is it that Win11 has only gotten worse, that's now how updates are supposed to work.
Posted on Reply
#73
AGlezB
AVATARAT25H2 here.
Just manage your OS.
That was the whole point. Most users don't know or care about what updates they're getting and that's how MS betatest updates.
Posted on Reply
#74
TheinsanegamerN
GattI hear you. But when you've been stupid enough to update immediately (like me), what do you do?

Do you risk another mess or do you wait months for the patch that fixes those problems and risk all the other bugs appearing?
System restore to pre update and wait for the fixes, or blow it away and reinstall a stable OS version.

All my stuff is on separate drives for this reason. Half an hour and everything is reinstalled and restored.
Posted on Reply
#75
EsaT
zenlessyankGo to work at Microsoft and help them out. I was told long ago that if I wasn't part of the solution, then I was part of the problem.
Shouldn't problem be addressed at its root?
Meaning need to fire Satya using 16" naval rifle.
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