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)
Has MS decided to ignore NT servers ?
I don't know.
Do you know if all the devices use SMB 2 or do some use SMB 1. Try turning off SMB 1 support in Windows 10, Programs and Features > Turn Windows features on or off to see if it changes or stay the same across all your NAS devices.
Affected NAS do not have an SMB option. They have CIFS which I recall reading somewhere recently that this is a predecessor of SMB. Netgear unaffected RN102 NAS has SMB selected true.
Unaffected MyBookLive SMB status unknown.
Windows features SMB 1.0/CIFS File sharing support options after July update are :-
SMB 1.0/CIFS Automatic Removal - true
SMB 1.0/CIFS Client - true
SMB 1.0/CIFS Server - false
Setting all three true does not restore access to affected NAS.
Setting all three false results in 3 affected and MyBookPro disappearing from file explorer leaving only RN102 visible and accessible.
Restoring options per update restores 5 NAS visible, 2 available, 3 visible but not accessible.
I haven't changed Windows features SMB Direct option which is not set.
I upgraded to 2004 on 1 Aug. After seeing that 2 out of 3 NAS stores were not connecting, went looking for a reason. Found this page. After reading 10 pages of workarounds for a basic MS cock-up, decided that my best approach is to just roll back to 1909,
I have rolled-back, and everything works again.
I also posted to the feedback hub with critique, and pointed whoever reads it to this page.
Thankyou. I cannot believe that this problem is being totally ignored. It has not only cost me thousands, but I haven't been in bed till 6am a couple of nights in a row. I have over 4tb of data that I had to convert from EXT4 to NTFS, now currently sorting it into where it should be...I'm tired and grumpy that MS decommissioned my Nas that was working beautifully before this update... heads need to roll due to incompetence. Seriously, if anyone is interested, I would love to create a class action for this ****!
