https://www.askwoody.com/forums/topic/microsoft-snuck-in-another-out-of-band/#post-2811053
Windows 10 now has a preview update that should fix this.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
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.
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!
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.
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.
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".
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.
Microsoft deberia revisar esto, no se puede permitir tal error.
Yeeay man the problem is the same SID.
THANKYOU
I have the same problema here. With a lot of PCs
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.
Removing it worked for me! Many thanks!
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.
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.
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.
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.
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.
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.
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!
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.
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
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.
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.
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
The exact same issue occurs on Windows 10 with update KB5065429, and the above "Answer" doesn't work on that either.
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.
I already have port 445 open and it doesn't help.
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?
Update has reinstalled and now even using that command doesn't uninstall update.
try to run:
'sfc /scannow' then 'dism /online /cleanup-image /restorehealth'
me too, i have de same problem now
DFS Replication for me also broke after installing this update
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.
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.
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.
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.
uninstalling this KB fixes event id event id 6167 when mapping a drive...
When this updated on windows 11?
I'm seeing more and more computers experiencing this problem. What's the solution?
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.
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.
https://www.askwoody.com/forums/topic/ms-defcon-4-finally-24h2/#post-2814835 See if the September updates help
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).
https://www.askwoody.com/forums/topic/microsoft-snuck-in-another-out-of-band/#post-2811053
Windows 10 now has a preview update that should fix this.
Does that address the question of duplicate machine SID's? The comments to this post are all over the map. It sounds like some users don't use SMBv1.
I am honestly not sure. All it talks about is SMBv1.
When this update on windows 11?
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.
I have tried installing KB5066198 (on Windows 10) and it does NOT fix my problem of not being able to access my Buffalo Linkstation HD-H250LAN NAS drive (SMB1 only), so I have had to uninstall KB5065429 again.
Installing KB5066198 did NOT fix the problem with accessing my Buffalo Linkstation HD-H250LAN (SMB1 only) on Windows 10 so I have had to uninstall KB5065429 again (the Win10 version of KB5065426)
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.
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?
On the machines impacted what is the SID?
From a command line type in wmic useraccount get name,sid
@Susan Bradley Does it matter? We are using domain account.
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.
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
still yesterday shortly after my comment above:
as I said: after being successful in my "home net" I moved the computer back to the "company net" awaiting same success over there. But -- no, not running! The problem is still the same. Only difference now is the fritz.box in the middle. "home version" 7590 AX and "company version" 7490. Both absolutely up to date and reseted.
As I said "home" all okay "company" not.
I will continue checking. Next step will be to uninstall KB5065426 on both computers in "company net" and ...
Keep you updated about my frustration level!
Greetings
Problem solved:
Has anyone opened a case with Microsoft support?
SIDCHG works fine for me. Fortunately it provides offical trail license key.
SIDCHG fonctionne impeccablement.