windows explorer 'stalls' because of it's timeout duration. Windows Explorer is at the mercy of the devices it's trying to list. If any of those devices experience a delay in returning the information that Windows Explorer is asking for, you'll notice a delay.
Disconnecting network drives and perhaps unplugging other devices could at least give you a clue as to which device is contributing to the delay.
So .. no matter whos' File Manager is used, if it asks for information from a device that takes it's time answering (or doesn't answer at all) there will be a delay.
Another reason for a slow file manager might be that your PC has so much junk and spyware on it that explorer chokes. Do a cleanup.
Now, write a file manager with a timeout configuration value that's user adjustable.
Maybe I've used the wrong term. What I meant by "stall" is that when it displays an error message and then abandons the whole copy/move operation, leaving user in a confusion state of a folder split into two places...
For Each ctrl As Control In Me.Controls("pnlMainPanel").Controls
If ctrl.GetType Is GetType(System.Windows.Forms.Panel) Then
For Each subCtrl As Control In ctrl.Controls
If subCtrl.GetType Is GetType(System.Windows.Forms.TextBox) Then
If subCtrl.GetType Is ...