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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-07-21T22:09:09+00:00

    Enabling NFS brought my system to a virtual stand still.

    I don't understand how I am able to connect to my share via Run > //xxx.xxx.xxx.xxx

    Yet Explorer is unable to find it on it's own.

    If I forcibly map the drive in PS, the connection is sometimes available, sometimes not.

    Just why Mircosoft? Why fix something that isn't broke??

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-07-20T18:18:16+00:00

    Hi Guys!

    It's working if you switch nfs on the nas, and use the FQDN name. When you switch the nfs on the NAS, you can add the FQDN name to the nfs.

    That's right, not working with the IP, but working with the FQDN name.

    Best regards,

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-07-20T17:12:09+00:00

    Exactly, like old Linux file servers.

    Migration isn't an easy/fast solution at this moment.

    Hey Microsoft, anybody can help us there?

    I've tried to point out before we are users here and not Microsoft employees.

    Use the Feedback Hub for Microsoft. You may well find others users have already posted there. You can include a link to this post if you wish.

    I've created a thread on Feedback Hub pointing this post.

    https://aka.ms/AA916wu

    So, everybody here can comment there to rise the visibility of the problem by Microsoft.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-07-20T15:32:53+00:00

    Hi all,

    I've made a workaround that in my case resolve temporary network share to w2003 srv

    1. create a simply batch file using notepad and use the command net use to map network share; for example use the command

    net use Z: \MyServerIp\MyFolderShared /user:MYDOMAIN\MyUsername MyPassword /persistent:no

    1. save as .BAT in desktop for example
    2. go to command line and use the command shell:script and aappairs a windows for automatic startup and copy te batch file in here

    When I power on the pc, the script permits to mapped network share and with the prameter persistent:no at the end of the command I impose that when I power off the pc, the network share will be closed.

    Every time I start the pc I create again the network share with the letter imposed in the command syntax (in my example letter K).

    So waiting for the patch ... meantime I blocket windows update service via services.msc

    Hope this give help

    Bye

    Francesco

    EDIT: remember to delete network share before run script. In command line wirte net use delete MYLETTERMAPPED: /delete  (for example net use delete K: /delete)

    Was this answer helpful?

    0 comments