KB5065426 update stops file and print sharing from working

Kevin OBrien 205

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.

Eugene Mollentze 65 Reputation points

2025-09-11T07:09:26.28+00:00

Morning. This same issue happened on my sites. the ONLY way to make it working again is to uninstall the kb5065426 update. Even after doing as mentioned above, the issue persists.

This is something that needs to be avoided in regards to we who have large sites/organizations that we need to run.

Please let us know if there is a fix for this. the stress is through the roof at the moment.
TSENG 150 Reputation points

2025-09-11T09:05:36.2866667+00:00

There are thousands of computers in the company Sharing files and printers this way is causing chaos after the KB5065426 update! Help! Microsoft - wake up and fix this issue!
олексий горбатько 90 Reputation points

2025-09-12T07:13:39.54+00:00

After installing this package, when I try to access a shared folder, the system asks for a login and password. I enter the credentials in the format server\username and the correct password, but Windows keeps showing an error: "The username or password is incorrect." I am sure the credentials are 100% correct. This seems to be a Windows issue.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Michael Burk 50 Reputation points

2025-09-12T08:29:05.49+00:00

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".
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Winuker 0 Reputation points

2025-09-12T09:44:56.4566667+00:00

Microsoft deberia revisar esto, no se puede permitir tal error.
олексий горбатько 90 Reputation points

2025-09-12T11:04:57.34+00:00

Yeeay man the problem is the same SID.

THANKYOU
Tainã Andrade 0 Reputation points

2025-09-12T13:40:32.2333333+00:00

I have the same problema here. With a lot of PCs
Giulio Gaudio 60 Reputation points

2025-09-12T15:12:44.2733333+00:00

Adding a new user the SID remains the same, exception the latest four digit that increase but are UNUSEFUL to solve the SHARE problem that remains because all the inital characters of the SID are the SAME for ALL the new users yet create.... last four digits are 1001-1002-1003 for each new user you will add. So problaby the MASTER part of SID it is create by OS during installation prcedure.
Dwight Dingus 5 Reputation points

2025-09-12T16:47:19.4+00:00

Removing it worked for me! Many thanks!
Eric Joris 0 Reputation points

2025-09-13T12:22:28.9766667+00:00

Same problem here.
Clif 5 Reputation points

2025-09-13T14:39:58.5066667+00:00

I have same issue with KB5065426. I have tried all the suggestions and to no avail. the only solution at this point is to remove the update.

For those that do not that savvy about windows, be aware that you do not want to do use the recovery option, you want to go to update history and scroll down to the related setting section and click on uninstall updates. here a list of the recent updates will appear. they will be sorted by date and newest may be on the top but not always. Pay Attention to the dates and look for KB50655426

but if you do not pause the updates, it will reinstall it within hours in my case. i have paused updates for as far out as you can, seems different computers offer different lengths you can do this.

hope fully in the next couple of weeks Microsoft will have a new update that fixes this issue.
Nicholas Page 256 Reputation points

2025-09-13T16:35:18.81+00:00

Facing this exact issue on two (non-preview now) 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 make 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.
Steve Gutteridge 10 Reputation points

2025-09-14T11:05:21.47+00:00

This update has killed the Samba 1 share on my Buffalo Link station NAS, on two different machines. Tried everything but only uninstalling this update has worked.
LOUIS LOPEZ 25 Reputation points

2025-09-14T15:43:01.4733333+00:00

The update is now not removable. It is part of the OS and cannot be uninstalled now. I have 3 duplicate SIDs because I bought computers from china that were cloned. I need a SID changer or reload the OS from scratch to fix my issue. It is not an SMB 1.0 or any SMB issue. Microsoft has blocked duplicate SIDs from being able to communicate with each other.
LUIS MIGUEL CALDERON GAVIRIA 0 Reputation points

2025-09-15T07:37:03.6266667+00:00

