Microsoft fixes Windows 10 auth issue impacting Remote Desktop

Microsoft has fixed a known Windows 10 issue causing smartcard authentication to fail when trying to connect using Remote Desktop after installing the cumulative updates released during last month's Patch Tuesday.

As explained by the company, devices attempting to make Remote Desktop connections to devices in untrusted domains might be unable to connect.

"After installing KB5005611 or later updates, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication," Microsoft explained.

"You might receive the prompt, 'Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials.' and 'The login attempt failed' in red."

Windows platforms affected by this issue include both client (Windows 10 21H1, Windows 10 20H2, and Windows 10 2004) and server (Windows Server 2022, Windows Serve 20H2, and Windows Server 2004).

Fixed via Known Issue Rollback

Microsoft has already rolled out a fix to address this issue via the Known Issue Rollback (KIR) feature to affected Windows 10 devices.

"This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster."

On enterprise-managed devices, customers can also install and configure group policies to resolve the issue.

Microsoft has released the following group policies to address this specific issue (a restart is required after configuring the Group Policy):

Redmond has been using the Known Issue Rollback feature to roll back computers impacted by problematic bug fixes to a working state since late 2019.

A fully working version of KIR was introduced in Windows 10 2004 when all components started working together as a complete system. 

While fixes issued through KIR are distributed via Windows Update, they are not delivered as actual updates. Instead, they are deployed by creating Windows Registry entries that disable changes made in previous updates.

Known Issue Rollout fixes usually propagate to all affected systems within 24 hours, and that restarting impacted computers may speed up the process.

Microsoft previously used Known Issue Rollout fixes to performance issues while gamingresolve printing issues, and app freezes and crashes.

Related Articles:

Microsoft says April Windows updates break VPN connections

Microsoft fixes bug behind incorrect BitLocker encryption errors

Recent Windows updates break Microsoft Connected Cache delivery

Microsoft: Recent updates cause Sysprep Windows validation errors

Microsoft fixes Windows Sysprep issue behind 0x80073cf2 errors