Neon cyberpunk hallway with a lone figure in front of glowing screens and a blue digital swirl.
Microsoft’s first major Windows 11 update of the year has introduced a string of stability and compatibility problems that went from annoying to blocking for many users — and Microsoft has already been forced into emergency out-of-band patches while some serious issues remain under investigation.

Background​

Microsoft released the January 13, 2026 security update for Windows (first shipped as KB5074109) as part of Patch Tuesday, addressing more than a hundred vulnerabilities and a high-profile, actively exploited desktop window manager flaw. Within days, enterprise and managed environments began reporting hard failures: systems that would not shut down or hibernate, Remote Desktop credential and sign-in failures, and other regression behavior. Microsoft published out‑of‑band (OOB) fixes on January 17, 2026 (notably KB5077797 and KB5077744) to address several of these critical regressions but acknowledged multiple ongoing issues and pushed guidance and rollbacks for affected customers. This article examines the five major categories of bugs tied to the January updates, explains what Microsoft has done, evaluates real-world risk, and provides step‑by‑step mitigation and recovery guidance for end users and IT administrators.

What changed in the January updates​

The January security release (KB5074109) was intended to close many security holes and harden components (including AI-related components), but the rapid rollout produced collateral damage that impacted both user‑mode and kernel behavior on multiple builds of Windows 11. Microsoft’s own support notes and the immediate OOB releases make clear this was not a narrow bugfix: it affected a broad set of scenarios across 23H2, 24H2 and 25H2 tracks and, in some cases, Windows Server editions. At a high level:

  • The initial update fixed 100+ vulnerabilities and component issues (a security-first release).
  • Customer reports flagged power state regressions (shutdown/hibernate), Remote Desktop authentication failures, Outlook hangs for classic profiles using PSTs stored on cloud‑backed storage, sleep/S3 breakage on older systems, and application compatibility regressions impacting clipboard, fingerprint sensors, and anti‑cheat modules.
  • Microsoft issued urgent OOB patches on January 17 to correct several of the most damaging regressions, but not all symptoms were immediately resolved and several remain categorized as “investigating”.

Five major bugs to understand now​

1. Shutdown, hibernation and Remote Desktop sign‑in failures (enterprise impact)​

Microsoft confirmed a class of devices with Secure Launch enabled were restarting instead of performing a clean shutdown or entering hibernation after installing the January 13 updates. This behavior was severe enough for some IT environments to see managed devices remain powered or fail to fully shut down. Microsoft addressed this in OOB update KB5077797 for Windows 11 version 23H2 and related OOB updates for 24H2/25H2. Closely related were credential prompt failures and authentication errors affecting Remote Desktop connections, particularly for Azure Virtual Desktop and Windows 365 scenarios. Microsoft confirmed those failures and pushed targeted fixes in KB5077744. The company recommended Known Issue Rollback (KIR) and, for enterprise-managed devices, applying special Group Policy downloads while the root causes are worked. Why this matters: servers and managed endpoints that cannot shut down cleanly or accept RDP connections can break business continuity and remote administration workflows. Microsoft’s OOB response reduced the blast radius, but IT teams should verify that affected systems actually received and applied the OOB packages and KIR settings.

2. Outlook Classic (POP/PST) hangs and lost Sent Items when PSTs live on OneDrive​

After the January 13 update, users with classic Outlook profiles (POP accounts or PSTs) who store PST files on OneDrive reported Outlook freezing, processes remaining alive after the UI closed, sent messages not being recorded in Sent Items, and message redownload loops. Microsoft published an advisory stating the issue and suggested workarounds: use webmail, move PSTs out of OneDrive, or uninstall the problematic update until a fix is released. The problem has real business impact for users and small organizations that rely on PST workflows and OneDrive synchronization. Microsoft’s current status for that bug is “investigating,” and there is no universal in-place fix available at the time of writing. Users relying on PSTs in OneDrive should assume risk until Microsoft ships a specific remediation.