hola!! el problema persiste por mas de que elimine la actualizacion o haga lo que considere medianamente bien, pero seguimos con el problema. dos equipos con el mismo problema con actualizaciones todos los dia.
GJO 0 Reputation points

2025-09-15T17:58:34.3+00:00

After install that update "KB5065426" I get two laptop with BitLocker enable that now is asking for the recovery key every time is turn on the laptop and it doesn't matter if you enter the recovery key it keep asking for the key.

The only way is if you hit "skip" Windows boot and try to repair the Bitlocker but ending asking for the recovery and after enter the key Windows come up but the problem stay.
Paul Woodward 10 Reputation points

2025-09-16T02:20:15.8+00:00

Here is a solution I found. I did use SIDCHG (https://www.stratesave.com/html/sidchg.html)

Step 1. Uninstall any antivirus, then disable Defender

Open Windows Security → Virus & threat protection.

Under Virus & threat protection settings, click Manage settings.

Toggle Real-time protection → Off.

Step 2. Run SIDCHG from CMD prompt as Admin.

sidchg64-3.0m.exe /R

You can use trial key (78@5i-QwUJM-woQEE-Kv). Verify on their web site as it may change.

Step 3. Reboot then reinstall antivirus.

Note: I checked SID before and after using Power Shell:

(Get-CimInstance Win32_UserAccount -Filter "Name='$env:USERNAME'").SID -replace '-\d+$',''

This worked for me for 2 clients, good luck!
Steve Taylor (Staff) 5 Reputation points

2025-09-16T09:37:04.4766667+00:00

We also have major issues with this update. It stops certain software being run from mapped drives and breaks some of our printers. The fixes suggested do not make any difference on our system and we don't have duplicated SIDs.
David 0 Reputation points

2025-09-16T11:32:51.1566667+00:00

We're having the same problem on two computers. They haven't been cloned, but they have the same SID. I tried with a new user with a different SID, and the problem persists.

The problem is since the installation of kb5065426
LOUIS LOPEZ 25 Reputation points

2025-09-16T13:48:29.74+00:00

I removed the patches on three computers and something triggered that the patches are no longer removable even using powershell. Microsoft throws an error that the patches are now required and cannot be removed.
Mike Horton 0 Reputation points

2025-09-16T18:37:29.57+00:00

I have been having problems on two networks. First started on one printer sharing stopped working, \computername asked for password, entered uname and password. Said password was wrong, I knew it wasn't. Today another network called with file sharing issues. After numerous hours looking for a solution, I began looking at windows update and discovered that some computers had received KB 5065426 and some had not. I decided to remove it and file sharing came back. I then went directly to the network with the print sharing issue, and removed that update and printing was restored. I know we are supposed to keep things safe for the clients, but honestly, nothing working is not the answer. Find another way Microsoft, cause this is not helping anyone. I now have clients that are asking me to get them away from Microsoft products.
Amina Mubarak Hamad 0 Reputation points

2025-09-17T08:16:42.21+00:00

We are facing the same issue. workstations has different SIDs.. uninstalling the update using command 'wusa /uninstall /kb:5065426' solved the file sharing issue.

hope that Microsoft will urgently provide another update solving the issue as SMB and file/ print sharing are very important for organizations
Steve Gutteridge 10 Reputation points

2025-09-17T10:18:27.2633333+00:00

The exact same issue occurs on Windows 10 with update KB5065429, and the above "Answer" doesn't work on that either.
Clif 5 Reputation points

2025-09-17T16:09:30.5033333+00:00

just published on https://www.bleepingcomputer.com/news/microsoft/microsoft-says-windows-september-updates-break-smbv1-shares/ Microsoft is now working to resolve this issue, and until a fix is available, it has provided impacted customers with a temporary workaround.

This requires them to allow traffic on TCP port 445, which will cause the Windows SMB connection to resume successfully by switching to using TCP instead of NetBT.

read article for more details. but even though it says SMB1 I think it affects SMBv2 also.

i removed the update and am going to pause updates until the fix comes out.
Steve Gutteridge 10 Reputation points

2025-09-17T18:00:54.4566667+00:00

I already have port 445 open and it doesn't help.
Rameo64 0 Reputation points

2025-09-17T20:51:08.0166667+00:00

I uninstalled the kb:5065426 via powershell on my laptop and mini, that I use as a server with all of my hard drives attached to. I can't connect to the computer or the hard drives, but I can connect to my mini computer via RDP. Any ideas how to get back to my mini computer?
Brad 0 Reputation points

2025-09-18T02:48:13.9333333+00:00

Update has reinstalled and now even using that command doesn't uninstall update.
Amina Mubarak Hamad 0 Reputation points

2025-09-18T04:54:39.54+00:00

try to run:

'sfc /scannow' then 'dism /online /cleanup-image /restorehealth'
Aeris_Valetine 40 Reputation points

2025-09-19T00:54:41.4233333+00:00

me too, i have de same problem now
Antoin Currie 0 Reputation points

2025-09-19T09:24:53.42+00:00

DFS Replication for me also broke after installing this update
Steve Taylor (Staff) 5 Reputation points

2025-09-22T15:32:37.3533333+00:00

Just to update on our situation within our environment. ctl3d32.dll was the culprit for our issues as KB5065426 removes the file from the windows system folder / folders. This stopped our revelation database system from working.
Joseph Cavallaro 10 Reputation points

2025-09-24T21:48:59.99+00:00

So at first we were thinking it was a DNS issue but it is related to the update. A workaround that seems to be consistently working is to map the drives by IP address vs. name.

Removing the update does require a sfc /scannow to be run on almost every machine we have removed the update from.
GJO 0 Reputation points

2025-09-24T23:08:32.6+00:00

Hi,

Do someone has tried to create a new rule in the Windows Defender Firewall with Advanced Security under Inbound Rules and Outbound Rules for the port 445 to give full access to that port and force Windows to allow the file and print sharing?

That problem resembles the same situation when that port is blocked in the firewall.
Jim McLeod 0 Reputation points

2025-09-25T18:23:03.31+00:00

Was unable to successfully uninstall KB5065426 on my server - located and initiated an update removal, after reboot the update still shows up, Unable to initiate another update removal. Forced to perform workarounds to access my business data.

Will be installing Linux for evaluation, this is untenable.
Stephen Grimmer 0 Reputation points

2025-09-25T22:14:33.9533333+00:00

uninstalling this KB fixes event id event id 6167 when mapping a drive...
Aeris_Valetine 40 Reputation points

2025-09-26T07:29:32.7733333+00:00

When this updated on windows 11?
David 0 Reputation points

2025-10-08T09:35:32.4733333+00:00

I'm seeing more and more computers experiencing this problem. What's the solution?
GJ Eldering 0 Reputation points

2025-10-10T15:35:32.3833333+00:00

I'm also having trouble creating Linux shares in Windows 11.

I keep getting error: 0x80070043.

I've tried everything, unfortunately, without success.

Ping to Linux works fine, and from Linux, I see the share on Windows 11.

So, there's an error creating the shares from the Linux PC to Windows 11.

I hope Microsoft fixes this soon.
ahmad hazwan mohd adris 0 Reputation points

2025-10-15T01:35:48.36+00:00

any update from october 2025 can solve the issue. i need to reimage a lot of device from many site since the update cannot uninstall.
Susan E Bradley, CPA/CITP/CFF, GSEC 50 Reputation points

2025-10-15T03:55:49.16+00:00

https://www.askwoody.com/forums/topic/ms-defcon-4-finally-24h2/#post-2814835 See if the September updates help
James Imray 10 Reputation points

2025-10-30T02:04:48.78+00:00

I am no expert but I undestand the problem is with duplicate machine SIDs (not duplicate user IDs) which is why you are still having this problem. The machine SID is the user SID after the last "-" and any numbers after that are removed.

I check machine SIDs in Powershell with the command "Get-LocalUser | Select-Object Name,SID" (without quotes and ignore the SID result from the last dash onwards).
八神アンドレ伊織 40 Reputation points

2026-01-21T05:06:31.5566667+00:00

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

This rollback fixes these issue e.e

27 answers

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
LOUIS LOPEZ 25 Reputation points

2025-09-16T04:12:12.3466667+00:00

Message: My password is incorrect. - I call horse hockey.

I had three computers with matching SIDs because they were cloned by the manufacturer.

They were able to map drives to each other and RDP to each other and they all have Windows 11 Pro.

A few updates from Microsoft broke that connection.

Those updates were KB5065426 and KB5064401.

They moved my network from Private to Public and disabled File and Print Sharing and network discovery without my permission.

I moved them back to Private and enabled the File and Print and discovery.

That did not work. I removed those KBs at 3:00am and that solved the problem. At 8:00am the same day a few hours later, those KBs came back. I removed them again, and checked File and Print and Public/Private. This time, it did not work. I tried to reinstall KB5065426 and then hope to remove it. It was not listed in updates and also it would not let me install it because it stated that it was already installed. I attempted to powershell remove the KB5065426 with the following command.

wusa /uninstall /kb:5065426

The error message showed Security Update for Microsoft Windows (KB5065426) is required by your computer and cannot be uninstalled.

I tried stepping back to SMB 1.0 and match all LMs.

SMB 1.0 Server are on all machines and matching

SMB 1.0 Client are on all machines and matching

LmCompatibilityLevel 1 on all machines

RequireSecuritySignature Workstation and Server disabled on all machines

AllowInsecureGuestAuth on set on all machines

EnableLinkedConnections on all machines

Removing stored credentials did not work

Using alternate credentials did not work

Tried new matching accounts created on all machines did not work

Changing the firewall to default policy and created an allow all in and out rule did not work on all machines

PsGetsi64.exe confirmed the SID matches

The identical SIDs can communicate File and Print and RDP to all non-matching SIDs and all non-matching SIDs can communicate with each other and back to the identical SIDs. Only the matching SIDs CANNOT communicate with each other using File and Print and also CANNOT communicate using RDP. The error message is the password is incorrect and they password and usernames are perfectly matching no matter what account I use or alternate credentials. They just will not communicate.

sysprep killed one computer to the point I couldn't install windows on that hardware without moving the SSD to a new piece of hardware and installing Windows and then moving the SSD back to that machine. The other machine I installed Windows Clean and instead of creating a windows.old folder, it wiped out all data including folders in the root directory. All three SIDs are unique and can communicate with each other again. I am pretty sure the Stratesave Systems SIDCHG would work because others stated it would. This used to be owned by Microsoft was was sold off to them (I think). What do I know. I am just a dummy that can't get two computers to communicate peer-to-peer.
Was this answer helpful?

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
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.
Was this answer helpful?

1 person found this answer helpful.
LOUIS LOPEZ 25 Reputation points

2025-09-14T21:47:48.5033333+00:00

Yesterday, came to the same conclusion. sysprep seemed to be the way to go.

What I did and what the outcome was so far.

cmd as Administrator

rem C:\Windows\System32\Sysprep\sysprep.exe /generalize /oobe /shutdown

Failed
%WINDIR%\system32\sysprep\sysprep.exe /generalize /oobe /quit

powershell

Failed - there were packages that needed to be removed

Remove-AppxPackage -Package Microsoft.WidgetsPlatformRuntime_*_x64__8wekyb3d8bbw

Remove-AppxPackage -Package Microsoft.Winget.Source_2025.911.2246.5_neutral__8wekyb3d8bbwe

C:\Windows\System32\Sysprep\sysprep.exe

select OOBE Generalize and reboot

Pending the outcome because I was doing it from remote. I need to go in to see the result

...Okay This edit follows up on sysprep. The computer is Operating System usable and installation bricked. Cannot boot to windows at all now. Boot to Windows 11 Repair failed. Startup repair failed. Attempted to install on the same partition. Failed. Deleted all non-essential partitions and try to install to the partition containing Windows as a new install. Failed. Moved all data from the root of c:\ to c:\root leaving zero folders of any kind in the root, then install Windows clean, failed. Next step is to wipe all partitions and reinstall. By-the-way, lost the users profile completely. There was no windows.old folder of any kind. Not even in the root. The semi-clean install to the existing partition installed Windows 11 24H2 to 11% and came up with Windows installation failed. Profile gone after that when looking at the correct partition when booting out-of-band. It was not that I could not see the profile or have a permissions issue, the C:\Users\username folder is completely gone.

End result - fresh install is next.

...Unable to reload OS on MINIS FORUM. Required the NVMe to relocate to install Windows 11 on other hardware and bring it back.

Also, I forgot to mention I did switch the public to private, changed all firewall settings and enabled file and print services several times.

Intelligent-Cable 10 Reputation points

2025-09-14T22:04:26.03+00:00

Should work but keen to hear that it resolves this issue, have a read on sysprep for building your images in future, be aware of the rearm limit ;)

