KB5065426 update stops file and print sharing from working

Kevin OBrien 205 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

27 answers

Sort by: Oldest
  1. 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?

    Was this answer helpful?

    1 person found this answer helpful.

  2. 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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  3. Assistec Informática - Rodeio Bonito-RS 0 Reputation points
    2025-09-25T12:38:44.18+00:00

    Bom Dia!! Aguém tentou ja criar um usuário com senha que compra os requisitos de segurança

    8 Digitos, Letras minusculas e mauisculas, numeros, caracteres ?

    Was this answer helpful?

    0 comments No comments

  4. Susan Bradley 261 Reputation points MVP
    2025-09-25T21:20:31.3233333+00:00

    Was this answer helpful?

    1 person found this answer helpful.

  5. James Imray 10 Reputation points
    2025-10-07T22:09:14.19+00:00

    This same update (KB5065426) stopped our machines RDCing 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 SSID 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".

    Good luck everyone!

    Was this answer helpful?


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.