3. Sleep, S3 power state failures and 'screen goes blank but system stays on'​

Those with older hardware that use the traditional S3 sleep state — reported that the display would go dark when entering sleep but the machine would not fully enter the low power state, leaving the device drawing power and often requiring a hard reboot to recover. Early reporting ties this to the January 13 update (KB5074109) and Microsoft indicated a fix was forthcoming; in the meantime, unplugging certain USB peripherals (for example, webcams) was reported by some users as a temporary partial workaround. Why this matters: Modern Standby (S0) devices are less impacted, but the S3 sleep st older laptops and desktop systems; failing to achieve the expected sleep/low‑power sy drain, lost unsaved work, and user frustration.

4. Gaming and driver compatibility — Easy Anti‑Cheat conflicts and blue screens​

User reports aggregated aunity threads describe conflicts between the update and anti-cheat modules such as Easy ducing Blue Screen of Death (BSOD) events on affected systems — with multiple reports specifically naming Intel Alder Lake+ platforms as experiencing a higher incidence of crashes. Microsoft and game anti‑cheat veng, and users are seeing workarounds only when temporarily uninstalling updates or rolling back drivers.

This class of regressions also intersects with other hardware/driver incompatibilities — users have reported BSODs tied to Intel Smart Sound Technology drivers and certain Western Digital SSDs in the same update window. Those are actively being triaged by hardware vendors and Microsoft.

5. Fragmented compatibility regressions: cache reporting, cursor disappearance, network issues and fingerprint sensor failures​

Beyond the headline bugs, a wide range of smaller but disruptive regressions were reported in community threads and aggregate reporting:

  • A persistent delta of ~8.63 GB of “unremovable” cache appearing in storage reports that in practice can be cleared by Windows Update Cleanup but remains confusing to users.
  • Mouse pointer vanishing in Chromium‑based browsers while typing in text fields.
  • Intermittent inability to obtain a valid IP address after the update on some systems, breaking both Ethernet and Wi‑Fi connectivity for users until driver or firmware fixes are applied.
  • Fingerprint sensor authentication becoming unreliable for some machines, forcing users back to PINs or passwords.
  • Clipboard history reporting as empty despite populated items for certain profiles.

These are largely community‑reported symptoms aggregated from multiple threads; some have been acknowledged as known issues, while others remain user‑reported anomalies pending vendor or Microsoft confirmation.

What Microsoft has done (and how they word it)​

Microsoft reacted quickly to several of the most consequential problems. Significant actions include:

  • Publishing KB5074109 as the January security update (released January 13, 2026).
  • Issuing out‑of‑band cumulative updates (KB5077797, KB5077744) on January 17 to address shutdown/hibernate and Remote Desktop authentication failures, respectively. Those OOB updates are cumulative and include previous security fixes plus targeted fixes for the most immediate regressions.
  • Advising Known Issue Rollback (KIR) and providing Group Policy packages for enterprise admins to temporarily disable the problematic change while waiting for permanent fixes.
  • Posting explicit guidance for the Outlook hang issue and workarounds (move PSTs out of OneDrive, use webmail, or uninstall the update). Microsoft listed that Outlook problem as "investigating" and provided stepwise workarounds.
    Microsoft’s public statements repeatedly emphasize that Home and Pro users on personal devices are very unlikely to experience some of these enterprise‑class failures, while acknowledging that managed and enterprise fleets saw the brunt of the initial regressions. That distinction is important for consumer risk assessment.