Ron DeLorenzo 0 Reputation points

2025-11-25T19:03:27.3933333+00:00

we recently purchased several machines from a secondary vendor and have started deployment with a pair of machines. I noticed some issues with the C$ share, when trying to quickly transfer a few files from one machine to the next. Just brushed it off and forgot about it. Now that I'm getting to do additional machines, and have a pair of them on my desk, I've discovered that this vendor apparently did not sysprep the machines as both machines have the same SID (confirmed with PSGetSID64). This is something that I have always been a proponent of (and always telling students about). Going forward, I will be wiping all systems and deploying via our normal process using SCCM/SCEM. Annoyed that I can't trust vendors to do things the right way...

WayneK 0 Reputation points

2025-11-25T19:49:20.8466667+00:00

Ron - I had the same issues with identical SKU machines imaged with the same "golden master" which duplicated SIDs. I used SIDCHGL from https://www.stratesave.com/html/sidchg.html on one machine. SIDCHG was relatively non-destructive to the user accounts with the exception that three apps needed re-activation due to their reliance on SID.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
LOUIS LOPEZ 25 Reputation points

2025-09-13T20:18:48.7+00:00

Name and password is correct

Different usernames with matching passwords did not work

Using alternate credentials did not work

Removing stored credentials did not work

Changing the firewall to default and allow in and out SMB

