Workgroup (no Active Directory) Client: Windows 11 24H2 (build …) Server (peer PC hosting the share): Windows 11 24H2 (build …) Recent updates installed: KB5063878, KB505440 Since updating to 24H2, our clients can’t access \SERVER\Share anymore. Windows always prompts for credentials and rejects them (“The user name or password is incorrect”). Before the update, access worked. Disabled SMB signing (Client/Server “digitally sign communications – always/if agrees”) Set “Network access: sharing and security model for local accounts” = Classic (ForceGuest=0) Enabled LocalAccountTokenFilterPolicy=1 LmCompatibilityLevel=3 (NTLMv2) Tested with IP and with SERVERNAME, cleared credential cache, firewall SMB-In allowed Services running: LanmanServer, Workstation, Function Discovery Provider Host/Resource Publication Test-NetConnection SERVER -Port 445 → name resolution failed; with IP works net use \<IP>\Share /user:.\shareuser * Event Viewer (server) Event ID 4625 at the same time → Status/SubStatus: 0x… Clean 24H2 images (client+server) in workgroup. Create local user “shareuser” on server, share C:\Data\Share and grant Share+NTFS. From client, map \SERVER\Share (or \<IP>\Share) with SERVER\shareuser credentials. Observe repeated credential prompts/rejection. Successful authentication with local user in Workgroup. Credentials rejected after 24H2. Looks like SMB/NTLM hardening or guest/classic model regression. Please advise or confirm if this is a known issue. Happy to provide Feedback Hub logs and ETW traces. A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation Tech Support • 0 Reputation points 2025-09-12T02:18:24.4866667+00:00 Same issue - we just lost access to some USB connected shared printers. At first I thought it was our endpoint protection - disabled that Then windows firewall - disabled that Credentials rejected throughout the process. Installed smb 1.0 as a workaround - also failed i found this thread... the adventure continues https://learn.microsoft.com/en-us/answers/questions/5551014/kb5065426-update-stops-file-and-print-sharing-from 0 votes Same issue - we just lost access to some USB connected shared printers. At first I thought it was our endpoint protection - disabled that Then windows firewall - disabled that Credentials rejected throughout the process. Installed smb 1.0 as a workaround - also failed i found this thread... the adventure continues https://learn.microsoft.com/en-us/answers/questions/5551014/kb5065426-update-stops-file-and-print-sharing-from Dmitriy Khazak • 0 Reputation points 2025-09-12T19:45:15.42+00:00 Similar issue. Host Win11 23H2 (10.0.22631.0) updated itself yesterday to 24H2 (10.0.26100.0) without asking permission. Upon restart host's shared folder, mapped in a VM (also W11, but still 23H2 so far), is no longer accessible from the guest. Guest refuses to ping the host by name (times out). Both guest and host have no problem pinging other computers on the network. Guest has mapped drives to shares from other network locations - no issues. That same shared folder in question was mapped from another network machine long time ago, and is stilll accessible from there [- after update], so it's not a problem with sharing /credentials /permissions.. But what else? One more detail: guest VM has autoconfigured IP address (172.19.42.75) and DNS Suffix "mshome.net". That may have smth to do with the issue, but everything worked fine before the damn update to 24H2! P.S. Clicking the "Connection information" icon in the updated RDP bar .. kills the connection to VM! 0 votes Host Win11 23H2 (10.0.22631.0) updated itself yesterday to 24H2 (10.0.26100.0) without asking permission. Upon restart host's shared folder, mapped in a VM (also W11, but still 23H2 so far), is no longer accessible from the guest. Guest refuses to ping the host by name (times out). Both guest and host have no problem pinging other computers on the network. Guest has mapped drives to shares from other network locations - no issues. That same shared folder in question was mapped from another network machine long time ago, and is stilll accessible from there [- after update], so it's not a problem with sharing /credentials /permissions.. But what else? One more detail: guest VM has autoconfigured IP address (172.19.42.75) and DNS Suffix "mshome.net". That may have smth to do with the issue, but everything worked fine before the damn update to 24H2! P.S. Clicking the "Connection information" icon in the updated RDP bar .. kills the connection to VM! M Olt • 5 Reputation points 2025-09-15T13:00:13.9933333+00:00 Same issue after recent update. Not resolved yet. Waiting on work around or fix. 0 votes Same issue after recent update. Not resolved yet. Waiting on work around or fix. M Olt • 5 Reputation points 2025-09-15T13:13:22.9633333+00:00 According to some research found on Spiceworks , It appears as if the issue is caused by Windows 11 update KB5065426, which enforces stricter SMB authentication. Even proper local accounts may be rejected unless used in the correct format. I'll try removing the update later this afternoon and keep everyone informed. 0 votes According to some research found on Spiceworks , It appears as if the issue is caused by Windows 11 update KB5065426, which enforces stricter SMB authentication. Even proper local accounts may be rejected unless used in the correct format.

