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.
![](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.
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.
With my insider if I make sure the mapped drive isn't mapped during boot and then go to map the drive using \dlink\share then it prompts for a password and maps immediately, even though the credentials are already in Credentials Manager and it should map without prompting.
There's obviously something wrong that we cannot fix with a workaround but I don't know why Microsoft haven't addressed it. It seemed to start with the removal of SMB1.
I have a post in the Feedback Hub that I've linked to this thread but as my account is in use for the Insider account I think it only appears to insiders. The database for feedback is split into insider and non insider.
I have a LAN with 3 Netgear NAS that are affected (2 Duo running OS 4.1.16, 1 Duo v2 running OS 5.3.13), 1 Netgear NAS that is not affected (RN102 running OS 6.10.3) and 1 unaffected WD MyBookLive.
Using Netgears RAIDar app, the affected 3 report Computer type as "Windows NT 4.9 Server", the unaffected 1 reports Computer type as "Windows Server".
Has MS decided to ignore NT servers ?
My workaround is to use Windows 7.