SMB 1.0 Server and client are on both machines and matching

I tried EnableLinkedConnections on or off didn't work

I tried LmCompatibilityLevel 1 or 3 matching

I tried the RequireSecuritySignature Workstation and Server registry on or off at both machines

I tried AllowInsecureGuestAuth on or off

One machine can map shared to the planet earth (all other machines)

The other machine can map shared to the planet earth (all other machines)

They can't map to each other.

I removed the KB5065426 from Windows updates

It came back

I removed the KB5065426 from Installed updates

It was gone but the shares still did not work

I ran Powershell to attempt to remove it and expecting it to already not be eligible for removal I got another error indicating it is still there.

wusa /uninstall /kb:5065426

The error message showed Security Update for Microsoft Windows (KB5065426) is required by your computer and cannot be uninstalled.

This led me to find Sysinternals PsGetsid.exe and that showed me the SIDs match!

I joined the computer to a domain just for fun and SID stayed, I unjoined the computer from the domain because it wasn't supposed to be in a domain for this peer-to-peer scenario.

Need a simple, no-cost, trust-worthy, free Windows 11 SID changer. Why? Because it worked until a Microsoft Windows Update was installed and was working without a SID changer. But going forward, likely needs a new SID. The computers were MINISFORUM Chinese computers.
Was this answer helpful?

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Nicholas Page 256 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.
Was this answer helpful?
Thomas Bunch 5 Reputation points

