Can't access shared USB drive after Windows 10 update to version 2004

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Can't access shared USB drive after Windows 10 update to version 2004

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Can't access shared USB drive after Windows 10 update to version 2004
Can't access shared USB drive after Windows 10 update to version 2004
2020-07-23 16:53:39 - last edited 2020-07-27 01:13:59
Model: TL-WDR4300  
Hardware Version: V1
Firmware Version: 3.13.33 Build 130617 Rel.46239n

OS Windows 10 Professional

 

I use a USB drive plugged into this router to be able to access it from all computers on my home network. With Windows 10 version 1909 this worked without a problem, but I had to enable SMB1 protocol (disabled by default).

 

I've now upgraded to version 2004 and the USB drive is no longer accessible - if I try to access it using \\tplinklogin.net it gives and error

 

 

Does anyone know how to enable this device using Windows 10 version 2004?

  0      
  0      
#1
Options
1 Accepted Solution
Re:Can't access shared USB drive after Windows 10 update to version 2004-Solution
2020-07-25 07:57:56 - last edited 2020-07-27 01:13:59

@simonc8 

 

If you have not already, try mapping the USB device using the router IP address rather than its name.

 

So where you would map (on my router anyway) \\router-name\volume(sda1) try mapping to \\192.168.1.1\volume(sda1)

 

Obviously if your router doesn't call your USB device volume(sda1) then substitute its name.

 

This is working for me.

 

 

 

 

 

 

Recommended Solution
  1  
  1  
#4
Options
5 Reply
Re:Can't access shared USB drive after Windows 10 update to version 2004
2020-07-24 09:22:55

@simonc8 

 

Hello,

 

Can you please confirm again if the SMB1 protocol is still enabled on the Windows 10 version 2004?

 

BTW, do you have any other computer and try to access the USB just for a check?

 

Thanks.

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer BE800 New Firmware Added Support for EasyMesh in AP Mode, DoH&DoT, and 3-Band MLO Connection Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#2
Options
Re:Can't access shared USB drive after Windows 10 update to version 2004
2020-07-24 12:50:44 - last edited 2020-07-24 12:51:01

@Kevin_Z 

 

Thanks for your reply.

 

I can confirm SMB1 is enabled:

 

There are two other computers on the network which can still see the USB drive, one is running Windows 10 Pro build 1909 and the other Windows 10 Pro build 1903.

 

I've since found other threads covering this same issue, sadly none has a solution, for example

SMB sharing not working after windows 10 update Build 2004 update

  0  
  0  
#3
Options
Re:Can't access shared USB drive after Windows 10 update to version 2004-Solution
2020-07-25 07:57:56 - last edited 2020-07-27 01:13:59

@simonc8 

 

If you have not already, try mapping the USB device using the router IP address rather than its name.

 

So where you would map (on my router anyway) \\router-name\volume(sda1) try mapping to \\192.168.1.1\volume(sda1)

 

Obviously if your router doesn't call your USB device volume(sda1) then substitute its name.

 

This is working for me.

 

 

 

 

 

 

Recommended Solution
  1  
  1  
#4
Options
Re:Can't access shared USB drive after Windows 10 update to version 2004
2020-07-25 10:25:28

@Tog 

 

Thanks - it worked!!!! Brilliant.

  0  
  0  
#5
Options
Re:Can't access shared USB drive after Windows 10 update to version 2004
2020-07-27 10:13:19 - last edited 2020-07-27 10:14:18

@Tog

 

At least, it worked on Saturday - today (Monday) when I booted up the PC (didn't use it yesterday) the mapped drive was no longer available. First attempts to remap it failed as Windows said there was no folder with that name, then I logged in to the router in a browser, and tried mapping the drive again, and this time it worked.

 

Perhaps I am going to have to go through this every time I boot the computer... 

  0  
  0  
#6
Options

Information

Helpful: 0

Views: 2856

Replies: 5

Related Articles