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(70.4, 63%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDD%3C/text%3E%3C/svg%3E)
After having upgraded to Windows 10 20H2, I continuously experience a problem of not restoring Samba shares to LenovoEZ share NAS. The message box pops up with "Location is not avaialable", "Z:\ is not accessible", the specified network name is no longer available. Some icons showing connection turn green momentarily, and then show up with red cross as disconnected. This happens after every update, which, even though I tried to disable it, is forced by Windows anyway. The SMB1 and SMB2 protocols are enabled. I am using Advanced IP Scanner to see the NAS, in this tool NAS is found and one can access the drives. In the past, I found that it is possible to unshare the drives, and then share them again; this restores connection. But it is VERY inconvenient. Why the drives which use the same credentials as before are not accessible after Windows push updates? What can be done to permanently disable Windows push updates?
Hi Dmitrii
Since your question is not related to the Open Specifications documents, I've removed the tag openspecs-windows-filesharing
![](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(307.2, 32%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Yeah, I've had this issue since the Windows update mid-January.
I've heavily researched this and tried a number of registry hacks, checked NAS share user profile and password, entered NAS user details into Windows Credential Manager, tried putting the NAS IP into the hosts file, and deleting and recreating the network drive on that PC - to no success.
My Nvidia media streamer can access the NAS shares fine, I can ping the NAS (both by name and IP), and can log into the NAS as admin using IP address, so something has definitely changed with the Windows 20H2 update.
![](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(278.4, 92%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EE%3C/text%3E%3C/svg%3E)
I have the same issue.
The only workaround I found is to connect with the IP address. Then connection are restored at start-up.