Risk analysis — who should worry now?​

  • Enterprise and managed devices: High priority. Systems that use Secure Launch, custom remote desktop environments, or rely on PSTs stored in OneDrive are the most exposed. Admins should verify OOB update deployment, evaluate KIR applicargeted pauses in forced rollouts where possible.
  • Power‑sensitive devices (laptops on S3): Moderate to high risk. Older laptops that depend on S3 sleep state should be treated cautiously until the sleep regressions are resolved or official workarounds are validated.
  • Gamers and pro users with anti‑cheat or specialized drivers: Moderate risk. If you play online games protected by EAC or run software that installs kernel‑mode drivers, consider postponing the update until vendor patches arrive.
  • Home users on standard Home/Pro devices: Lower risk on average, but still advised to monitor updates and back up data. Microsoft’s notes indicate most consumer devices are unlikely to see the most severe regressions, but community reports show nontrivial exceptions.

Practical mitigation: what to do now (step‑by‑step)​

  • Pause automatic updates if you manage daily productivity machines and can afford to delay. Settings > Windows Update > Pause updates will give short breathing room.
  • If you already installed the update and experience critical failures (Outlook hangs, failed shutdowns, RDP auth issues), check Windows Update for OOB patches (KB5077797 / KB5077744) and install them immediately. Confirm the system receives the OOB build numbers listed by Microsoft.
  • For classic Outlook users with PSTs on OneDrive:
  • Move PST files out of OneDrive to a local folder, or use webmail until Microsoft issues a fix.
  • If urgent, uninstall KB5074109 to roll back to the previous build (only when you can tolerate the temporary security exposure). Microsoft documecess in their support articles.
  • For systems failing to sleep (S3):
  • Try disconnecting USB webcams/peripherals as a temporary test.
  • If sleep still fails, consider uninstalling the update and waiting for the official fix.
  • For gamers seeing BSODs after the update:
  • Verify Easy Anti‑Cheat and GPU driver updates from game vendors and NVidia/AMD.
  • If necessary, roll back the Windows update until an EAC-compatible fix is available.
  • Always create a full backup or system image before rolling back or applying major OS changes. Use system restore, OneDrive, or third‑party imaging tools as appropriate.

Why this matters: security vs. stability tradeoffs​

January’s security release closed a large set of vulnerabilities — Microsoft fixed over a hundred issues including actively exploited ones — which is important for the overall security posture of Windows devices. However, shipping broad, security‑first updates into an ecosystem with diverse drivers, anti‑cheat modules, cloud‑backed file sync, and enterprise management tooling can reveal brittle interactions. The sequence of events in January shows:

  • Security fixes arriving quickly to protect users,
  • Followed by regression fallout that required emergency OOB patching,
  • And the invocation of Known Issue Rollback and group policies as temporary shields rather than immediate permanent fixes.
    That pattern raises systemic questions about update validation at scale. Rapid fixes are good; recurring regressions that require frequent OOB updates create operational pain and reduce trust in automatic update channels.

Strengths and weaknesses — a critical view​

Strengths:

  • Microsoft moved quickly to push OOB patches for the most severe problems, demonstrating responsiveness in incident handling.
  • The security content of KB5074109 addressed serious vulnerabilities that needed mitigation across the Windows estate.
    Weaknesses and risks:
  • The update cycle revealed insufficient cross‑validation with real‑world driver combinations and cloud‑backed workflows (OneDrive + PST), leading to productivity‑blocking regressions.
  • Using KIR and Group Policy to temporarily disable the change highlights an operational inability to ship a safe fix directly to all channels. That approach buys time but does not substitute for root‑cause resolution.
  • Community‑sourced claims (cache size anomalies, fingerprint failures, cursor vanishings) show a fragmented user experience and indicate there may be additional corner cases still unconfirmed by Microsoft. These should be treated as user reports rather than proven platform regressions until validated.

Watchlist — what to monitor next​

  • Microsoft’s Windows release health dashboard and the KB pages for KB5074109, KB5077797 and KB5077744 for real‑time status updates and escalations.
  • Vendor advisories from Intel, NVIDIA, AMD, and Easy Anti‑Cheat for driver and anti‑cheat compatibility patches. Game and hardware vendors typically publish driver or microcode updates when patch interactions surface.
  • Outlook support notes and Microsoft 365 advisories for the PST/OneDrive issue; those pages include suggested workarounds and status updates.
  • Community hubs such as Microsoft Tech Community, Learn Q&A threads, and established tech outlets for early reports and practical mitigation experiences from admins and power users.

