Mapped Drives Crash On W11 Deployments

[SJ98]

Hello,

 

We've been testing a Windows 11 deployment through SCCM so that we can migrate our school PCs/Laptops to it before W10 goes out of support, and one main issue that we've come across that has halted our progress is that when the deployment has finished and you can log in, the log in process takes a considerable amount of time, and then when you go to File Explorer and double-click any mapped drive, the whole window freezes. We found that you can navigate to the drive if you type in the address for it, but the actual shortcut in File Explorer completely freezes everything up.

 

Just wondering if anyone else has come across this issue, as it's not something we're aware of? I believe it's going onto 23H2, and is just a standard W11 build with our image config pasted over the top.

Any knowledge or understanding would be appreciated!

[SJ98]

Thanks lofasonan,

I will have a look into this with my manager, hopefully it is something as straight forward as that! Was it any conflict specifically?

 

If there's any possibilities from any other user, please let me know!

[armadillo]

HI, did you manage to get a fix for this? we seem to be having same issue in one it room. Thanks

[SJ98]

Not really.

We ended up removing basically all of our GPOs and Regkeys etc and they did work, so it's obviously something to do with the way that it is set up.

Weird thing is though we can't pin down the exact thing that is breaking it.

[chaplic]

Assume nothing has changed at the fileserver backend?

 

How did the mapped drive get there? it is a persistent drive mapped elsewhere? can you map a new drive to the same share?

 

Are you accessing a windows file cluster, is Continuous Availability enabled on it?

 

Does it come back to life after 6 minutes?

 

Do a wireshark trace before you access it, do you see an attempt to connect to the fileserver on port 80? webclient could be messing with you.

[EvilEmpire]

Solved this one awhile back. It's a simple regedit that'll fix it. Teachers would take their domain joined laptop home, then complain about the green progress bar that always seems to take 15 minutes before windows explorer actually works. The problem is mapped drives. The device will keep trying to connect, then after not connecting it finally times out. This also happened with autopilot / AAD devices using mapped drives as well.

 

Now for the fix...

 

Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider]"RestoreConnection"=dword:00000000