1803 breaks network drives?


  1. khl
    Posts : 41
    Windows 10 32 bit
       #1

    1803 breaks network drives?


    Here's something that forced a rollback from the Windows 10 version 1803 update. After installing the update, I could no longer write to or reach a USB flash drive that was being used as a network drive through a Linksys router. All attempts to solve this failed, and Microsoft level two support could not find a solution. The only way out was to roll back to version 1709. Right now, this is an unsolvable problem, and that evaluation comes from Microsoft support. You may want to check for similar trouble after installing version 1803.
      My Computer


  2. Posts : 14,409
    Win10 Pro and Home, Win11 Pro and Home, Win7, Linux Mint
       #2

    I still have my 2 NAS drives even with the new 1809 but they are Ethernet-cable connected. I don't Map the drives but do Map the Public Folder on the drives. I haven't tried the USB connection yet, only have one on the Router.
      My Computers


  3. Posts : 752
    Windows 10 Pro 64-bits
       #3

    The 1809 update changed how the shared resources are connected, when compared to 1803 version. I'd like to say that 1809 is the same as it had been in 1709, but I have not finished testing it yet.

    You should look at the excellent tutorial how to share resources in Windows 10, especially, if you're having issues:

    Share Files and Folders Over a Network in Windows 10 | Windows 10 Tutorials

    PS: I've updated my system last week to 1803 and the system had similar issues as yours. That issue seem to disappeared, when my PC accidentally updated to version 1809, forgot to set the policy of delaying feature updates...
      My Computer


  4. Posts : 1,471
    Win10 Home x64 - 1809
       #4

    FWIW ... Running Win10 1809 and no issues with connect/read/write to my NetGear Router with USB HDD (ReadyShare). I can access it as a mapped drive, by IPAdress & by ShareName. I don't have SMBv1 installed as I no longer have any legacy devices on my network, but without SMBv1 it doesn't automatically appear in File Explorer > Network like my other Win10 Shares do. It actually uses SMBv3 for the connection, so I think this is more of a NetGear Samba issue vs Win10 issue, but don't quote me on that :)
      My Computers


  5. Posts : 1,689
    X
       #5

    I haven't had any sharing problems with Windows 10, regardless of version (every version since 1703 (or 1704?).
    So I wonder why some people have problems and others do not.

    I create shares with "net use X: \\host\C password /user user-name /persistent:yes"
    Is that why mine always works?
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:16.
Find Us




Windows 10 Forums