Author Topic: External Refresh issue  (Read 14056 times)

Matthias515566

  • Power Member
  • ****
  • Posts: 323
    • View Profile
External Refresh issue
« on: May 27, 2018, 11:45:48 »
When multiple instances open and a external HDD is disconnected, MC think sometimes the HDD isnt disconnected. When a Android Smartphone disconnected, MC think it is still connected. When a Android Smartphone reconnected, MC have yet the old links and can't connect to a reconnected Smartphone. But wenn a new file created or a file overwritten in most cases MC recognize it, but sometimes i need to press the refresh button. But the refresh button do not help for Smartphones which are via MTP connected.
« Last Edit: May 27, 2018, 12:33:11 by Mathias (Author) »

Mathias (Author)

  • Administrator
  • VIP Member
  • *****
  • Posts: 4411
    • View Profile
    • Multi Commander
Re: Refresh issue
« Reply #1 on: May 27, 2018, 12:32:58 »
When multiple instances open and a external HDD is disconnected, MC think sometimes the HDD isnt disconnected.
Hmm If it is a normal drive then Windows should notify MC about that,
I can't recreate that. If I remove external device that is F: then F: goes away in MC. 

When a Android Smartphone disconnected, MC think it is still connected.
Yes, That is because Windows does not always notify MC when phone using WPD is disconnected.  Some phones works some dont





Matthias515566

  • Power Member
  • ****
  • Posts: 323
    • View Profile
Re: Refresh issue
« Reply #2 on: May 28, 2018, 08:01:14 »
If I remove external device that is F: then F: goes away in MC. 
Yes, it works also for me, but sometimes not.

Ulfhednar

  • Contributor
  • VIP Member
  • *****
  • Posts: 514
    • View Profile
Re: External Refresh issue
« Reply #3 on: May 28, 2018, 10:51:35 »
I posted this in another thread but may be relevant here...
Quote
I have been finding erratic & slow USB recognition/processing for a while with W10, after a lot of messing about it looks like it is related to w10 recent builds & USB drivers.  I have had things working perfectly, w10 update screws it, new drivers come out - fixes it; then w10 breaks it again....

Using different external hubs dramatically changes performance for me when connecting v 1.1 or v2.x to v3 ports.
v3 is supposed to be compatible with v2 but it hasn't been 100% for me this year, last year it was ok & everything was recognised correctly. 
Sometimes now I need to daisy-chain devices with a hub to get recognition/performance.