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-11-06T06:40:15+00:00

    Hi Guy,

    I also find out this issue. But I got temp solution as you must do hardcode in credential manager.

    last time at username field, you all put "domain\user"

    now you change it to "user @ domain.local"

    It will be worked.

    hope this can help you all.

    Regards

    Waichun

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-11-05T11:06:39+00:00

    My fix for my Linux server shares was to follow this guide

    https://devanswers.co/discover-ubuntu-machines-samba-shares-windows-10-network/

    and install windows discovery for my Linux server after my samba shares suddenly become inaccessible 3 days ago for absolutely no F%^&*(*G reason - PC the night before was copying files over to my server just fine, the next afternoon after work I fired up my desktop PC, could ssh into my server just fine, noticed my SMB shares were not working and my server was not even detecable on the network as far was explorer was concerned yet was absolutely online and available via SSH and obviously connected to my router just fine via the router management interface...

    Oh and YES I checked all my samba settings on my linux server before I even tried to resolve this issue thinking something might have gone **** there first... but NOOOOO it was as solid as its ever been, even kicked a user off to reboot the server manually in case there was some issue with the services RAM data (ecc ram so I seriously doubt it with no issues noted on the servers hardware diagnostics panel)...

    is this a case of MS screwing over people yet again OR WHAT changed in the last 3 days regarding WIN 10 OS?!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-11-04T18:46:17+00:00

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-11-04T17:47:41+00:00

    "Still can't access after reboot"

    1. in the 'Type here to search' box next to the start menu search for "Windows Features' click 'turn windows features on or off' go down to 'SMB 1.0/CIFS...' click the plus in front, uncheck any checked box in front of the 3 sub item

    reboot when prompted.

    1. go back into 'Windows Features' and put a check in front of 'SMB 1.0/CIFS Client' (only)

    reboot when prompted

    1. after reboot remove(disconnect) all mappings see:

    https://support.microsoft.com/en-us/help/890413/you-may-receive-the-the-local-device-name-is-already-in-use-error-mess

    "To resolve this issue, remove the existing network mapping. Then create a new network mapping for the share."

    That article is regarding connecting to shares on xp or before computers.

    1. Remap your shares.
    2. Reboot-test, Reboot-test  (it stayed working for me on various systems)

    NO registry editing or other settings where changed.

    What are you trying to map to (a linix box, windows box, network storage device, etc)?

    I followed your steps and procedure. Result is the same. Still can't access the map drive after reboot. I'm trying to map a shared folder from network storage drive.

    Was this answer helpful?

    0 comments