KB5065426 update stops file and print sharing from working

Kevin OBrien 195 Reputation points
2025-09-10T16:09:06.4466667+00:00

I was having issues with multiple locations using windows file and print sharing with password sharing. I found windows update KB5065426 was installed and that my file and print sharing options were turned off. I also found that networks were set to public that had previously sent to private.

Even after setting the settings back, the computers would not working with file and print sharing and I had to uninstall the update to get the functionality to work.

Windows for home | Windows 11 | Windows update
{count} votes

25 answers

Sort by: Most helpful
  1. Klaus 5 Reputation points
    2025-09-16T18:34:54.01+00:00

    I don't know if this will be helpful, but...

    The problem as shown in the title appeared on 4 of my computers in geographically very distant local networks. Now it seems to be that I do have a solution.

    1. I checked my computers with 'sfc /scannow' and 'dism / online /cleanup-image /restorehealth' and found that the computers having the problem reported heavy bugs in health. The named programs repair such. --- and: very important: they have had the bugs KB5065426 was installed!!!
    2. After repair I removed KB5065426 and reinstalled it on the now healthy system.

    Success... (for at least now one main computer.) --- Tomorrow I will try to get it running on a second one.

    I hope that this might be a way to solve the mal-function of KB5065426.

    Greetings

    1 person found this answer helpful.

  2. Susan Bradley 56 Reputation points
    2025-09-18T05:06:53.3633333+00:00

    You can detect the SMBv1 status without elevation by running the Get-SmbServerConfiguration command: Get-SmbServerConfiguration | Format-List EnableSMB1Protocol

    What is the status of that?

    1 person found this answer helpful.

  3. Joseph Cavallaro 10 Reputation points
    2025-09-24T22:02:22.6333333+00:00

    A workaround that seems to be working consistently for us is to map the network share via IP address instead of name. Otherwise removing the "update" is the only other fix that has worked.

    After almost every removal we have to run the sfc /scannow command.

    Hope this helps someone.

    1 person found this answer helpful.
    0 comments No comments

  4. Susan Bradley 251 Reputation points MVP
    2025-09-25T21:20:31.3233333+00:00
    1 person found this answer helpful.

  5. Nicholas Page 251 Reputation points
    2025-09-13T16:31:25.97+00:00

    Facing this exact issue on two system at home, one was cloned from the SSD of the other and I just changed the name and Windows license etc and has been working fine for years until now...all file/printer sharing and RDP is dead, just keeps saying incorrect user/pass. All the normal stuff is verified, private network, sharing on, etc etc and certain it is due to the update plus same SID as follows:

    I verified both machines do have the same SID.

    I tried uninstalling KB5065426 from both systems but that did not resolve.

    Next I removed KB5064081 from both systems and reboot and now SMB/RDP is working normally again.

    In my process of troubleshooting I found that the Remote Desktop Classic Windows app actually still worked also but, the regular RDP would not, so the RDP Classic app must authenticate differently? I'm not sure if you can even get or install this still since the newer "Remote Desktop" app is depreciated and maybe not working at all.

    I am considering trying SIDCHG on one of them as a long term solution since I assume Microsoft will not maybe any attempt to revert this dispite what will likely be millions of impacted systems. Please us know if you tries SIDCHG and any problems or side effects or other issues are encountered.


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.