Multi Commander startup time is about 70 seconds

[Barney63]

New MC user here, Multi Commander startup time is about 70 seconds, both installed and portable version. OneDrive is installed and active. Any ideas?
Windows 11, all updates.

(cutted...)
2026-08-07 10:18:53.311 Use extra UI thread for progress dialogs : 0
2026-08-07 10:18:53.316 Failed to read the key mapping file : CustomKeymappings.xml
2026-08-07 10:18:53.375 Copied templete config file : "C:\Program Files\MultiCommander (x64)\Config\Scripts\Examples\Examples.zip" to (cutted...)
2026-08-07 10:20:04.045 OneDrive folder not found : ""
2026-08-07 10:20:04.045 OneDrive folder not found : ""
2026-08-07 10:20:04.062 Dropbox appdata folder not found : "C:\Users\Bernd\AppData\Roaming\Dropbox"
2026-08-07 10:20:04.062 GoogleDrive folder not found : "<empty>"
(cutted...)

[Mathias (Author)]

in core setting for logging.. for application log , change loglevel to full.. and you will se in more details in the log., often it is becuse it tries to get information about remote devices that is not reachable.

[Barney63]

Thank you.

P:, W:, and X: are mapped network drives belonging to PCs that are only in use intermittently and are powered off when Multi Commander starts up.
P: causes a startup delay but is not displayed as "offline" within MC; this only happens with W: and X:.
When I bring P: online, W: then causes a startup delay. It seems Multi Commander generally struggles with offline network drives and consequently skips the subsequent offline drives?
I also currently use Total Commander, which does not exhibit this behavior; it always starts quickly and immediately displays P:, W:, and X: as offline drives.

If P: ist offline, it delays startup:

2026-08-08 10:22:06.737 [Device Manager] - Starting to get device information for drive : P
2026-08-08 10:22:30.442 [Device Manager] - Get Device Icon for : P:
2026-08-08 10:22:30.457 [Device Manager] - Processing 'P:\' done
2026-08-08 10:22:30.457 [Device Manager] - Starting to get device information for drive : W
2026-08-08 10:22:30.459 [Device Manager] - Get Device Icon for : W:
2026-08-08 10:22:30.480 [Device Manager] - Processing 'W:\' done
2026-08-08 10:22:30.480 [Device Manager] - Starting to get device information for drive : X
2026-08-08 10:22:30.483 [Device Manager] - Get Device Icon for : X:

If P: ist online, now following W: delays startup:

2026-08-08 10:54:36.906 [Device Manager] - Starting to get device information for drive : P
2026-08-08 10:54:36.907 [Device Manager] - Get Device Icon for : P:
2026-08-08 10:54:36.916 [Device Manager] - Processing 'P:\' done
2026-08-08 10:54:36.916 [Device Manager] - Starting to get device information for drive : W
2026-08-08 10:54:57.930 [Device Manager] - Get Device Icon for : W:
2026-08-08 10:54:57.944 [Device Manager] - Processing 'W:\' done
2026-08-08 10:54:57.944 [Device Manager] - Starting to get device information for drive : X
2026-08-08 10:54:57.946 [Device Manager] - Get Device Icon for : X:

Can I change this behavior regarding network drives via configuration?

[Mathias (Author)]

MC does not handle the network it self. It is all done by Windows. and sometimes Windows does not know if it is available until it tries to access it. and it takes a while before it times out.

[Barney63]

Other applications display the drives, and the timeout (typically 5 seconds for network drives, not 40 seconds) only occurs when the drive is selected. No Windows application I am aware of takes 40 seconds simply because there are disconnected network drives.

[Mathias (Author)]

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