2025-09-26T15:38:38.99+00:00

I have tried sidchg and it does work

JTB3 0 Reputation points

2025-10-24T23:48:11.4166667+00:00

Unfortunately, in my case, running the popular SIDCHG utility on my cloned Windows 11 machine was anything but painless. 1st, I had to re-sign into and re-sync all of my Chromium and Firefox browsers, communications apps, Office, OneDrive, re-sync Signal desktop, etc. Then, the horrible Windows File Explorer lag issue happened, causing 20-second delays in navigating and renaming files using Window's built-in File Explorer - making the machine frustratingly unusable. Hours of wasted work. Reverting back to an earlier image - because of the Explorer lag. Make sure you have a good OS image backup before trying SIDCHG. Your mileage may vary...

JTB3 0 Reputation points

2025-10-25T00:19:32.32+00:00

Unfortunately, in my case, running the popular SIDCHG utility on my cloned Windows 11 machine was anything but painless. 1st, I had to re-sign into and re-sync all of my Chromium and Firefox browsers, communications apps, Office, OneDrive, re-sync Signal desktop, etc. Then, the horrible Windows File Explorer lag issue happened, causing 20-second delays in navigating and renaming files using Window's built-in File Explorer - making the machine frustratingly unusable. Hours of wasted work. Reverting back to an earlier image - because of the Explorer lag. Make sure you have a good OS image backup before trying SIDCHG. Your mileage may vary...

