Microsoft issues emergency patch for latest Windows bugs – grab it ASAP

Microsoft releases out-of-band updates after January Patch Tuesday bugs

Microsoft has issued emergency, out-of-band patches to resolve a pair of bugs introduced by its January 2026 Patch Tuesday rollout. The original update, released on January 13, addressed more than 110 security vulnerabilities, including several rated critical and at least one reported as exploited in the wild. However, it also introduced new reliability issues affecting Windows 11, Windows 10, and various Windows Server versions.

Out-of-band updates are not part of Microsoft’s normal monthly cadence; they’re typically reserved for time-sensitive fixes when an issue is disruptive enough to warrant faster distribution. In this case, the problems range from Remote Desktop sign-in failures to shutdown and hibernation behavior on certain secured Windows 11 systems.

What went wrong: two bugs tied to January’s security update

Bug 1: Remote Desktop sign-in failures for Cloud PCs

The first issue impacts users attempting to remotely connect to a Cloud PC through Microsoft’s Remote Desktop ecosystem—particularly scenarios involving the Windows App and services like Azure Virtual Desktop and Windows 365.

Microsoft said that after installing the January 2026 security update, some users may encounter credential prompt failures, resulting in sign-in errors in certain remote connection applications. The effect is especially noticeable in environments where authentication prompts are required to complete remote sessions.

Affected platforms called out in Microsoft’s guidance include:

• Windows 11 (version 25H2, and also listed alongside 24H2 in the patch documentation)
• Windows 10 (version 22H2 ESU)
• Windows Server 2025

Organizations that rely on Cloud PCs for hybrid work or contractor access may feel the impact more sharply, since Remote Desktop authentication issues can block routine access to line-of-business apps.

For reference on Microsoft’s Cloud PC service, see the official Windows 365 page.

Bug 2: Windows 11 23H2 restarts instead of shutting down or hibernating

The second bug is narrower in scope but potentially more disruptive for managed-device fleets. Microsoft says some PCs running Windows 11 version 23H2 with Secure Launch enabled may restart instead of shutting down or entering hibernation after the January 13 update.

Secure Launch is part of Microsoft’s security stack designed to help protect devices from firmware-level threats—such as bootkits—by using virtualization-based protections early in the boot process. While it’s often discussed alongside Secure Boot, Microsoft positions Secure Launch more squarely for managed organizational PCs.

In affected cases, users may attempt to shut down or hibernate, only to find the machine reboots—an outcome that can:

• Interrupt patching windows and after-hours maintenance
• Confuse power-management policies
• Create user frustration (especially on laptops expected to hibernate)

For broader Windows security context, Microsoft’s Windows Security overview explains how protections like virtualization-based security fit into the platform.

Who needs the emergency updates—and who can wait

Microsoft’s guidance is straightforward: install the out-of-band patches only if you’re affected. If your device is running one of the impacted Windows versions and you’re seeing the described behavior, the fix should appear through Windows Update.

To manually check:

• Windows 11: Settings → Windows Update → Check for updates
• Windows 10: Settings → Update & security → Windows Update → Check for updates

In managed environments, many users won’t be able to install these updates directly. Instead, IT teams will typically deploy them via enterprise tooling (for example, Windows Update for Business, Microsoft Configuration Manager, or other management platforms). If you’re on a corporate device, Microsoft advises waiting for your IT administrators to push the fix.

If your organization is already investing in automation to streamline patch workflows and reduce manual effort, it may be worth reviewing process improvements such as Driving Productivity at Scale with Microsoft Power Automate Consulting to help standardize update checks, notifications, and remediation steps.

KB numbers and affected Windows versions

Microsoft published separate updates depending on the OS version. The company’s support pages list the details and installation requirements.

Here are the versions and KBs referenced in the guidance:

• Windows 11, versions 25H2 and 24H2: KB5077744
• Windows 11, version 23H2: KB5077797
• Windows 10, version 22H2 ESU and Windows 10 Enterprise LTSC 2021: KB5077796
• Windows Server 2025: KB5077793
• Windows Server 2022: KB5077800
• Windows Server 2019 and Enterprise LTSC 2019: KB5077795

Why out-of-band patches matter—especially after major security releases

January’s Patch Tuesday was a large security drop, and large security drops can sometimes expose edge cases in authentication and power-management behaviors—particularly in mixed environments where:

• Multiple Remote Desktop clients are in use
• Cloud PC services are integrated with conditional access
• Security features like Secure Launch are enabled on only part of a fleet

For end users, the key takeaway is pragmatic: if you’re unaffected, you may not need to do anything beyond normal update hygiene. But if you’re seeing Remote Desktop credential failures or unexpected restarts when shutting down, Microsoft’s out-of-band updates are intended to restore normal behavior.

What to do next

• If you use Remote Desktop/Cloud PCs and sign-ins started failing after January’s update, check Windows Update for the relevant out-of-band patch.
• If you’re on Windows 11 23H2 with Secure Launch enabled and shutdown/hibernate triggers a restart, install the out-of-band fix when offered.
• If you’re on a managed device, contact your IT team or wait for the enterprise deployment.

As always, keeping Windows current remains one of the most effective baseline defenses—especially when Microsoft flags vulnerabilities as actively exploited. For official product and update documentation, Microsoft’s main hub at Microsoft is a good starting point for security and platform guidance.

Source: Read Original Article