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
Win11=🚽
[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.
When trying to repair (after pressing Error checking) the drive:
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.
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.
Attached (for those interested!); “Optional Update” January 2026;Source
With a friendly smile from Build - 26100.1742,
Fred.
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:
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
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
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.
In my young ages I did that a lot lol
NVIDIA confirms graphics issues related to Windows Update KB5074109
Deskmodder (de)
With a friendly smile,
Fred.