I'll try removing the update later this afternoon and keep everyone informed. 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. 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. M Olt • 5 Reputation points 2025-09-15T22:26:53.94+00:00 So removing the windows update worked fine for the two win 11 systems but after clearing the windows credentials a win 10 system still refused to get into the share. It challenges me every time. Still waiting for resolve from MS. 0 votes So removing the windows update worked fine for the two win 11 systems but after clearing the windows credentials a win 10 system still refused to get into the share. It challenges me every time. Still waiting for resolve from MS. Full Electronica 2 • 0 Reputation points 2025-09-16T13:47:28.7133333+00:00 Hola, estoy con el mismo tema, despues de la actualizacion no puedo acceder a carpetas compartidas que tengo en mi red, tampoco puedo acceder a la impresora compartida.. 0 votes Hola, estoy con el mismo tema, despues de la actualizacion no puedo acceder a carpetas compartidas que tengo en mi red, tampoco puedo acceder a la impresora compartida.. Ing. Alberto Aiello • 5 Reputation points 2025-09-16T21:56:49.46+00:00 Stesso identico problema! Cartella condivisa su NAS, impossibile accedere! sto impazzendo 1 vote Stesso identico problema! Cartella condivisa su NAS, impossibile accedere! sto impazzendo Aeris_Valetine • 40 Reputation points 2025-09-19T00:52:02.2666667+00:00 Me too, i have this problem now: this conextion work fine some weeks ago 0 votes Me too, i have this problem now: this conextion work fine some weeks ago Thagulla, Sai Kumar • 0 Reputation points 2026-01-09T16:00:13.9766667+00:00 Iam uble to productions paths 0 votes Iam uble to productions paths Steve Franks • 21 Reputation points 2026-01-23T11:33:49.2933333+00:00 I implemented the suggested change, but I still cannot link my Fedora PC to a Windows 11 share. My network is set to allow all valid users access to shares; this has never worked. MS suggested creating a local account, which I did specifically for networking, but that doesn't work. It did briefly work whilst I was still on Windows 10. There is other evidence that networking is faulty in Windows 11. Occasionally it won't let me update files on OneDrive, because it thinks that another user has them open. This BS, because I am the only user of my PCs. I cannot credit that in the 21st century one is still forced to copy data between computers by means of physical disks. 0 votes I implemented the suggested change, but I still cannot link my Fedora PC to a Windows 11 share. My network is set to allow all valid users access to shares; this has never worked. MS suggested creating a local account, which I did specifically for networking, but that doesn't work. It did briefly work whilst I was still on Windows 10. There is other evidence that networking is faulty in Windows 11. Occasionally it won't let me update files on OneDrive, because it thinks that another user has them open. This BS, because I am the only user of my PCs. I cannot credit that in the 21st century one is still forced to copy data between computers by means of physical disks. Carlos V. Gonzalez • 15 Reputation points 2025-10-06T13:32:12.4566667+00:00 Very conveniently Microsoft changed how Windows Samba client behaves connecting to Samba Servers in the last update for Windows 10 and on Windows 11 I have a Debian Samba Server share that Windows 10 stop working to, after last windows 10 update, my Android device however had no problems connecting to server, the culprit seems to be: EnableSecuritySignature $true that is now default on Windows 10 Samba client, to change it, open power shell with administrator priviedges and: Set-SmbClientConfiguration -EnableSecuritySignature $false that should be enough. Restart Windows... 4 comments Show comments for this answer Timothy Edgin • 5 Reputation points 2025-10-16T21:39:23.3866667+00:00 This was the final straw for me; I can no longer trust Microsoft as a partner. This a an overt attempt to force the remaining resistors to the cloud. What good is a network operating system if it cannot network to other similar machines? This is is a good example of why we need strong regulations and enforcement of monopoly laws. This literally destroyed thousands of small businesses ability to do on-rem work without spending significant money or -you guessed it-moving to the Cloud scam. 0 votes Edward • 0 Reputation points 2025-10-24T01:49:28.7833333+00:00 hey thank you so much I was finally able to login to my server through the network folder. this worked on windows 11 0 votes Andrey Fedosov • 0 Reputation points 2025-12-24T13:19:39.7066667+00:00 Small update - most likely the parameter in question was: Set-SmbClientConfiguration -RequireSecuritySignature $false Or they added it later. But now it is required to disable at least the second one 0 votes Miguel Eca Alvarez • 0 Reputation points 2025-12-27T14:49:10.6933333+00:00 de gran ayuda 0 votes Sign in to comment Add comment Very conveniently Microsoft changed how Windows Samba client behaves connecting to Samba Servers in the last update for Windows 10 and on Windows 11 I have a Debian Samba Server share that Windows 10 stop working to, after last windows 10 update, my Android device however had no problems connecting to server, the culprit seems to be: EnableSecuritySignature $true that is now default on Windows 10 Samba client, to change it, open power shell with administrator priviedges and: Set-SmbClientConfiguration -EnableSecuritySignature $false that should be enough. Restart Windows... Timothy Edgin • 5 Reputation points 2025-10-16T21:39:23.3866667+00:00 This was the final straw for me; I can no longer trust Microsoft as a partner. This a an overt attempt to force the remaining resistors to the cloud. What good is a network operating system if it cannot network to other similar machines? This is is a good example of why we need strong regulations and enforcement of monopoly laws. This literally destroyed thousands of small businesses ability to do on-rem work without spending significant money or -you guessed it-moving to the Cloud scam. 0 votes This was the final straw for me; I can no longer trust Microsoft as a partner. This a an overt attempt to force the remaining resistors to the cloud. What good is a network operating system if it cannot network to other similar machines? This is is a good example of why we need strong regulations and enforcement of monopoly laws. This literally destroyed thousands of small businesses ability to do on-rem work without spending significant money or -you guessed it-moving to the Cloud scam. Edward • 0 Reputation points 2025-10-24T01:49:28.7833333+00:00 hey thank you so much I was finally able to login to my server through the network folder. this worked on windows 11 0 votes hey thank you so much I was finally able to login to my server through the network folder. this worked on windows 11 Andrey Fedosov • 0 Reputation points 2025-12-24T13:19:39.7066667+00:00 Small update - most likely the parameter in question was: Set-SmbClientConfiguration -RequireSecuritySignature $false Or they added it later. But now it is required to disable at least the second one 0 votes Small update - most likely the parameter in question was: Set-SmbClientConfiguration -RequireSecuritySignature $false Or they added it later. But now it is required to disable at least the second one Miguel Eca Alvarez • 0 Reputation points 2025-12-27T14:49:10.6933333+00:00 de gran ayuda 0 votes 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 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