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.
This issue has still not been resolved! We recently updated a few computers and this problem started occurring. We got an obsolete financial software running in our company, which cannot be run/installed on newer server version, therefore we cannot upgrade it and we are currently stuck with windows server 2003.
Please fix this issue, before it escalates.
I have the same problem. Waiting for a fix or regedit to resolve.
Thanks neilpzz. I'm accessing a ReadyNAS which uses SMB1 via guest connections - no authentication needed. As a work around I enabled the NFS client and set up mount points on the NAS, which worked fine. After reading your post I disabled NFS on the NAS and used SMB/CIFS again to to set up mapped drives to the NAS, and lo and behold the drive mapping works at this time! I have no explanation as to this behavior.
Update:
The next day I lost access again and had to re-enable NFS support on the NAS and NFS client feature in Windows and mount via NFS to regain access. Still no idea why...
![](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)
There is something a miss with SMB in 2004. I use File History to my NAS and also have two mapped drives to shares on the NAS. My password would not be accepted
Over a few days I realised that if I Disconnect the mapped drives in File Explorer and then select File History in Control Panel to input the password the drives can be mapped again without a problem in File Explorer. I currently leave the drives unmapped until I need them and they always work.
I have ensured SMB 1.0/CIFS File Sharing Support is enabled. (I did disable then re-enable again initially)
We will have to wait for Microsoft to issue a patch but if you cannot get it to work then use the Feedback Hub to report the problem.
