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

#127
Prima.Vera
You cannot make this $hit up 😂😂😂
Win11=🚽
Posted on Reply
#128
Darmok N Jalad
Prima.VeraYou cannot make this $hit up 😂😂😂
Win11=🚽
Making stuff up is the job of Copilot.
Posted on Reply
#129
tpa-pr
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.
Late to reply to this, but I honestly think that day is already here.

[tinfoil hat on]

I suspect the majority of the senior Windows team, the ones who actually know the plumbing, have all moved on or (more likely) retired. And because the Windows codebase is quite frankly, a mess, the new crop of engineers are battling to maintain it without breaking things.

It's part of the reason why Windows 11 keeps getting more "new" features over fixes to existing ones. The new team can't repair what's already there so they're trying to replace it (see for example, the new taskbar) and praying the underlying plumbing continues to hold up.

Then there's the AI code. You could train a model to be an expert on a codebase, but if said codebase is a mess and full of hacks and workarounds, it's going to make code that is hacky and workaround-y.

[tinfoil hat off]

Note that I have no insider information to prove my theory, so take it with many grains of salt! This is based on stuff like reading about the development history of Windows, the leaked codebases of some Windows versions ("We are morons" :) ), listening to Paul Thurrott talk to Microsofties like Panos Panay etc.
Posted on Reply
#130
Prima.Vera
This is my friends Windows 11:

When trying to repair (after pressing Error checking) the drive:

Posted on Reply
#131
AVATARAT
Prima.VeraThis is my friends Windows 11:

When trying to repair (after pressing Error checking) the drive:

Reboot to Advance Startup, Command prompt, chkdsk C: /F
Posted on Reply
#132
Prima.Vera
AVATARATReboot to Advance Startup, Command prompt, chkdsk C: /F
Actually I had to open as command prompt, issue the chkdsk C: /f /r and then restart the PC.
Funny how this previously was done in Win 10 from the same Check drive without me going to a separate command prompt window. Also the Cleanup Disk was removed too, so now I have to search for it manually to remove the garbage files.
This Win 11 is x10 times more garbage than Vista or Windows ME. Pure junk.
Posted on Reply
#133
AVATARAT
Prima.VeraActually I had to open as command prompt, issue the chkdsk C: /f /r and then restart the PC.
Funny how this previously was done in Win 10 from the same Check drive without me going to a separate command prompt window. Also the Cleanup Disk was removed too, so now I have to search for it manually to remove the garbage files.
This Win 11 is x10 times more garbage than Vista or Windows ME. Pure junk.
If it works, fine 👍
But some errors cannot be fixed on C when working with Windows, and a few times I've had to use a flash drive because the fix "couldn't" be applied.
Posted on Reply
#134
wNotyarD
AVATARATIf it works, fine 👍
But some errors cannot be fixed on C when working with Windows, and a few times I've had to use a flash drive because the fix "couldn't" be applied.
Didn't the GUI tool had a "Reboot and repair" button before, though?
Posted on Reply
#135
FR3D1
Ninja Cat
Prima.VeraWhen trying to repair
Please correct me if I'm wrong, but the “chkdsk” command was originally created for platters, not flash memory. Of course, that doesn't make the nonsensical double dialog any better. Even if an “experienced” user would certainly have gone via the command line.😶‍🌫️

Attached (for those interested!); “Optional Update” January 2026;
[Secure Boot] This release for Windows 11, version 24H2 will execute updates in the Boot Manager on devices that already have the Windows UEFI CA 2023 certificate in their Secure Boot Signature Database (DB). It replaces the 2011 signed bootmgfw.efi with the 2023 signed bootmgfw.efi. Be advised of the consequences of resetting the DB or turning on Secure Boot, as this can cause a “Secure Boot violation” issue. In those rare cases, the solution is to create the Secure Boot recovery media.
Source

With a friendly smile from Build - 26100.1742,
Fred.
Posted on Reply
#136
Wirko
Prima.VeraActually I had to open as command prompt, issue the chkdsk C: /f /r and then restart the PC.
Many users want to switch to Linux, at least that's what Mico the spy heard and understood. So MS now offers you some more command prompt, hoping you'd stay here.
FR3D1Please correct me if I'm wrong, but the “chkdsk” command was originally created for platters, not flash memory.
But it can correct filesystem errors on anything it recognises as a volume. It can't do anything about bad sectors on flash storage because they are not visible to the OS, but isn't that the case with modern HDDs as well?
Posted on Reply
#137
AGlezB
FR3D1Please correct me if I'm wrong, but the “chkdsk” command was originally created for platters, not flash memory.
Only the part relating to bad sectors ( /R command line option). :D