Clif 5 Reputation points

2025-10-25T13:24:19.1866667+00:00

the issue is resolved. see this article "Major Windows 11 Update Bugs Fixed With a New Release" https://www.msn.com/en-us/news/other/major-windows-11-update-bugs-fixed-with-a-new-release/ar-AA1ORmtZ?ocid=msedgntp&pc=U531&cvid=68fa378b694346c796f34df3d93cc2a0&ei=29

i used windows update and the new patch downloaded if you tick get latest updates.

all is back to normal for me.

Lan Manager 0 Reputation points

2025-10-29T22:03:38.5466667+00:00

This scenario happened to me and I had to perform a System Restore Point that was created before the date that KB5065426 was installed. This learn.microsoft.com article actually pointed me in the right direction. After the restoring the system restore point the File and Print sharing worked again. I verified that the PC sharing files and printers did indeed have the same Security Identifier. For the interim I disabled Windows Update on PC;s affected using gpedit.msc (Group Policy editor) and disable Windows Update in hopes Mr. Softy would provide a permanent fix. (They didn't).

To disable Windows updates using gpedit.msc on Windows 11 Pro, open the Local Group Policy Editor, navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage end user experience, double-click "Configure Automatic Updates," set it to Disabled, and click Apply then OK.

So now.. I started to scratch my head wondering how in the %&*# did my new Dell PC's end up with identical Sid's to begin with? Turns Out that Dell and HP only have third party resellers on Amazon. My hypothesis is that some of these resellers are purchasing PC's from HP and Dell without an operating system and then they acquire activation keys at low prices to increase profitability. The cloning process obviously does not use Sysprep, and that is the reason for the duplicate Sids. Just my opinion.

I'll end up using SYSCHG utility from Stratestave. Maybe KB506426 was meant to break file and print sharing on those Duplicate SID PC's? LOL

Susan E Bradley, CPA/CITP/CFF, GSEC 50 Reputation points

2025-10-29T22:09:21.4933333+00:00

The patch wasn't intended to break file share - rather to block duplicate SIDS. If you would rather use a group policy workaround, send me an email at sb-at-askwoody.com. Please provide feedback in the Windows feedback forum.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

KB5065426 update stops file and print sharing from working

27 answers

Your answer