Microsoft has resolved an issue in Windows 10 that would cause authentication failures when connecting to devices in an untrusted domain using Remote Desktop using smart card authentication.
The company explained that the issue only surfaced after installing the cumulative updates released that were part of September’s Patch Tuesday.
“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,” explains Microsoft.
We’re looking at how our readers use VPNs with streaming sites like Netflix so we can improve our content and offer better advice. This survey won’t take more than 60 seconds of your time, and we’d hugely appreciate if you’d share your experiences with us.
According to Microsoft, the issue pops up on several Windows 10 versions, including Windows 10 21H1, Windows 10 20H2, and Windows 10 2004, as well as on various Windows Server releases such as Windows Server 2022, Windows Serve 20H2, and Windows Server 2004.
Patched via rollback
Microsoft confirms that it has rolled out a fix to address the issue via the Known Issue Rollback (KIR) feature.
KIR is a Windows 10 specialty that enables Microsoft to revert buggy fixes delivered through WIndows Updates, in case they cause regressions and break functionality. According to BleepingComputer, Microsoft has been using KIR to revert fixes that introduce unexpected bugs, since late 2019.
Furthermore, KIR fixes don’t rollback security fixes, and although distributed via the Windows Update mechanism, they aren’t really updates in the truest sense of the word. KIRs are instead propagated as Windows Registry entries that simply disable the regression-causing changes made during a previous update.
While Microsoft has stated that the fix for the remote desktop authentication issue will propagate automatically to consumer devices and non-managed business devices, enterprise-managed devices can resolve the issue by installing and configuring the two released group policies.
Via BleepingComputer
