Recent Posts

41

Support and Feedback / Re: Problem with move

« Last post by Lukasz S. on July 13, 2026, 23:51:53 »

I've sent you my file operation logs, maybe it support you with finding the issue please check the email.
Some logs are quite heavy over 15MB and you can find errors  there, it seems that MC would like to repeat move operation but there are no files because all of them were already moved.
I think the app is stuck in some kind of loop

42

Support and Feedback / Re: Problem with move

« Last post by Mathias (Author) on July 13, 2026, 22:59:55 »

Lets keep the issues separate..  move the post to own thread.

what build 3190 ? I can't reproduce any issue doing an abort of move operation.

if I move folder to target panel where we have the same folder, files are moved but folder remains in source panel.

Will check. Move of folder is skipped since it already exists.. so kind of not a bug. But I guess it should be delete anyway.

If there is a lot folders MC is preparing to move operation for a long time and nothing happend. Sometimes there is an error displayed, files are moved but folders remain. There is something wrong with folders operation I'll continue testing.

OK not very specific on what is happening and what the issue is.. So not much to go on..  If you see it again. check fileoperations logs (ctrl+L)

43

Support and Feedback / Problem with move

« Last post by Lukasz S. on July 13, 2026, 21:30:18 »

Similar issue is during moving folder with files. I'm not able to abort operation. Additionally if I move folder to target panel where we have the same folder, files are moved but folder remains in source panel. If there is a lot folders MC is preparing to move operation for a long time and nothing happend. Sometimes there is an error displayed, files are moved but folders remain. There is something wrong with folders operation I'll continue testing.

BR
Lukasz

44

Support and Feedback / Re: MC not starting after updating to v16.0 (build 3186)

« Last post by Mathias (Author) on July 13, 2026, 13:37:53 »

build 3189 was bad. not all new files in the release was correct version. so there is a 3890 that should be correct..

45

Support and Feedback / Re: MC not starting after updating to v16.0 (build 3186)

« Last post by Mathias (Author) on July 13, 2026, 13:09:21 »

Might be that it got corrupted when it did not work before. or something else has the file open so it cant resave it

46

Support and Feedback / Re: MC not starting after updating to v16.0 (build 3186)

« Last post by ncodina on July 13, 2026, 12:56:59 »

16.1 out now. It should now load config file using UTF8 encoded path. so it is not fail on path containing special characters

Thank you! Now it kinda starts. I'm not getting the previous error message, but it looks like it cannot read or save the config files. It says Access Denied, even if I run it as admin.

47

Support and Feedback / Re: MC not starting after updating to v16.0 (build 3186)

« Last post by Mathias (Author) on July 13, 2026, 11:25:42 »

16.1 out now. It should now load config file using UTF8 encoded path. so it is not fail on path containing special characters

48

Support and Feedback / Re: [Bug] Shift+F4 doesn't launch an editor

« Last post by Mathias (Author) on July 13, 2026, 11:25:02 »

16.1 out now.. Create and Edit should work again

49

Support and Feedback / Re: [Bug] Shift+F4 doesn't launch an editor

« Last post by Jungle on July 13, 2026, 11:06:09 »

I've never used installable versions. Portable only.

50

Support and Feedback / Re: MC not starting after updating to v16.0 (build 3186)

« Last post by Mathias (Author) on July 13, 2026, 10:36:54 »

Hi Mathias, thanks for your quick reply.
I'm running it on Windows 11 Pro (26200.8655).
My user name does contain a special character "é", but MC has been working fine until today within the same path.
I tried Portable version from an easier path. First run was ok, I restarted it and I'm getting the same error again, pointing at the same original path (AppData\Roaming...).
I'm attaching one of the logs I got.

Xml handling in MC is done from a 3rd party library. and all of them are updated. and I saw something that they do not handle Windows UTF16 encoded path anymore.. so must be UTF8 encoded.. so I think that that might be the reason