XYplorer Beta Club

Well done!

1) But I still cannot reproduce it. There must be another factor.

2) Can you also see the issue with foreground operations? (untick Configuration | File Operations | File Operations | Background Processing | Enable background processing)

Yes, confirmed I can still reproduce it with "check beforehand whether there is enough free space" and "Enable background processing" both unchecked. Total capacity, regardless of target disk, is shown as 32GB.

Is that path a junction?

No, plain directory path, and I am seeing the same 32GB capacity reported regardless of whether the drive is SATA, M.2, local, or NAS. As long as "check beforehand whether there is enough free space" is unchecked, I'm seeing 32GB reported as the total capacity.

Maybe a mount point then. I can see in the code what probably happens. The next beta should fix it.

My local folders were neither junctions nor mount points, but regardless, this is fixed in 23.80.0005

Thanks Don!

FYI, when you hover the mouse over the Used Space bar, the tool tip displays the drive for which the used disk space is shown. Is it really "S:\" in your case?

yes, the tooltip over the used space bar shows "S:\'"

OK, thanks. Then what actually happened was an underground API behavior change between Win8 and Win10 and later. Whatever, good that it's fixed.