SMB sharing not working after windows 10 update Build 2004 update

Anonymous
2020-06-20T02:30:38+00:00

Any help is  appreciated

Windows for home | Windows 10 | Internet and connectivity

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.

0 comments
Answer accepted by question author
Monkey57 3,535 Reputation points
2020-11-03T02:21:51+00:00

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.

Was this answer helpful?

20+ people found this answer helpful.
0 comments

246 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-10-08T19:30:59+00:00

    We're also using Synology.  Glad that it works for you; however, this is untenable for us as our security policy requires us not to use SMB1.  Likewise, solutions calling for AllowInsecureGuestAuth are also not possible.   Microsoft really needs to fix whatever they did in v2004.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-10-08T20:08:20+00:00

    Well, by default our minimum and maximum were both set for SMB1. I guess it had been set like that since 2014 since the NAS was implemented. I would have thought that maybe Synology would have sent something out or fixed that setting with a DSM update along the way but I guess not. I never even gave that a thought until I was fishing around in the settings and ran across that configuration page. It all kind of makes sense now, looking back. The options for these settings are shown below.

    ======================

    I just changed the maximum to SMB3. I did not test changing both minimum and maximum to SMB2 but I might think that would not be an issue since all our machines are running Windows 10 Pro. Something tells me that taking SMB1 completely out of the picture would be the best thing to do anyway but I was just desperate to get rid of the error we were seeing constantly on the workstations on the LAN. We have a fonts folder with thousands of fonts stored for our graphic design team on a folder on the NAS and I can definitely tell you that changing that maximum setting to SMB3 from SMB1 definitely fixed that teams' access issues to that shared folder on the NAS. It's lightning fast now according to them and there is no lag or issues at all. They were experiencing a lot of weird things like slow file explorer access to those folder and even locking up their machines at times. They say that is all gone now.

    I will set the minimum setting on the NAS to SMB2 at close of business today and see if users have any issue with accessing the shares tomorrow.

    I'll report back.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-10-08T21:08:12+00:00

    File sharing can only work when you enable sharing settings correctly. Besides, you also have to share data in the right way. For that, follow these steps:

    Step 1. Click "Start" > "Control Panel" > "Network and Sharing Center" > "Advanced sharing settings".

    *Under Private (current profile), check "Turn on network discovery" and "Turn on file and printer sharing". Click "Save changes" to confirm.

                     To make sure the problem can be solved, allow File and Printer Sharing in Windows firewall settings.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2020-10-08T21:22:36+00:00

    Khan,

    We're WAY past this as being the issue. That was verified a LONG time ago without any resolution.

    Was this answer helpful?

    0 comments