RDP and mapping issue after applying patch windows11.0-kb5068861-x64

Question

We have a 2 Windows environment, 1 environment on a Windows Domain and another environment on a Peer-to-Peer (P2P) network. We deployed Windows Security Update (windows11.0-kb5068861-x64) to both environments, and on the Peer-to-Peer computers were unable to map or RDP to computers the network. The computers were able to ping each other but mapping ability via Explorer or net use and Remote Desktop connection stopped working. Since the only change to the computers was the patch, uninstalling the patch windows11.0-kb5068861-x64 resolved the issue. Everything, so far, appears to the working on the computers connected to the Windows Domain. Has anyone run into this issue and/or have a resolution other than uninstalling the patch? Thanks.

---

Moved from: Sysinternals

Answer 1

It seems that the issue you are experiencing with Remote Desktop Protocol (RDP) and mapping after applying the Windows Security Update (windows11.0-kb5068861-x64) may be related to changes introduced by the patch. While I do not have specific information regarding this particular update, it is common for security patches to inadvertently affect network functionalities, especially in different network environments like Peer-to-Peer (P2P).

Here are a few general troubleshooting steps you might consider:

1. Check Firewall Settings: Ensure that the firewall settings on the Peer-to-Peer computers allow RDP and file sharing. Sometimes, updates can reset or modify firewall rules.
2. Review Group Policies: If applicable, check if any group policies are affecting the RDP settings or network sharing capabilities.
3. Network Discovery: Ensure that network discovery is enabled on the Peer-to-Peer network, as this can affect the ability to map drives and establish RDP connections.
4. Reconfigure RDP Settings: Sometimes, reconfiguring the RDP settings or re-enabling the Remote Desktop feature can resolve connectivity issues.
5. Check for Known Issues: Look for any known issues related to the specific update on Microsoft's official documentation or forums, as other users may have reported similar problems.

If uninstalling the patch resolves the issue, it may be a temporary solution while you investigate further or await a subsequent update that addresses this problem.

---

References:

• Microsoft Security Bulletin MS11-065 - Important
• Microsoft Security Bulletin MS12-054 - Critical

Answer 2

**Hello **OL-Alejandro, Marcelo (Online),

The KB you mentioned (windows11.0‑kb5068861‑x64) is a cumulative security update. In recent builds, Microsoft has hardened how SMB and RDP handle authentication. On domain‑joined machines, Kerberos and NTLM policies are centrally managed, so the update doesn’t cause disruption. On peer‑to‑peer networks, however, the patch can enforce stricter credential handling, which breaks “simple” share mapping or RDP connections that rely on local accounts.

What you can try before uninstalling the patch is:

• Check SMB settings: make sure “SMB 1.0/CIFS” isn’t required by your P2P setup. The update may disable legacy SMB.
• Review Local Security Policy → Security Options for changes to “LAN Manager authentication level.” Setting it to “Send NTLMv2 response only” is often required after these patches.
• For RDP, confirm that Network Level Authentication (NLA) is enabled on both sides. The patch may enforce NLA, and if one machine doesn’t support it, connections fail.
• If you’re using local accounts, ensure the same username/password exists on both machines. After the update, mismatched credentials are no longer tolerated.

I hope this helps,

If this guidance proves helpful, please kindly click “Accept Answer” so we know we’re heading in the right direction 😊. And of course, I’m here if you need further clarification or support.

Domic Vo.