Users of Windows 11 have reported various complications following the installation of update KB5074109, notably a persistent black screen and Outlook malfunctions for those connecting via POP accounts. This update appears to primarily affect systems utilizing Nvidia GPUs, but user experiences vary across both Nvidia and AMD hardware. Additionally, it seems that File Explorer is no longer honoring the settings defined by desktop.ini, especially the property ‘LocalizedResourceName’.
Released on January 13, 2026, during the January Patch Tuesday, Windows 11 KB5074109 is designed for the 25H2 and 24H2 versions, pushing systems to Build 26200.7623 or 26100.7623 respectively. Unfortunately, software updates—including these patches—often introduce a new set of challenges, impacting a limited number of users.
Identifying the Black Screen Problem Post-January 2026 Update
The black screen issue related to Windows 11 KB5074109 may stem from the update itself or compatibility dilemmas with graphics drivers. Confirmation of the issue across a minority of systems featuring both Nvidia and AMD GPUs has been received. After the January 2026 Update, users experience abrupt black screens accompanied by brief freezes of the desktop.
One potential mitigation reported by a user involved switching the monitor’s DisplayPort mode—shifting from 1.4 to 1.2 and vice versa. Typically, this issue is not pervasive, but if it occurs repeatedly, it may be advisable to consider uninstalling KB5074109 or updating your GPU drivers.
Another related phenomenon post-update involves users witnessing a black wallpaper, regardless of the chosen background. Whether utilizing the Spotlight feature or a personal custom design, your settings may revert after the upgrade.
If you experience this reset to a black wallpaper following the update to Windows 11 Build 26200.7623 (25H2) or 26100.7623 (24H2), navigate to Settings > Personalization to select your background anew.
Outlook Issues Following Update KB5074109
Microsoft has acknowledged a significant issue wherein Outlook—which functions using POP accounts—fails to launch or exit properly post-update. Users report that Outlook may appear closed while the outlook.exe process continues running invisibly in the background. This leads to complications when attempting to reopen Outlook, often resulting in error messages indicating that it is still running. Users can only regain access by terminating the process in Task Manager or rebooting their devices.
Users have experienced Outlook freezing shortly after launching, facing a frustrating ‘Not Responding’ status during usage:
This issue appears to affect only Outlook Classic when configured with POP/SMTP settings, while IMAP accounts operate without disruption. One user remarked, “After the Patch Tuesday update, classic Outlook in POP mode becomes unresponsive within 5-10 minutes, repeatedly freezing.”
Microsoft is aware of this dilemma and is investigating potential solutions. Although no immediate workaround is in place, an update addressing the POP account profile issue is anticipated.
Steps to Resolve Outlook Freezing Issues Post-January 2026 Update
In the event that Outlook fails to open or close, the first step is to access Task Manager and end the Outlook.exe process. However, it is advisable to refrain from force-stopping the process except when necessary.
If troubleshooting through Task Manager does not provide relief and Outlook continues to misbehave, uninstalling Windows 11 KB5074109 might be the best path forward until a stable update is released.
Challenges with Azure Virtual Desktop and Remote Desktop Functionality
Additionally, Microsoft has confirmed that the January 2026 Patch Tuesday updates could disrupt Azure Virtual Desktop (AVD) functionality, particularly with remote desktop protocol (RDP) connections. Users may encounter issues such as sign-in failures or persistent prompts for credentials after installing Windows 11 KB5074109.
This problem greatly affects Azure Virtual Desktop and Windows 365, especially during connection attempts, as the authentication process seems compromised in the January update.
An affected user documented encountering “Unable to Authenticate” errors alongside a Remote Desktop dialog displaying “An authentication error has occurred (Code: 0x80080005).” Microsoft has officially recognized these credential prompt failures as an issue stemming from recent security updates.
Microsoft has suggested that users consider alternative access methods, such as utilizing the Windows App web client or the Remote Desktop client temporarily, while they work towards a resolution.
“Our inquiry has concluded that recent changes in Windows security updates have led to these credential prompt issues during Remote Desktop connections, ” remarked a Microsoft spokesperson.
Resolving Azure Virtual Desktop Connectivity Issues Post-Update
Microsoft has released a Known Issue Rollback (KIR) aimed at rectifying AVD-related problems stemming from Windows 11 KB5074109 by disabling the feature causing issues. This rollback can be accessed via the Microsoft admin portal or directly downloaded from the official Microsoft website.
The Known Issue Rollback concerning Windows 11 KB5074109 serves to disable problematic features affecting Remote Desktop functionality:
<policies>
<policy name=”KB5074109\_260114\_0745\_1\_KnownIssueRollback”class=”Machine”displayName=”$(string. KB5074109\_260114\_0745\_1\_KnownIssueRollback)”explainText=”$(string. WUKnownIssue\_Help)”key=”SYSTEM\\CurrentControlSet\\Policies\\Microsoft\\FeatureManagement\\Overrides”>
<parentCategory ref=”KnownIssueRollback\_Win\_11\_24H2\_25H2″/>
<supportedOn ref=”SUPPORTED\_Windows\_11\_0\_24H2\_25H2\_Only”/>
<enabledList defaultKey=”SYSTEM\\CurrentControlSet\\Policies\\Microsoft\\FeatureManagement\\Overrides”><item valueName=”1387134606″><value><decimal value=”1″/></value></item><item key=”SYSTEM\\CurrentControlSet\\Policies\\Microsoft\\FeatureManagement\\Overrides\\Metadata\\1387134606″valueName=”ChangeTime”><value><decimal value=”3″/></value></item></enabledList>
<disabledList defaultKey=”SYSTEM\\CurrentControlSet\\Policies\\Microsoft\\FeatureManagement\\Overrides”><item valueName=”1387134606″><value><decimal value=”0″/></value></item><item key=”SYSTEM\\CurrentControlSet\\Policies\\Microsoft\\FeatureManagement\\Overrides\\Metadata\\1387134606″valueName=”ChangeTime”><value><decimal value=”3″/></value></item></disabledList>
If applying the rollback is not a preferred option, consider removing Windows update KB5074109 completely or awaiting an out-of-band patch, which is expected shortly.
Disruptions in File Explorer Due to KB5074109 Update
Recent investigations have illuminated a bug within Windows 11 KB5074109 affecting File Explorer’s ability to recognize the LocalizedResourceName directive located in desktop.ini. This alteration impacts customizing folder names as this directive is typically employed to assign friendly display names to directories.
Additionally, users have reported that the hidden attribute, previously applicable to certain folders like “Saved Games, ” is being ignored altogether despite being set.
Normally, File Explorer reads [.ShellClassInfo] and uses the LocalizedResourceName to display customized folder names when file attributes are configured correctly. After the implementation of KB5074109, however, while the folder remains visible, the custom names fail to appear.
The underlying cause of the problems concerning LocalizedResourceName remains uncertain, potentially linked to updates made to Windows’ core components. Microsoft may have inadvertently disrupted functions within these key files:
- windows.storage.dll
- shell32.dll
- ExplorerFrame.dll
- Windows. FileExplorer. Common.dll
- explorer.exe
As of now, Microsoft has yet to formally address these feedback reports. However, there is an expectation that a fix will emerge in the upcoming cumulative update.
Related Articles:
Microsoft Recommends 32GB RAM as the Ideal Upgrade for Windows 11 Gaming
19:34
Satya Nadella Confirms 1.6 Billion Monthly Windows Users and Bing Surpasses 1 Billion Users
15:14
Satya Nadella Acknowledges Microsoft’s Need to Regain Windows 11 Users and Enhance Performance for Low RAM Computers
0:54
Leave a Reply