So if you could close whatever is left open after the log has been written, that would be great

Oh sure, I'm using it all the time! My favorite shell extension.Lare2 wrote:I know this doesn't address your issue. But I found a program that may come useful, not only for when XYplorer does it, but to really know who's the culprit.
Take a look at it. http://ccollomb.free.fr/unlocker/
Yes, bug confirmed. Research brought up surprise: it wasn't me!jacky wrote:So if you could close whatever is left open after the log has been written, that would be great
Right, thanks, though as I said, I already know about it/use it. That's actually how I found out the lock on my USB drive came from XYLare2 wrote:I know this doesn't address your issue. But I found a program that may come useful, not only for when XYplorer does it, but to really know who's the culprit.
jacky wrote:...now each time I have to use Unlocker first, since XY won't let go.
That's good news indeed.admin wrote:The good thing is: when I fix this it will fix the same problem whenever the common dialog is called in XY. Let's see...