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.
it's not a problem ... I'm an administrator. the problem is in the win 10 update 2004 error
The only solution that works for me with the win 10 - 2004 version is to create a bat file and start it when logging in:
timeout /t 30
net use w: "\network name\folder" /persistent:no
be sure to put /persistent:no
this solution works great with NAS deluxe servers
timeout you can reduce!!!
This worked - I created the bat file and put it in the startup folder. It mapped shares on an old Windows 2003 server. Worked great!
I wonder if Microsoft plans to fix this, or if it's this way by design?
Mate,
You're not gonna believe it. I added to the script with FQDN path the parameter " /persistent:no" without "timeout" and it seems to be finally working! Your advice is much more helpful than whole MS team.
Did restart few times and network drive is mapping with no issues. I'll let you know if any problems occurs.
Thanks !
Discovered a couple things today regarding this:
If the domain user account is just a member of the local users group, you won't be able to browse to the server by it's short-name, but FQDN works fine.
Make the domain user account a member of the local admin group and everything works as expected. (obviously not how you want to leave it)
I ended up disconnecting the previous drive mapping via a script and remapping the drive with the FQDN in a login script. This then allowed me to access the share, and if the drive is mapped using the FQDN, you are then able to browse to the share via the short-name.
So, no clear answer, but a definite work-around.
