When either dragging an encrypted disk to the trash or clicking on it in the menubar list I get the message:

The Disk “name” needs to be ejected first before it is removed

Not sure what this means since the disk disappears from the desktop like you would expect. There doesn’t seem to be anything else really to do.

The message you saw is an error message (although probably a badly worded one): After you closed the whole-disk vault, Knox tried to eject the underlying volume, but the operating system responded with an error. Normally, Knox would say “Safe to remove ‘name’—The vault ‘name’ was closed successfully and the disk can now be safely removed.”

Does this always happen—have you ever got the “Safe to remove” message?

If not, there might be an application running on your system that dissents to the eject Knox is trying to perform. Do you have an antivirus application or some other disk-related tool running? If you go to /Applications/Utilities/Disk Utility, do you still see the disk there after this happens?

Sorry about the trouble—hopefully we’ll get to the bottom of this.

I’ve never seen the safe to remove message when dragging the encrypted volume to the trash. I get the warning every time. I created a vault on my startup drive and when trashing it i get no message at all (which is fine). I also created a vault on a usb thumb drive and when trashing it I get no message either.

After trashing the encrypted volume and running Disk Utility I see the manufacturers name in the drive list and underneath it the “name” (Knox Vault) listing grayed out.

Hope this helps.

Unrelated Idea: This is probably outside the scope of your intention with this program but it would be great if Knox could unmount a vault after a predetermined idle time.

Thanks.

Okay, looks like a bug to me—I’ve heard from one other person with the same problem. We’ll have to investigate.

We get requests for the automatic unmount every once in a while, but we recommend just using a password-protected screensaver instead. With automatic unmount, we’d either have to err on the side of data safety (do not unmount if there are open files), or on the side of security (force unmount even if there are open files). We really don’t want to make that call on behalf of our users—with thousands of you out there, we’d surely make the wrong choice from someone’s point of view.

Thanks…Good Point.

Hi David!

We now have a release candidate version of Knox 1.5.1 available, which should fix the “_The Disk “name” needs to be ejected first before it is removed_” problem.

You can download it from:

Knox-1.5.1.dmg

Please try it and tell us if it fixes your problem. Thanks and sorry for the trouble this issue has caused!

with Knox 1.5.1 it works…

Thanks alot