XYplorer Beta Club

1. 28.30.1700 (64bit)
2. Win 10 Pro
3. 100%

I have two copies of XY, Both on Win 10, 100% scaling, both up-to-date, both use nvme drives.

If I add a slash to a folder name (to easily create a subfolder from the name) (There's a setting that controls this particular ability, but I don't recall what it is):
On PC #1 - The response is near instantaneous. Folder is created, usable immediately.
On PC #2 - The same task takes 30-60s for XY to become responsive again; However, if I look at the folder with another application, it performs the task essentially immediately.

This problem has been around as long as I can remember, however it was only recently that I tried the same thing on another pc.

Attached is a screen recording. I tried to add an MP4 as well, since it is annoying to wait 50seconds but I don't think it let me.
Here is a link to the mp4 scren recording so you can skip ahead: https://savedly.net/f/u6x424qh


So;
1. Why is this happening?
or
2. How can I troubleshoot when an action in XY takes a long long time?

Is a network path involved?

admin wrote: ↑11 Aug 2026 10:54 Is a network path involved?

No. The example demonstrated was under C:\, on the NVME as mentioned.

Same behavior with the 32-bit XYplorer?

admin wrote: ↑14 Aug 2026 08:58 Same behavior with the 32-bit XYplorer?

I have not used it since the upgrade; But as I recall, I'm pretty sure this was an issue in that version as well.

1) It happens 100% each time?
2) With any path, or only there?

admin wrote: ↑14 Aug 2026 21:10 1) It happens 100% each time?
2) With any path, or only there?

1) Yes, here's two different drives, an SSD and a removable USB, same thing. Always.
2) I thought I'd answered this already, so I'm not sure I understand the question. But Any path that I add a slash to, to create a sub-directory, yes. Doesn't matter if it's empty, has files, or which drive it is on. (see attachments)

Can't explain it. It works instantly here all the time.

admin wrote: ↑16 Aug 2026 09:08 Can't explain it. It works instantly here all the time.

Understood. How can I troubleshoot this, debug it, log it, something?

Currently there is no way to dig into this within the app. Which leaves you with comparing your systems: What might be the crucial difference between the fast one and the slow one?

admin wrote: ↑20 Aug 2026 16:00 Currently there is no way to dig into this within the app. Which leaves you with comparing your systems: What might be the crucial difference between the fast one and the slow one?

I tested ::fresh the other night, and after enabling 'allow move on rename' it's near instant on the 'slow' pc. That means it's an XY configuration/bug problem.
Admittedly, I've had a license for a almost 20 years at this point. I'm sure my ini file has lots of old, dead tweaks and changes in it.
But, this points to the fact that it's not a problem between two PC's, it's a problem somewhere within XY, right?

Is there a way to (at your leisure) put something in a build to record a trace log of some kind? I realize I'm edge case in this.

Ever tried to copy the ini from PC1 to PC2 and see if it makes a difference?
If it does, compare the two ini files to find the differences.

RalphM wrote: ↑21 Aug 2026 02:23 Ever tried to copy the ini from PC1 to PC2 and see if it makes a difference?
If it does, compare the two ini files to find the differences.

Probably harder than it sounds considering that (I'll continue using slow and fast) the Fast PC's ini started out as a copy of Slow PC and the ini file at the moment looks like 120KB, while the fast pc is 200kb.

Just backup/rename the current ini of the slow pc and copy the one from the fast one over to see if it makes a difference for this problem.
If not delete that copied ini and restore/rename the old one again.
Are you doing completely different things on the two pc's so you want to keep the ini's as they are?

I'm curious to see what comes out. 50 seconds is a long time. It will probably be some heavy columns or a script triggered by custom event actions.