Multi Commander > Support and Feedback

Multi Commander startup time is about 70 seconds

<< < (2/3) > >>

Mathias (Author):
Normally the timeout is not 40s.. not sure why it is that long for you. MC has no control over it.

Barney63:
Sorry for being a bit persistent here; I’d really like to use MC in the future.

I have now tested older versions of MC (portable 64-bit version).

The last version (and all older ones) that starts up quickly, as expected, is MultiCommander_x64_Portable_(15.5.0.3102). All subsequent versions exhibit this long delay.

MultiCommander_x64_Portable_(15.5.0.3102):

--- Code: ---2026-08-17 08:47:23.310 Initialization of Core started.
...
2026-08-17 08:47:23.790 Loaded config file : d:\temp\MultiCommander_x64_Portable_(15.5.0.3102)\Config\Modules.xml
...
2026-08-17 08:47:24.193 [Device Manager] - Starting to get device information for drive : W
2026-08-17 08:47:24.195 [Device Manager] - Get Device Icon for : W:
2026-08-17 08:47:24.203 [Device Manager] - Processing 'W:\' done
...
2026-08-17 08:47:25.857 Show Main Window
--- End code ---


MultiCommander_x64_Portable_(15.6.0.3119):

--- Code: ---2026-08-17 08:47:24.787 Initialization of Core started.
...
2026-08-17 08:47:25.546 Loaded config file : d:\temp\MultiCommander_x64_Portable_(15.6.0.3119)\Config\Modules.xml
...
2026-08-17 08:47:26.380 [Device Manager] - Starting to get device information for drive : W
2026-08-17 08:47:46.435 [Device Manager] - Get Device Icon for : W:
2026-08-17 08:47:46.461 [Device Manager] - Processing 'W:\' done
...
2026-08-17 08:47:47.644 Show Main Window
--- End code ---

That is why I still don't believe that Windows 11 (current version) is to blame here.

Mathias (Author):
There is no change between 15.5 and 15.6 that has anything to do with the startup.. Running them after each other will affect startup time since Windows will cache result for devices. and timeouts will be less.

There is NO API call in windows that say if a network device really is there or not. Windows will have to try to access it before it can say that.

Barney63:
Okay. For anyone else facing the same issue: I found a workaround; however, other applications (Explorer, Total Commander, Salamander ) now no longer visually distinguish between connected and offline network drives, because the connection is only established at the moment of access—specifically, when I click the drive letter within the application.

Registry tweak to address the delay

* Press Win + R, type `regedit`, and press Enter.
* Navigate to the following path: `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider`
* Look for the DWORD (32-bit) value named `RestoreConnection`.
* If the value does not exist, create it by right-clicking -> New -> DWORD (32-bit) Value and naming it exactly `RestoreConnection`.
* Double-click `RestoreConnection` and set the value to 0 (zero).
* Restart your computer.Note: With this setting, the network drive will no longer connect in the background during system startup (or application startup); instead, it connects only when you actively access it in File Explorer.

All versions of MC now exhibit the same startup behavior...

Barney63:
One more thing occurred to me: I reverted the registry change and launched MC v15.5 and v15.6 again. And bingo—fast starting v15.5 correctly distinguishes between online and offline network drives and displays them correctly. That doesn't happen in v15.6. It shows W: incorrectly as connected and did not show X:. There is a fundamental difference here.

Navigation

[0] Message Index

[#] Next page

[*] Previous page