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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-09-15T14:23:09+00:00

    If sombody still interested I use a workaround that seems to work after reboot

    Remove the connection to the network drive

    put a simple batch into automatic startup

    net use /persistent:no z: \192.168.0.120\store

    obiuvsly z: \192.168.0.120\store have to be personalized to your needs

    persistent:no is the key to the success because avoid auto mount at reboot

    because of it seems to hit only smb1 devices I suppose it not will be solved, so this workaround could become a good solution

    excuse me for my english

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-08-28T18:09:42+00:00

    Those of you who still have this problem, try the following:

    in the Registration Key [HKEY_CURRENT_USER\Network\*SMBv1 Drive Letter*], create the Value REG_DWORD "ProviderFlags" decimal 1 (0x00000001)

    This should make it possible to communicate properly with the network drive at startup and shutdown. Do the process for all those units you have with smbv1 connection

    This worked for me too.  Thanks Serafin

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2020-08-19T11:00:32+00:00

    Well it is for me. On version 2004, v1 works fine. If I disbale v1, then and enabe SMB Direct (v3), then SMB browsing does not work. I was asking this question to find out if using this setting

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters] "AllowInsecureGuestAuth"=dword:1

    fixes the v3 problem.

    And I have no idea why you brought up "CSIRO, ADF, nor government", seems irrelevant to me.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-08-19T08:53:12+00:00

    This worked for me too.

    Thanks.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments