Windows 10: 24H2 update leads to mapped drives using namespace problems

Ever since our computers upgraded to 24H2 Win11, I have been having problems with virtual drives mapped to a namespace. Some computers maintain the connection reliably, others disconnect. Prior to 24H2, they all worked reliably. anyone have any ideas?

:)

 

Problems with mapped drive

Well I got one step closer to getting the mapped drive working.

Instead of using Windows 10 File Explorer to map the Network Drive, I do it manually from a Command Prompt run as Administrator:

net use G: \\XP07\XP_Dev

After executing this command I can copy files to and from the mapped drive to the system disk. And while this is a huge step forward there are still other problems with the mapped drive.

Opening a jpg file in Paint by clicking it from File Explorer loads the picture just fine, but I can't save it. When Paint tries to save the file it can't find the mapped drive, it doesn't even show up when browsing for a place to save it.

There are a few links on the web discussing this very issues of not being able to browse a mapped drive from within a program. There is supposed to be a registry fix for this by adding EnableLinkedConnections and settings it's value to 1 but it didn't work.

So the next step after getting File Explorer working is to somehow get programs to see the mapped drive.

 

Mapped Drives Issues

To clarify .... the issue is the Windows 10 OS. It is with Windows File Explorer. The Mapped drives used to appear in File Explorer's left panel list of drives and folders. Two days ago File explorer stopped show the mapped drives. so not they don;t appear in the list of Drives and folders.

- - - Updated - - -

I did, it has no effect. I also check the NAS devices they support SMB 2.0. Also I have several other computers on my home network they work fine with the mapped drives and They do not have SMB 1 turned on. So it is something that happened to the computer in question.

 

Connecting NAS - mapping of drives

Ok, If you want, we can do a step by step troubleshooting of your current situation: If you are able to ping your Machine and it responds. Code:

Try to view if your NAS appears on the Network List: Code:

If Your NAS appears on the list, try to view it: Code:

The available shares will be listed there. Then Try to List the content of one of the directories: Code:

This should list the content of the directory, If all this works Try to map a drive on one share: Code:

Pls reply with the "response" of the first "encounter" of a non positive output. This exercise should reveal if you have a Network or Protocol or Cipher or Authentication problem.