This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Any help is appreciated
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 51%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Win10 20H2 fixes the issue.
Previously when 2004 broke smb1, I rolled back.
There was no registry change or any other modification made to the system. After Win10 20H2 upgrade was installed via Windows Updates; SMB1 worked as it did before the upgrade.
Thank you Microsoft.
The community needs to wake-up and accept reality. The overwhelming majority of W10 users are unaffected by, and unaware of, the issue. Microsoft have not acknowledged any workaround and have no incentive to change its' posture - SMB1 NAS will never be accessible under W10.
Why accept SMB 1 NAS would be out of service because a W10 update ! Security LAN is a personal job, there's many ways to do so, i don't need Microsoft for that.
But, finally, i think the issue is NOT SMB 1 ! I have 3 computers on my LAN, one is a Microsoft surface recently updated from 1909 to 20H2... My SMB 1 NAS was not connected here before, and i noticed that i still can access the NAS through network sharing after update without problem.
Then i disconnected the NAS (previously Z:) on my main computer, Win1909. After reboot, i update to Win 20H2 and i notice that registry has changed for network SMB 1. I think the issue is there and the work around is to disconnect the device before updating (to 2004 or 20H2).
After some stop & start, my SMB 1 NAS can be accessed through network sharing.
The internet is littered with proposed solutions to this problem, none of which have been endorsed by Microsoft, and all of which are no more than uninformed amateur workarounds with questionable applicability.
The community needs to wake-up and accept reality. The overwhelming majority of W10 users are unaffected by, and unaware of, the issue. Microsoft have not acknowledged any workaround and have no incentive to change its' posture - SMB1 NAS will never be accessible under W10.
Those committed to W10 have no alternative than to either replace their gaged NAS with compliant units or adopt online storage. Given that the internet is a cauldron of criminality, half truths and corporate greed, only a fool would commit their data to corporate online storage irrespective of provider claims of security and integrity.
So long as LAN and WAN share a common addressing scheme, the only secure way of ex-PC data storage using SMB1 NAS is to configure a LAN controlled by a non-W10 PC divorced from the internet.
if you had read a few posts before, you would have seen that this tip has been given already. I don't really understand why people still have the problem.
In a desperate attempt to stop notifications on this thread, perhaps this will work
