TheArkive
New Member
- Messages
- 5
SOLVED
Basically when I map network drives (even just one) the EXPLORER.EXE file browser hangs. Admittedly I usually have at least 4 drives mapped at any given time. And they aren't always connected.
Now that I've removed all network drives and replaced them with "network folders" it opens instantly again.
I see the difference. The network drive link actually shows drive space used/free, not to mention a different context menu. And now it's making sense as to why it's slower.
I'm just wondering if anyone has found a way to get explorer.exe to load instantly with network drives mapped, and have explorer simply update the GUI and list the drives as they are pinged/detected, instead of the entire file explorer hanging?
I frequently access my local drives, and waiting for the network drives to be seen by windows is a pain.
Has anyone found a work-around for this? ... I might have to go back to Explorer++
SOLUTION
Delete drive mappings and re-map them.
Who knew it would be that easy...?
MORE INFO
It seems there's a bit more to this.
The mapped drives can still cause problems if there is some heavy network traffic going on. It doesn't have to be coming from/going to the mapped drives either. It can be as simple as an internet download going at about 2-4 MBps. At that point (at least for me) the entire computer is lagging (downloading to the local drive). During the download, I happened to think of my original post here and so I removed all the mapped drives again, and once again, EXPLORER.EXE came back as speedy as ever with no mapped drives.
So I want to pose the same question as above:
Anyone know of a way to get explorer to just list the mapped drives from cache/memory and then to poll the stats on free/used space? As opposed to waiting to get all that info first and then displaying the drives 20 seconds later?
Basically when I map network drives (even just one) the EXPLORER.EXE file browser hangs. Admittedly I usually have at least 4 drives mapped at any given time. And they aren't always connected.
Now that I've removed all network drives and replaced them with "network folders" it opens instantly again.
I see the difference. The network drive link actually shows drive space used/free, not to mention a different context menu. And now it's making sense as to why it's slower.
I'm just wondering if anyone has found a way to get explorer.exe to load instantly with network drives mapped, and have explorer simply update the GUI and list the drives as they are pinged/detected, instead of the entire file explorer hanging?
I frequently access my local drives, and waiting for the network drives to be seen by windows is a pain.
Has anyone found a work-around for this? ... I might have to go back to Explorer++
SOLUTION
Delete drive mappings and re-map them.
Who knew it would be that easy...?
MORE INFO
It seems there's a bit more to this.
The mapped drives can still cause problems if there is some heavy network traffic going on. It doesn't have to be coming from/going to the mapped drives either. It can be as simple as an internet download going at about 2-4 MBps. At that point (at least for me) the entire computer is lagging (downloading to the local drive). During the download, I happened to think of my original post here and so I removed all the mapped drives again, and once again, EXPLORER.EXE came back as speedy as ever with no mapped drives.
So I want to pose the same question as above:
Anyone know of a way to get explorer to just list the mapped drives from cache/memory and then to poll the stats on free/used space? As opposed to waiting to get all that info first and then displaying the drives 20 seconds later?
Last edited:
My Computer
System One
-
- OS
- Windows 8
- Computer type
- Laptop
- System Manufacturer/Model
- iBUYPOWER CZ-12
- CPU
- Intel Core i7-2860QM @ 2.5GHz
- Motherboard
- Compal PBL21
- Memory
- 8GB DDR3 PC3-10700
- Graphics Card(s)
- NVIDIA GeForce GT 540M Rev A1
- Browser
- Firefox
- Antivirus
- ESET Smart Security