We are experiencing the same issue and the fault is definitely rooted in the SID. Two machines with the same SID can't authenticate. Our solution is to create a new Windows User, which also get's a new SID. Or reset the current user with "Sysprep".
KB5065426 update stops file and print sharing from working
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
25 answers
Sort by: Most helpful
-
-
Karen W 10 Reputation points
2025-10-31T18:23:24.26+00:00 I work in a small office and we bought Windows 11 PCs at the same time and they have the same SID. I followed Susan Bradley's advice (askwoody) and ran the Microsoft Group Policy patch software https://download.microsoft.com/download/c6c70455-59ce-4d47-b13c-56b99d0435f1/Windows%2011%2024H2%2c%20Windows%2011%2025H2%20and%20Windows%20Server%202025%20KB5065426%20250923_06201%20Known%20Issue%20Rollback.msi
Then went into Local Group Policy editor entry for KB5065426...Known Issue Rollback > Windows 11, version 24H2,25H2... and disabled it.
I only ran this on the PC that accesses the shared data. After the reboot I can get to my shared data again!!!
-
Susan Bradley 251 Reputation points MVP
2025-09-11T18:55:01.2833333+00:00 Read that KB article.
"In Full Enforcement mode, if a certificate fails the strong (secure) mapping criteria (see Certificate mappings), authentication will be denied."
"If customers cannot reissue certificates with the new SID extension, we recommend that you create a manual mapping by using one of the strong mappings described above. You can do this by adding the appropriate mapping string to a users altSecurityIdentities attribute in Active Directory."
Per my read there is no "fix" coming from Microsoft. In a domain, you need to take action.
-
Intelligent-Cable 10 Reputation points
2025-09-14T21:34:43.41+00:00 You have cloned PC's , and have matching machine SID's
To change the machine SID's .. try sysprep, and to avoid this before cloning a PC, sysprep with with generalize so it's ready for cloning without a unique machine SID
On an affected PC
open an admin cmd
nagivate to
C:\Windows\System32\Sysprep
sysprep /generalize /oobe /shutdown
Test on a machine, be aware it will enter Oout of box experience after, and some apps / settings may be reset.
Machine SID's are for security and Microsoft aren't going to fix this, they assume you will sysprep with generalize pre cloning.
Let me know if that resolves this.
-
Wolfgang Aust 5 Reputation points
2025-09-16T15:09:51.6533333+00:00 Problem solved:
- Determine the SID on the computers using Sysinternals\PsGetsid64.exe (Sysinternals\newsid.exe doesn't work under Win11 24H2).
- Change the SID on one of the computers with a duplicate SID (without sysprep) using SIDCHG: (stratesave.com - follow the instructions carefully!)
- Everything's fine again . Researching the network error 0x80004005 almost drove me to despair.