@df14936 Win 11 has issues with shared files over the network.  Its been a problem for a while.

  @df14936 

I am in a similar  situation..

Even sharing drives on a W10 and W11 PC is problematic... Same for the router USB drive...

I did find though it does 'work better' if you use the NET VIEW \\IP Address of the router that it does work. For instance from my W11 PC Command prompt;

Hmm, some Windows Updates I guess changed how it works?

=================

C:\>net view \\tp-share
Shared resources at \\tp-share

Share name  Type  Used as  Comment

-------------------------------------------------------------------------------
G           Disk
The command completed successfully.

C:\>net view
System error 6118 has occurred.

The list of servers for this workgroup is not currently available

===================

So using the SHARENAME will work? NET VIEW on the other PC and mine works fine, but NET VIEW by itself will not?

I suggest you create and ICON using NET USE X: \\tp-share\g where X is any non-assigned drive letter and 'g' is the actual name of the USB drive. Then you can use 'X:' anywhere on either PC to access the USB share.

I have found that even though the USB drive does not show the files or directories that are on it. if I have a program with a drive location on it saved, it can back up files onto the dirve.

Also I can set a network location (ftp) and open it and see the files.  But of course you can't open them directly from there.

Don't know if any of that sheds any light on the problem.

@df14936 

  @IrvSp 

Unfortuntaly, this gives the same result.  

The first time I open the link, everything shows up.  The next time, it is again blank.

I have to go to the properties and change the security settings and then I can see everything for one or two times opening the link, then it resets itself again?

  @df14936 

I can't help here, different from what I am experiencing.

TP-Link support was on my PC debugging this. Capturing TCP/IP packets and it clearly IS Windows problem. I am on Win 11 24H2, and the problem is due to that it seems?

  @df14936 

From reading this and other threads there is no workaround or fix other than going back to 23H2.