years..decades! And file explorer still does this! network timeouts

[JeffMD]

Any time I accidently try to access (ie click on) a network resource that is unavailable, that window of file explorer becomes unusable until its internal timeout meter is reached. I can GO to other directories and drives but they will not show anything in them (refresh) until the network search bar at the top has timed out. This is amateur hour peoples.. the process that is handling the network connection should be separate and asynchronous to file explorer and the file explorer window should be free to MULTITASK to other things while waiting on the network connection.

/rant

 

[ArisVer]

Change OS?

 

[JeffMD]

my pc is built around gaming, that isn't going to happen for a while. -_-

 

[Red Squirrel]

Yeah windows has always been horrible for that, I don't understand why they can't fix that issue. That and if there is 1 error it halts the entire copy operation instead it should keep copying and just have an error summary at the end giving you various options of what to do with those files such as copy elsewhere or just generate a list that you can paste somewhere. Though I have not played much with Linux GUI file copies I imagine it's the same thing. I always use command line and rsync for large copies.

 

[tidy]

.

 

[Dahak]

Well for copying, they did fix it in Win8+, it will continue to copy and then at the end will give you the errors or if you need to copy over something that is there.
In addition to allow you to pause a copy and resume it too

For the network explorer issue, yes that is still annoying

 

[plion]

does folder properties>view>'launch window in separate process' fix this?

 

[R0H1T]

does folder properties>view>'launch window in separate process' fix this?

Probably not, since the underlying issue isn't resolved looking at the posts above, however it does give you the option to kill the (explorer) process without restarting the shell.