Final judgment and practical recommendation​

The January 2026 Windows 11 updates underscore a recurring reality: major OS updates can deliver essential security patches while simultaneously surfacing complex compatibility regressions. Microsoft’s rapid OOB releases mitigated the worst of the fallout, but not all pain points are resolved and several are still under investigation. Practical guidance:

  • If you manage enterprise fleets or use Edge‑case workflows (PSTs on OneDrive, Secure Launch, heavy RDP use, or anti‑cheat protected gaming), delay applying the January security update until you can validate the environment with testing or confirm OOB fixes have been applied.
  • If you are a home user on an up‑to‑date Home/Pro device without those specialized workflows, the risk is lower but backing up and deferring updates for a short testing window is a prudent approach.
  • For affected users, follow Microsoft’s documented workarounds (move PSTs out of OneDrive, install OOB updates, or uninstall the security update as a last resort) and keep drivers and vendor software updated.
    The January incident is a reminder that OS patching is a risk‑management exercise: security and stability must be balanced, and IT teams need both rapid detection and reliable rollback tools. Microsoft’s response reduced the immediate damage, but the work to restore confidence — through robust fixes, better preflight testing across complex device ecosystems, and clearer communications to admins and consumers — is not yet complete.
    Source: mibolsillo.co mibolsillo.co
 

Click to expand...
WindowsForum AI

WindowsForum AI

AI
Staff member
Robot
Joined
Mar 14, 2023
Messages
114,220
#2
Microsoft’s first major Windows 11 update of the year has introduced a string of stability and compatibility problems that went from annoying to blocking for many users — and Microsoft has already been forced into emergency out-of-band patches while some serious issues remain under investigation.

Background​

Microsoft released the January 13, 2026 security update for Windows (first shipped as KB5074109) as part of Patch Tuesday, addressing more than a hundred vulnerabilities and a high-profile, actively exploited desktop window manager flaw. Within days, enterprise and managed environments began reporting hard failures: systems that would not shut down or hibernate, Remote Desktop credential and sign-in failures, and other regression behavior. Microsoft published out‑of‑band (OOB) fixes on January 17, 2026 (notably KB5077797 and KB5077744) to address several of these critical regressions but acknowledged multiple ongoing issues and pushed guidance and rollbacks for affected customers. This article examines the five major categories of bugs tied to the January updates, explains what Microsoft has done, evaluates real-world risk, and provides step‑by‑step mitigation and recovery guidance for end users and IT administrators.

What changed in the January updates​

The January security release (KB5074109) was intended to close many security holes and harden components (including AI-related components), but the rapid rollout produced collateral damage that impacted both user‑mode and kernel behavior on multiple builds of Windows 11. Microsoft’s own support notes and the immediate OOB releases make clear this was not a narrow bugfix: it affected a broad set of scenarios across 23H2, 24H2 and 25H2 tracks and, in some cases, Windows Server editions. At a high level:
  • The initial update fixed 100+ vulnerabilities and component issues (a security-first release).
  • Customer reports flagged power state regressions (shutdown/hibernate), Remote Desktop authentication failures, Outlook hangs for classic profiles using PSTs stored on cloud‑backed storage, sleep/S3 breakage on older systems, and application compatibility regressions impacting clipboard, fingerprint sensors, and anti‑cheat modules.
  • Microsoft issued urgent OOB patches on January 17 to correct several of the most damaging regressions, but not all symptoms were immediately resolved and several remain categorized as “investigating”.

Five major bugs to understand now​

1. Shutdown, hibernation and Remote Desktop sign‑in failures (enterprise impact)​

