KB5077744

Microsoft has released an out-of-band cumulative update, KB5077744, for Windows 11 version 25H2 (2025 Update). This update resolves sign-in failures during Remote Desktop connections. The issue appeared after installing the January Patch Tuesday security update.

The out-of-band update KB5077744 (Build 26200.7627) for Windows 11 version 25H2 fixes sign-in failures during Remote Desktop connections that occurred after installing the KB5073724 (Build 19045.6809) update. It resolves an error that caused users to encounter credential request problems when trying to connect to Windows 365 and Azure Virtual Desktop services via the Windows App. Microsoft had previously confirmed the issue and recommended temporarily using the classic Remote Desktop client or the web version of Windows App.

Note: Update KB5077744 is only available for manual installation from the Microsoft Update Catalog.

The out-of-band update KB5077744 includes both the security fixes from the previous update KB5074109 (Build 26200.7623) dated January 13, 2026, and additional important fixes.

Some users experienced sign-in failures during Remote Desktop connections. This problem affected the authentication steps for various Remote Desktop applications in Windows, such as the Windows App.

If you have installed previous updates, only the new fixes contained in this package will be downloaded and installed.

How the new features work:

KB5077744 (Build 26200.7627): This out-of-band patch fixes RDP authentication failures. The issue occurred after installing KB5073724 (Build 19045.6809), manifesting as an infinite credential prompt. Mechanism: fixed a conflict in the CredSSP and LSASS call chain that blocked session token transfer.

Windows 365 and Azure Virtual Desktop: Fixed an error in the Windows App component where the client couldn't properly handle authentication redirection. Technically: restored the IDL_RemoteDesktop_Client_Authenticate call in the RDP ActiveX control, broken due to TLS policy changes in the previous update.

Temporary workaround before the patch: Microsoft recommended using the classic RDP client (mstsc.exe) or the web version of Windows App. The classic client bypasses the modified Windows App stack, using direct authentication via CredUI without invoking changed APIs. The web version works over WebRTC and does not depend on local CredSSP.

The last 10 Windows updates: