Hey guys i have question after instaling KB5065426 on multiple Windows 11 in our company, we have problem with RDP and network shard folders ( the are denied, we have corect login and pass ). Do you know if there any plans for an official fix for this update in future ? Mark H • 10 Reputation points 2025-10-07T20:38:59.9033333+00:00 After all the problems I have experienced and hours of my life wasted troubleshooting Microsoft problems, (still cannot get Network shares to work), I will just throw all these machines away and go to a MAC. Support is useless and we all know for decades the troubleshooters are worthless. Enough is enough. 2 votes After all the problems I have experienced and hours of my life wasted troubleshooting Microsoft problems, (still cannot get Network shares to work), I will just throw all these machines away and go to a MAC. Support is useless and we all know for decades the troubleshooters are worthless. Enough is enough. MicheleP-7583 • 0 Reputation points 2025-10-17T07:59:59.35+00:00 I had a similar problem; I could not detect or connect to a local network, and I tried all the solutions listed on the various Microsoft troubleshooters or Q&As. The only thing that apparently worked was deactivating all the Windows firewalls. After doing that, and even after reactivating them, everything worked. 0 votes I had a similar problem; I could not detect or connect to a local network, and I tried all the solutions listed on the various Microsoft troubleshooters or Q&As. The only thing that apparently worked was deactivating all the Windows firewalls. After doing that, and even after reactivating them, everything worked. James Imray • 10 Reputation points 2025-10-07T22:15:07.28+00:00 This same update (KB5065426) stopped our machines RDC/RDPing to each other. Similarly, the issue was found to be that the machines had all been built and supplied to us with the same machine SSID. I found the easiest way to look up the machine SSIDs was in Powershell with the command "Get-LocalUser | Select-Object Name,SID" (without quotes and ignore the result from the last dash onwards). Uninstalling KB5065426 and pausing updates has worked as an interim solution. We are evaluating the implications of using a SID-changing tool like SIDCHG to change the machine SIDs. I understand it has less implications than running sysprep /generalize which "resets a lot of things". Can anyone from Microsoft please advise if this RDC/RDP problem will be fixed in a rollback/future update or do we need to live with the fact that going forwards we must ensure we don’t have any machines sharing the same machine SID? 2 comments Show comments for this answer Esteve Thomas • 0 Reputation points 2025-10-15T12:50:22.9033333+00:00 Good afternoon, Just to tell, I checked Monthly Update and I didn't see fix about our issue. To solve this issue, I launched Sysprep command with "Generalize" option. 0 votes Edgar Hennig • 0 Reputation points 2025-10-16T16:36:38.48+00:00 The KB5065426 update does not appear in the list of updates that can be uninstalled. KB5065426 cannot be uninstalled! 0 votes Sign in to comment Add comment This same update (KB5065426) stopped our machines RDC/RDPing to each other. Similarly, the issue was found to be that the machines had all been built and supplied to us with the same machine SSID. I found the easiest way to look up the machine SSIDs was in Powershell with the command "Get-LocalUser | Select-Object Name,SID" (without quotes and ignore the result from the last dash onwards). Uninstalling KB5065426 and pausing updates has worked as an interim solution. We are evaluating the implications of using a SID-changing tool like SIDCHG to change the machine SIDs. I understand it has less implications than running sysprep /generalize which "resets a lot of things". Can anyone from Microsoft please advise if this RDC/RDP problem will be fixed in a rollback/future update or do we need to live with the fact that going forwards we must ensure we don’t have any machines sharing the same machine SID? Esteve Thomas • 0 Reputation points 2025-10-15T12:50:22.9033333+00:00 Good afternoon, Just to tell, I checked Monthly Update and I didn't see fix about our issue. To solve this issue, I launched Sysprep command with "Generalize" option. 0 votes Good afternoon, Just to tell, I checked Monthly Update and I didn't see fix about our issue. To solve this issue, I launched Sysprep command with "Generalize" option. Edgar Hennig • 0 Reputation points 2025-10-16T16:36:38.48+00:00 The KB5065426 update does not appear in the list of updates that can be uninstalled. KB5065426 cannot be uninstalled! 0 votes The KB5065426 update does not appear in the list of updates that can be uninstalled. KB5065426 cannot be uninstalled!