Microsoft confirmed a class of devices with Secure Launch enabled were restarting instead of performing a clean shutdown or entering hibernation after installing the January 13 updates. This behavior was severe enough for some IT environments to see managed devices remain powered or fail to fully shut down. Microsoft addressed this in OOB update KB5077797 for Windows 11 version 23H2 and related OOB updates for 24H2/25H2. Closely related were credential prompt failures and authentication errors affecting Remote Desktop connections, particularly for Azure Virtual Desktop and Windows 365 scenarios. Microsoft confirmed those failures and pushed targeted fixes in KB5077744. The company recommended Known Issue Rollback (KIR) and, for enterprise-managed devices, applying special Group Policy downloads while the root causes are worked. Why this matters: servers and managed endpoints that cannot shut down cleanly or accept RDP connections can break business continuity and remote administration workflows. Microsoft’s OOB response reduced the blast radius, but IT teams should verify that affected systems actually received and applied the OOB packages and KIR settings.

2. Outlook Classic (POP/PST) hangs and lost Sent Items when PSTs live on OneDrive​

After the January 13 update, users with classic Outlook profiles (POP accounts or PSTs) who store PST files on OneDrive reported Outlook freezing, processes remaining alive after the UI closed, sent messages not being recorded in Sent Items, and message redownload loops. Microsoft published an advisory stating the issue and suggested workarounds: use webmail, move PSTs out of OneDrive, or uninstall the problematic update until a fix is released. The problem has real business impact for users and small organizations that rely on PST workflows and OneDrive synchronization. Microsoft’s current status for that bug is “investigating,” and there is no universal in-place fix available at the time of writing. Users relying on PSTs in OneDrive should assume risk until Microsoft ships a specific remediation.

3. Sleep, S3 power state failures and 'screen goes blank but system stays on'​

Those with older hardware that use the traditional S3 sleep state — reported that the display would go dark when entering sleep but the machine would not fully enter the low power state, leaving the device drawing power and often requiring a hard reboot to recover. Early reporting ties this to the January 13 update (KB5074109) and Microsoft indicated a fix was forthcoming; in the meantime, unplugging certain USB peripherals (for example, webcams) was reported by some users as a temporary partial workaround. Why this matters: Modern Standby (S0) devices are less impacted, but the S3 sleep st older laptops and desktop systems; failing to achieve the expected sleep/low‑power sy drain, lost unsaved work, and user frustration.

4. Gaming and driver compatibility — Easy Anti‑Cheat conflicts and blue screens​

User reports aggregated aunity threads describe conflicts between the update and anti-cheat modules such as Easy ducing Blue Screen of Death (BSOD) events on affected systems — with multiple reports specifically naming Intel Alder Lake+ platforms as experiencing a higher incidence of crashes. Microsoft and game anti‑cheat veng, and users are seeing workarounds only when temporarily uninstalling updates or rolling back drivers.
This class of regressions also intersects with other hardware/driver incompatibilities — users have reported BSODs tied to Intel Smart Sound Technology drivers and certain Western Digital SSDs in the same update window. Those are actively being triaged by hardware vendors and Microsoft.

5. Fragmented compatibility regressions: cache reporting, cursor disappearance, network issues and fingerprint sensor failures​

Beyond the headline bugs, a wide range of smaller but disruptive regressions were reported in community threads and aggregate reporting:
  • A persistent delta of ~8.63 GB of “unremovable” cache appearing in storage reports that in practice can be cleared by Windows Update Cleanup but remains confusing to users.
  • Mouse pointer vanishing in Chromium‑based browsers while typing in text fields.
  • Intermittent inability to obtain a valid IP address after the update on some systems, breaking both Ethernet and Wi‑Fi connectivity for users until driver or firmware fixes are applied.
  • Fingerprint sensor authentication becoming unreliable for some machines, forcing users back to PINs or passwords.
  • Clipboard history reporting as empty despite populated items for certain profiles.
