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.
We Run Windows 10 workstations with Linux Samba as a file server.
From time to time, we lose the ability to connect to mapped drives.
We find that the command 'net use x: /delete' will delete the mapped drive x:
We can then re-map the drive using windows 10 mapping and we're good to go until it happens again.
Note that the 'net use' command is reported by MS as deprecated for Windows 10 and there is no mention of a replacement or work-a-round.
Best of luck.
Why wouldn't you just restart the workstation service, instead of remapping? some of my users have 6 mapped drives that would take forever. Unless you are using a script to remap.
We Run Windows 10 workstations with Linux Samba as a file server.
From time to time, we lose the ability to connect to mapped drives.
We find that the command 'net use x: /delete' will delete the mapped drive x:
We can then re-map the drive using windows 10 mapping and we're good to go until it happens again.
Note that the 'net use' command is reported by MS as deprecated for Windows 10 and there is no mention of a replacement or work-a-round.
Best of luck.
Restarting 'Workstation' service is fixing this for those on the fly fixes where rebooting doesn't.. Great.
This sucks though.
On one PC the "ProviderFlags" worked great but I only set that on one of the drives, maybe I need to set that for all the network drives for this other PC that is doing this...
Although still a problem for many people, I have found that restarting the service "Workstation" and associated dependencies clears the issue up until the next reboot. Not a permanent fix but it certainly helps with the loss productivity and headaches until Microsoft provides a permanent solution.
This works every time for me.
I'd be curious for a chime in from users how many this quickly serves as a workaround.
Thanks, Steve! This worked for me. A few months back, my NAS stopped appearing under my network locations. I was able to add it as a pinned location, but that stopped working today. None of the usual fixes worked, but starting/restarting the "Workstation" service did.
Hope the problem gets resolved soon, but thanks for the workaround!
