Foldersize wrong if folder contains very long paths

[StefanH]

I have to copy a folder from the network to an other location and to verify if everthing is ok I compare the foldersize from source and target. I'm wondering that it differ and it becomes clear that this is due to very long pathes of the source dir. Getting the folder size of the source with robocopy shows the correct size. See screenshot (right = source, left = target). I'm usiing Multicommander 15.2 on Windows11.
If I show the properties of the source folder with the file explorer it shows the correct size (like the result fo the robocopy).

Any ideas if this could be fixed by whatever setting in MC? It seems that the support for long paths isn't implemented so far.

[Matthias515566]

Your screenshots do show the correct directory size, though.

[Mathias (Author)]

I'm not able to test it at the moment..

But to get this right.
Folder sizing show wrong size on network path that are extra long ( Longer then 255char ) ?

Long path support is supported. but it might fail on some places. since not all windows API support it.
I know it worked before. But folder sizing has been reworked since then.
But it can most likely be fixed if it is an issue. I will check tomorrow

[StefanH]

I'm not able to test it at the moment..

But to get this right.
Folder sizing show wrong size on network path that are extra long ( Longer then 255char ) ?  => yes

Long path support is supported. but it might fail on some places. since not all windows API support it.
I know it worked before. But folder sizing has been reworked since then.
But it can most likely be fixed if it is an issue. I will check tomorrow