Major Problem when unmounting drives while SBxed apps run

[OwenBurnett]

I found a major problem when I try to unmount a drive (Unplug an USB HDD, or unmount a TC volume) while a program insandbox is running the drive latter is not being freed, untill the SBxed process is cloded.

EDIT: an other related problem:
when I mount or plug in a drive while a process is running in SB the process can not accedd the drive.

Owen

[tzuk]

The second problem is expected. Sandboxie scans and remembers drive letter information when a sandboxed program comes up, and this doesn't get refreshed later on.

This could be improved in a later version, perhaps, but I won't deal with that now.

As for the first problem: With TrueCrypt I was also able to reproduce this problem. I mounted drive T:, started a sandboxed command prompt, typed dir T: and I get

Volume in drive T has no label.
Volume Serial Number is 45E9-C634

Directory of T:\

File Not Found

Then I unmounted the drive and typed dir T: in the sandboxed cmd:

The system cannot find the file specified.

However, TrueCrypt displays drive U: twice, in other words, its display of drives got messed up to display U: instead of T:.

As soon as I exit the sandboxed cmd, the TrueCrypt display is corrected.

* * *

If I use Process Explorer to look into a sandboxed app, I see it holds open handles for the drives available when the app started. This may be what is keeping the drive from being ultimately unmounted. I'll see if this is something I can fix.

* * *

(Later) Yes, that was it, and there was no reason to keep the handles open. I fixed it now, thanks.