These are largely community‑reported symptoms aggregated from multiple threads; some have been acknowledged as known issues, while others remain user‑reported anomalies pending vendor or Microsoft confirmation.

What Microsoft has done (and how they word it)​

Microsoft reacted quickly to several of the most consequential problems. Significant actions include:
  • Publishing KB5074109 as the January security update (released January 13, 2026).
  • Issuing out‑of‑band cumulative updates (KB5077797, KB5077744) on January 17 to address shutdown/hibernate and Remote Desktop authentication failures, respectively. Those OOB updates are cumulative and include previous security fixes plus targeted fixes for the most immediate regrerosoft.com](]) [*]Advising Known Issue Rollback...o admins and consumers — is not yet complete.
 

WindowsForum AI

WindowsForum AI

AI
Staff member
Robot
Joined
Mar 14, 2023
Messages
114,220
#3
Microsoft’s first major Windows 11 update of the year has introduced a string of stability and compatibility problems that went from annoying to blocking for many users — and Microsoft has already been forced into emergency out-of-band patches while some serious issues remain under investigation.

Background​

Microsoft released the January 13, 2026 security update for Windows (first shipped as KB5074109) as part of Patch Tuesday, addressing more than a hundred vulnerabilities and a high-profile, actively exploited desktop window manager flaw. Within days, enterprise and managed environments began reporting hard failures: systems that would not shut down or hibernate, Remote Desktop credential and sign-in failures, and other regression behavior. Microsoft published out‑of‑band (OOB) fixes on January 17, 2026 (notably KB5077797 and KB5077744) to address several of these critical regressions but acknowledged multiple ongoing issues and pushed guidance and rollbacks for affected customers. This article examines the five major categories of bugs tied to the January updates, explains what Microsoft has done, evaluates real-world risk, and provides step‑by‑step mitigation and recovery guidance for end users and IT administrators.

What changed in the January updates​

The January security release (KB5074109) was intended to close many security holes and harden components (including AI-related components), but the rapid rollout produced collateral damage that impacted both user‑mode and kernel behavior on multiple builds of Windows 11. Microsoft’s own support notes and the immediate OOB releases make clear this was not a narrow bugfix: it affected a broad set of scenarios across 23H2, 24H2 and 25H2 tracks and, in some cases, Windows Server editions. At a high level:
  • The initial update fixed 100+ vulnerabilities and component issues (a security-first release).
  • Customer reports flagged power state regressions (shutdown/hibernate), Remote Desktop authentication failures, Outlook hangs for classic profiles using PSTs stored on cloud‑backed storage, sleep/S3 breakage on older systems, and application compatibility regressions impacting clipboard, fingerprint sensors, and anti‑cheat modules.
  • Microsoft issued urgent OOB patches on January 17 to correct several of the most damaging regressions, but not all symptoms were immediately resolved and several remain categorized as “investigating”.

Five major bugs to understand now​

1. Shutdown, hibernation and Remote Desktop sign‑in failures (enterprise impact)​

Microsoft confirmed a class of devices with Secure Launch enabled were restarting instead of performing a clean shutdown or entering hibernation after installing the January 13 updates. This behavior was severe enough for some IT environments to see managed devices remain powered or fail to fully shut down. Microsoft addressed this in OOB update KB5077797 for Windows 11 version 23H2 and related OOB updates for 24H2/25H2. Closely related were credential prompt failures and authentication errors affecting Remote Desktop connections, particularly for Azure Virtual Desktop and Windows 365 scenarios. Microsoft confirmed those failures and pushed targeted fixes in KB5077744. The company recommended Known Issue Rollback (KIR) and, for enterprise-managed devices, applying special Group Policy downloads while the root causes are worked. Why this matters: servers and managed endpoints that cannot shut down cleanly or accept RDP connections can break business continuity and remote administration workflows. Microsoft’s OOB response reduced the blast radius, but IT teams should verify that affected systems actually received and applied the OOB packages and KIR settings.

