This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 18%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPD%3C/text%3E%3C/svg%3E)
We are experiencing a reproducible issue with Remote Credential Guard (RCG) when connecting from Windows 11 24H2 clients to a Windows Server 2025 RDP host. Remote Credential Guard works correctly before installing update KB5072033 on the client. Immediately after installing this update, RCG stops functioning.
The issue is fully reproducible and affects only Windows 11 24H2 clients where KB5072033 is installed. The Windows Server 2025 host has also received the December cumulative update, but this does not change the behavior: RCG still fails when the client has KB5072033 installed.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 31%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERT%3C/text%3E%3C/svg%3E)
Microsoft, any progress in this? it is a showstopper for Server 2025 deployment!!
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 98%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDC%3C/text%3E%3C/svg%3E)
Hello,
I've managed to find confirmation of this issue, posted on Reddit by u/SteveSyfuhs.
https://www.reddit.com/r/activedirectory/comments/1gqq27g/comment/o0aso8c/
Additionally, I've installed KB5077241 on my Windows 11 25H2 client but installing this update didn't fix the Remote Credential Guard issue between Windows 11 25H2 client (26200.7922) and Windows Server 2025 RDP host (26100.32370).
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 59%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGK%3C/text%3E%3C/svg%3E)
Steve Syfuhs: "Sadly yes. Tooling problem. Fix is getting expedited. Please don't ask when. I don't know."
We're slowly getting desperate here.
A few months ago, we created a new RDS farm, but RCD wasn't working. We upgraded Windows Server 2022 to Windows Server 2025, and RCD started working again. Then the 2025-12 update came along and RDC stopped working again.
Now we're considering rebuilding the entire farm with Windows 2022. I no longer have any confidence in Windows Server 2025 :-(
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 55.00000000000001%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAK%3C/text%3E%3C/svg%3E)
Same problem. Could someone please urgently look into it ... ?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 21%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC7%3C/text%3E%3C/svg%3E)
Can anyone official from Microsoft confirm this? We also seeing this issue @Customers with Windows 11 24H2 and 25H2 after the KB5072033 update.
I would also like to highlight an additional point that further confirms this is a regression introduced by KB5072033.
Before installing KB5072033 on Windows 11 24H2 clients:
RCG did not work when connecting to Windows Server 2022
After installing KB5072033:
RCG no longer works with Windows Server 2025
RCG now works correctly with Windows Server 2022
This is the exact opposite behavior compared to before the update. No configuration changes were made on either the clients or the servers. The only change was the installation of KB5072033 on the Windows 11 24H2 clients.
This inversion strongly suggests that the update modifies the internal behavior of the RDP/CredSSP/Kerberos stack in a way that breaks compatibility with Windows Server 2025, even though the server is fully updated (including the December cumulative update).
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 90%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQQ%3C/text%3E%3C/svg%3E)
Hello Pierre DESTRÉE,
Thank you for sharing the detailed findings regarding Remote Credential Guard (RCG) behavior between Windows 11 24H2 clients and a Windows Server 2025 RDP host. Based on your description, the issue appears directly linked to the installation of update KB5072033, as RCG functions normally prior to applying this update and fails consistently afterward. At this time, the behavior you are seeing aligns with a known regression introduced in the update, and Microsoft is actively investigating the impact on RDP authentication and RCG negotiation. While the Server 2025 cumulative update does not resolve the issue, the current recommended workaround is to temporarily uninstall KB5072033 on affected clients or pause updates until a corrective patch is released.
You may also monitor the Windows Release Health dashboard for official status updates, as fixes for authentication‑related regressions are typically delivered through subsequent cumulative updates.
I hope this information helps you stabilize your environment while Microsoft works on a permanent resolution. If this guidance addresses your question, please consider clicking “Accept the Answer” so that others in the community can benefit from the findings as well.
Thank you so much!!
Best regards,
QQ.
Thank you for your response.
If this behavior is expected or already known internally, could you please clarify why it is not documented anywhere, including:
Remote Credential Guard is a critical security feature, and this update clearly changes its behavior in a way that breaks TGT forwarding between Windows 11 24H2 clients and Windows Server 2025, even when both sides are fully updated (including the December cumulative update on the server).
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 8%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKC%3C/text%3E%3C/svg%3E)
Are you able to provide a link to the known issue rollback for this? https://learn.microsoft.com/en-us/troubleshoot/windows-server/installing-updates-features-roles/known-issue-rollback
