Recent Posts

1

Support and Feedback / Re: Trend Micro Maximum Security detected Ransomware

« Last post by Mathias (Author) on Today at 09:19:13 »

Root cause is that the Trend sucks. and they have bad way to detect threats. The way AV software work it is real easy to flag files that are not an issue.

And False Positives are super common for Filemanager application. AV software see that this application is using lots of file APIs and that look suspicious so then it flags it, It often goes away after a while when their process have checked it more in depth or something.

Since false positives are super common a good way to verify is to use virualtotal.com to check files. if just some report its bad then its probably false positives. if most of them flags it then it is bad.

2

Support and Feedback / File Verifier does NOT check sha files

« Last post by SwissKnife64 on Today at 09:04:04 »

Observation: when clicking on SHA checksum file, the "File Verifier" opens. I can add the corresponding file for check. Pressing the start button for the SHA check , 0 (zero) files are checked.
Using the dialog with only a MD5 checksum, the dialog adds the corresponding fiel automatically and check works fine.

Expectation: the SHA check works the same way as the MD5 check.

Version: (x64) v16.2 (build 3205)

3

Support and Feedback / Trend Micro Maximum Security detected Ransomware

« Last post by lightpower on Today at 02:48:22 »

Trend Micro Maximum Security found a virus in the executable I installed.
Please check the root cause.

Date/Time   Threat   From   Version   Copyright   Detected Resource or Process ID   Response
8/20/2026, 8:37:02 AM   C:\Program Files\MultiCommander (x64)\MultiCommander.exe   Mathias Svensson   16.2.0 build 3205   2026 Mathias Svensson. All rights reserved   C:\Program Files\MultiCommander (x64)\MultiCommander.exe   Terminated

4

Support and Feedback / Created new Favorites Quick Path and it duplicated

« Last post by JBG2963 on Yesterday at 22:46:16 »

Hi,

I'm new with using Multi Commander (x64) v16.2 (build 3205) - Date of build : Aug 19 2026. What I did was create a new Favorites Quick Path. The stars along with the same shortcut numbers and names were duplicated. Is this the way the software should work? If not, it's a bug. I've attached a screenshot.

Please advise.

Thank you,
JBG2963

5

Support and Feedback / Tab colours

« Last post by Lukasz S. on Yesterday at 17:02:18 »

Hi,

I found that colours which I set for the tabs are not showed correctly, please see attached screenshot.
The issue is connected with setting tab and not active tab.

6

Support and Feedback / Re: Multi Commander startup time is about 70 seconds

« Last post by Mathias (Author) on August 17, 2026, 11:16:26 »

Sorry. No there is no difference in the code for this. code for this is exactly the same in 15.x and even in 16.x  But Windows it self should cache device status.

You can turn off device in core settings > FileSystem > Tweaking.
Under Hide Device. then MC will not probe any of them.

7

Support and Feedback / Re: Multi Commander startup time is about 70 seconds

« Last post by Barney63 on August 17, 2026, 11:12:50 »

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.

8

Support and Feedback / Re: Multi Commander startup time is about 70 seconds

« Last post by Barney63 on August 17, 2026, 11:00:33 »

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...

9

Support and Feedback / Re: Multi Commander startup time is about 70 seconds

« Last post by Mathias (Author) on August 17, 2026, 10:04:41 »

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.

10

Support and Feedback / Re: Multi Commander startup time is about 70 seconds

« Last post by Barney63 on August 17, 2026, 09:07:40 »

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: [Select]

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

MultiCommander_x64_Portable_(15.6.0.3119):

Code: [Select]

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
That is why I still don't believe that Windows 11 (current version) is to blame here.