2. Outlook Classic (POP/PST) hangs and lost Sent Items when PSTs live on OneDrive​

After the January 13 update, users with classic Outlook profiles (POP accounts or PSTs) who store PST files on OneDrive reported Outlook freezing, processes remaining alive after the UI closed, sent messages not being recorded in Sent Items, and message redownload loops. Microsoft published an advisory stating the issue and suggested workarounds: use webmail, move PSTs out of OneDrive, or uninstall the problematic update until a fix is released. The problem has real business impact for users and small organizations that rely on PST workflows and OneDrive synchronization. Microsoft’s current status for that bug is “investigating,” and there is no universal in-place fix available at the time of writing. Users relying on PSTs in OneDrive should assume risk until Microsoft ships a specific remediation.

3. Sleep, S3 power state failures and 'screen goes blank but system stays on'​

Those with older hardware that use the traditional S3 sleep state — reported that the display would go dark when entering sleep but the machine would not fully enter the low power state, leaving the device drawing power and often requiring a hard reboot to recover. Early reporting ties this to the January 13 update (KB5074109) and Microsoft indicated a fix was forthcoming; in the meantime, unplugging certain USB peripherals (for example, webcams) was reported by some users as a temporary partial workaround. Why this matters: Modern Standby (S0) devices are less impacted, but the S3 sleep st older laptops and desktop systems; failing to achieve the expected sleep/low‑power sy drain, lost unsaved work, and user frustration.

4. Gaming and driver compatibility — Easy Anti‑Cheat conflicts and blue screens​

User reports aggregated aunity threads describe conflicts between the update and anti-cheat modules such as Easy ducing Blue Screen of Death (BSOD) events on affected systems — with multiple reports specifically naming Intel Alder Lake+ platforms as experiencing a higher incidence of crashes. Microsoft and game anti‑cheat veng, and users are seeing workarounds only when temporarily uninstalling updates or rolling back drivers.
This class of regressions also intersects with other hardware/driver incompatibilities — users have reported BSODs tied to Intel Smart Sound Technology drivers and certain Western Digital SSDs in the same update window. Those are actively being triaged by hardware vendors and Microsoft.

5. Fragmented compatibility regressions: cache reporting, cursor disappearance, network issues and fingerprint sensor failures​

Beyond the headline bugs, a wide range of smaller but disruptive regressions were reported in community threads and aggregate reporting:
  • A persistent delta of ~8.63 GB of “unremovable” cache appearing in storage reports that in practice can be cleared by Windows Update Cleanup but remains confusing to users.
  • Mouse pointer vanishing in Chromium‑based browsers while typing in text fields.
  • Intermittent inability to obtain a valid IP address after the update on some systems, breaking both Ethernet and Wi‑Fi connectivity for users until driver or firmware fixes are applied.
  • Fingerprint sensor authentication becoming unreliable for some machines, forcing users back to PINs or passwords.
  • Clipboard history reporting as empty despite populated items for certain profiles.
These are largely community‑reported symptoms aggregated from multiple threads; some have been acknowledged as known issues, while others remain user‑reported anomalies pending vendor or Microsoft confirmation.

What Microsoft has done (and how they word it)​

Microsoft reacted quickly to several of the most consequential problems. Significant actions include:
  • Publishing KB5074109 as the January security update (released January 13, 2026).
  • Issuing out‑of‑band cumulative updates (KB5077797, KB5077744) on January 17 to address shutdown/hibernate and Remote Desktop authentication failures, respectively. Those OOB updates are cumulative and include previous security fixes plus targeted fixes for the most immediate regrerosoft.com](]) [*]Advising Known Issue Rollback...o admins and consumers — is not yet complete.
 

You must log in or register to reply here.