XnView locking handles

[bicarb]

Hi! This happens to me regularly. I am trying to rename a directory/folder that previously was open in XnView but now no longer is -- all images in that folder are closed, I have browsed elsewhere in the filesystem and am viewing images in a different folder. However, I am not able to rename the previously open folder either in XnView itself, in Windows Explorer, or in a cmd.exe window. Just get an error message (XnView = error renaming folder; Windows = can't rename, a program is using this file or folder.)

By searching in Process Explorer I can see that it is XnView itself which is maintaining a handle on the folder I am trying to rename. Within Process Explorer I can close out the handle by force and violence and then the folder can be renamed OK. This does not seem to make any problem for XnView. It does not complain, does not crash, and continues to function fine.

Has anyone else ever noticed persistant locks like this? Am I somehow using XnView improperly? Or--just thought of this--is it a problem introduced by using the portable edition from portableapps.com? Is there a setting I don't know about that would tell XnView always, always to release the lock on a directory/folder when all images in that folder have been closed and the browser has navigated away from it?

Thanks very much for advice! - Jim

details: Windows 7 ultimate, XnView 1.99.6 portable. (I use portable versions whenever I possably can in an effort to keep the awful ~\winsxs\ directory tree from growing to unmanageable size.)

[xnview]

Is it a folder shown in tree view pane?