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.
I forgot to mention in my post that I tried all the suggestions in previous posts. If you look in the picture below my share "Archer" is not listed.
But now I just tried to access typing the IP on the address bar and bam... the folder in my share appeared.
![](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(204.8, 96%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3END%3C/text%3E%3C/svg%3E)
Simon, I realise you are having issues but I was answering the comment made by crcastilho about the insider release.
If Windows 7 is still having the same problem accessing your NAS then it is not a Windows 10 issue. Have you checked the Feedback Hub link to upvote the problem, or as a non insider can you even access the Feedback Hub link.
Have you checked the Feedback Hub to see if others are reporting the same issues. You can always link to this thread in the Feedback Hub.
No it doesn't... on my part I can see it on he network, but my credentials declined. I have deleted the credentials both within windows and the registry. Won't connect... log in via a browser, not a problem.
On the new PC I built to replace my Nas, it doesn't show up. I even dragged an old Win7 pc out of the cupboard, same results... That's where I'm thinking it's maybe a defender issue rather than a windows issue. Either way both Microsoft. Cannot believe after months we still don't even get recognition from MS that it's a problem!
Interesting, I have insider preview Version 20H2 Build 19042.421 running on a virtual machine and if I map a drive to the same share as my host it prompts for a password and connects straight away. The host (on the same share) takes two goes to accept the password.
If the NAS share is connected at boot then it will not connect in File Explorer until I have removed it and remapped it.
I'm using the insider on the Beta channel.
I see the Feedback Hub post and believe it is only available to Insiders, but a non insider would have to confirm that. The feedback needs to go into the public release Feedback hub also.