BTW I've never used chkdsk to check for bad sectors. ScanDisk, on the other hand, I did use a lot along Norton Disk Doctor because HDDs back then were very unreliable and would both die on you without notice or develop bad sectors out of freaking air from one moment to the next so I had to scan them for bad sectors at least once a week. That was a time were you had to have backups of everything and then backups of your backups if you didn't want your data to end up looking down at you from computer heaven. :laugh:
Posted on Reply
#138
AVATARAT
wNotyarDDidn't the GUI tool had a "Reboot and repair" button before, though?
Yes, but this option sometimes gets stuck, simply restarts, scans, and does nothing, so in this case, it is necessary to use the pre-boot option or a flash drive.
Posted on Reply
#139
John Naylor
Vayra86So 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.
How do you figure ? What effort ? That's the exact purpose of WAU. It"postpones shit" until **you** decide to install it. And it keeps them there easily accessible and categorized until you are ready

Wait a few months ... now that would be problematic as not all issues are resolved in "a few months". MS says that it won't install updates if these issues will affect programs or hardware present on the system. But I have experienced otherwise.

1. WAU searches for updates and hardware drivers if you ask it to. I won't install the drivers from WAU, but knowing they exist prompts me to get them at manufacturer's web sites.
2. I wait a bit to see what hits the fan
3. I search the sites (as noted) that track the status of these issues, review each, one at a time. I Install security related updates ****as I see fit**** based upon whether or not the issues are "resolved" . Windows Defender Definition updates go in 1st. OS updates sit.
  • Officially resolved, gets installed
  • Not Resolved, sits until it is
5. I let 24H2 sit a year before installing ... I let 25H2 sit until all issues were "officially" resolved.

So no, I did exactly as I said and I wasn't screwed in any way.

I'd suggest read and comprehend
Posted on Reply
#140
micropage7
sometimes i feel lucky i set the update run on 1AM where i turn off the laptop and sleep
Posted on Reply
#141
AleXXX666
_roman_I'm waiting for those who will write, I do not have an issue with windows 11. Or those who will say I am still on w11 23h2, 24h2 which is basically the same as 25h2, or w10.

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.
22h2 shares with 23h2. 24h2 shares with 25h2. so 23h2 is NOT the same lmfao.
but "general recommendation" from me remains the same: downgrade to some unsupported Win 10/11 whichever you like and is great with your hw. These "security risks" are on your own ANYWAY lol
Posted on Reply
#142
avidgamer121
how low will ms stoop with w11? i have already abandoned it
Posted on Reply
#143
AVATARAT
I've been using dual booting with CachyOS for 3 days now because I'm curious about the compatibility and performance of games. And because I want first-hand information.
Posted on Reply
#144
AGlezB
AVATARATAnd because I want first-hand information.
I wish everyone thought like that at least some times. :toast:
Posted on Reply
#145
trparky
Remember how Microsoft said that they were going to appoint a "quality czar"? Yeah well, that was bullshit because according to this article, the person that they appointed has no direct reports or even a budget. Rumors, according to the same article, indicate that Charlie Bell (the person that Microsoft appointed) is getting ready to retire so really, this so-called "quality czar" position is nothing more than a way to placate the masses into thinking that Microsoft actually cares about how Windows is seen on the world stage.

However, in reality, as long as Windows continues to barely limp on to keep money being funneled into their cloud services, they really couldn't give a rat's ass about Windows.
Posted on Reply
#146
AleXXX666
AGlezBI wish everyone thought like that at least some times. :toast:
I don't have TIME for that Linux "games" (system install-reinstall), lol
In my young ages I did that a lot lol
Posted on Reply
#147
AGlezB
AleXXX666I don't have TIME for that Linux "games" (system install-reinstall), lol
In my young ages I did that a lot lol
What I mean is people tend to swallow whatever pill is first offered to them, no matter the color, so I applaud anyone willing to take the time to look behind the obvious answer.
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