CEA > Exit > Delete Command Hangs

[WirlyWirly]

XYplorer v28.00.0703
Windows 10 @ 100% (3440x1440)

Hello,

After a recent bug report that turned out to only be a problem for some users, I'm wondering if this is another one; seeing as I can't reproduce the bug with a ::fresh instance.

Setting the Configuration > General > Custom Even Actions > Exit == delete 0, 0, lax(<xypath>\Temp\*) doesn't work.

After closing XY and looking through the TaskManager, I can see that the XYcopy.exe process is hanging there indefinitely. I can open then close XY multiple times and the new processes will stack up.

2025-11-20_11-11-08.png

I'm sending you my XYPlorer.ini Don, maybe you see something I don't?

[admin]

Should be fixed in next beta.

1) The problem was caused by calling a background process (XYcopy) while exiting the app. Now processes are forced to the foreground when triggered while exiting the app (i.e. by CEA Exit).

2) By the way, delete 0, 0, lax(<xypath>\Temp\*):
a) No need for lax(), you can just do delete 0, 0, "<xypath>\Temp\*".
b) Why <xypath>\Temp\? The default temp folder is <xydata>\Temp\. <xypath>\Temp\ is usually not even writable.

[WirlyWirly]

Thanks, just updated and it's working great

I know I don't have to use lax(), I'm just in the habit of sticking it in whenever I'm working with paths

Also, I was playing with rclone's cache directory, so I pointed it to the first Temp folder I found while messing with the flags. I probably will end up using <xydata>\Temp

[admin]

Alright. Just to be clear: there are absolutely no disadvantages to using lax().