Jason Roberts • 2,115 Reputation points • Independent Advisor 2025-09-25T08:42:17.81+00:00 Hi Daw, My name is Jason and I am an independent advisor. This is a common issue I face a lot of the the time recently with this update. This a known issue with the KB5065426 update they experience problems with Remote Desktop Protocol (RDP) and network shared folders , often getting incorrect password or access denied errors. Workarounds at this time would be as follows Although this is a known issue at this time, there is no official hotfix from Microsoft specifically for the RDP and network share issues caused by KB5065426. However, I have been advising my business clients to follow these instructions and they are then back up and running.: Uninstalling the Update: The most common and effective solution is to uninstall the KB5065426 update . This will immediately restore RDP and network share functionality. To do this, go to Settings > Windows Update > Update History > Uninstall Updates . Find the update and click "Uninstall." You may also need to pause updates to prevent it from automatically reinstalling. SID Conflicts: Some reports suggest the problem is related to Security Identifier (SID) conflicts, especially on machines that were cloned or imaged from the same source. . If uninstalling the update doesn't work, you might need to use a tool to change the SID of the affected machines. Registry and Network Settings: Other workarounds include adjusting network settings, such as ensuring the network is set to "Private" and that file and printer sharing is enabled. Some users have also had success with registry edits related to guest access or SMB client security signatures, though these should be done with caution. Future Fixes: While Microsoft hasn't officially commented on a specific fix for this issue, it's highly likely they are aware of it due to the widespread reports. These types of issues are often addressed in subsequent cumulative updates or through a Known Issue Rollback (KIR). Keep an eye on the official Windows release health dashboard for any announcements. 1 comment Show comments for this answer Edgar Hennig • 0 Reputation points 2025-10-16T16:37:12.41+00:00 The KB5065426 update does not appear in the list of updates that can be uninstalled. KB5065426 cannot be uninstalled! 0 votes Sign in to comment Add comment My name is Jason and I am an independent advisor. This is a common issue I face a lot of the the time recently with this update. This a known issue with the KB5065426 update they experience problems with Remote Desktop Protocol (RDP) and network shared folders , often getting incorrect password or access denied errors. Workarounds at this time would be as follows Although this is a known issue at this time, there is no official hotfix from Microsoft specifically for the RDP and network share issues caused by KB5065426. However, I have been advising my business clients to follow these instructions and they are then back up and running.: Uninstalling the Update: The most common and effective solution is to uninstall the KB5065426 update . This will immediately restore RDP and network share functionality. To do this, go to Settings > Windows Update > Update History > Uninstall Updates . Find the update and click "Uninstall." You may also need to pause updates to prevent it from automatically reinstalling. SID Conflicts: Some reports suggest the problem is related to Security Identifier (SID) conflicts, especially on machines that were cloned or imaged from the same source. . If uninstalling the update doesn't work, you might need to use a tool to change the SID of the affected machines. Registry and Network Settings: Other workarounds include adjusting network settings, such as ensuring the network is set to "Private" and that file and printer sharing is enabled. Some users have also had success with registry edits related to guest access or SMB client security signatures, though these should be done with caution. Future Fixes: While Microsoft hasn't officially commented on a specific fix for this issue, it's highly likely they are aware of it due to the widespread reports. These types of issues are often addressed in subsequent cumulative updates or through a Known Issue Rollback (KIR). Keep an eye on the official Windows release health dashboard for any announcements. Edgar Hennig • 0 Reputation points 2025-10-16T16:37:12.41+00:00 The KB5065426 update does not appear in the list of updates that can be uninstalled. KB5065426 cannot be uninstalled! 0 votes The KB5065426 update does not appear in the list of updates that can be uninstalled. KB5065426 cannot be uninstalled! Christine Cox • 0 Reputation points 2026-02-01T00:16:11.6466667+00:00 I finally was able to see my old computer from my new comptuter and started copying files over but the screen saver would come on and stop the process. I tried every possible way to stop the computer from "falling asleep" and it does not work. Now I can't see the files on my old computer anymore. Why after all these years Microsoft never does any better?? 0 comments No comments Sign in to comment Add comment I finally was able to see my old computer from my new comptuter and started copying files over but the screen saver would come on and stop the process. I tried every possible way to stop the computer from "falling asleep" and it does not work. Now I can't see the files on my old computer anymore. Why after all these years Microsoft never does any better?? James Imray • 10 Reputation points 2025-11-03T23:23:26.9866667+00:00 We have tested rebuilding machines from installation media - this successfully created unique computer SIDs on the reinstalled machines. I appreciate this is not pratical for installations with large numbers of machines with the same Computer SID, however, if the RDC connections are typically only from one or two administrator/master machines then only rebuilding those machines should allow them to RDC to all the others that still have the same computer SID. This article indicates this issue is here to stay unless unique computer SIDs are used - https://www.neowin.net/amp/microsoft-quietly-makes-a-requirement-mandatory-for-windows-11-25h2-24h2-installations/#:~:text=Aside%20from%20these,s%20official%20site. 0 comments No comments Sign in to comment Add comment We have tested rebuilding machines from installation media - this successfully created unique computer SIDs on the reinstalled machines. I appreciate this is not pratical for installations with large numbers of machines with the same Computer SID, however, if the RDC connections are typically only from one or two administrator/master machines then only rebuilding those machines should allow them to RDC to all the others that still have the same computer SID. This article indicates this issue is here to stay unless unique computer SIDs are used - https://www.neowin.net/amp/microsoft-quietly-makes-a-requirement-mandatory-for-windows-11-25h2-24h2-installations/#:~:text=Aside%20from%20these,s%20official%20site.