can't delete contents

kwise · Post by **kwise** » Tue Sep 15, 2009 12:08 am

I can terminate all programs, and the system tray icon briefly has a red "x" showing it's deleting the sadbox, it doesn't delete the box. If i try delete contents, it says there are 114 files and 107 folder occupying 8 mg of space. I hit delete sandbox and i get this message:

Delete Sandbox DefaltBox: Could not move the sandbox out of the way
The object(file or folder) may be in use by another program.
Close any applications or windows that may prevent access.

System error code:

Access is denied/

(5)

I am also unable to delete the Defaultbox from windows explorer.

Any ideas?

dynarx · Post by **dynarx** » Tue Sep 15, 2009 12:38 am

Perhaps running Unlocker ( http://ccollomb.free.fr/unlocker/ ) on files remaining in the Sandbox container folder will help identify the processes involved.

Cheers,
D

paddyt · Post by **paddyt** » Tue Sep 15, 2009 7:08 am

kwise

for Windows 2000 but others may be similar

go to "Start" button
click "Run"
type regedt32 in box
click "OK"
look for box "HKEY_USERS on Local Machine"
you will see your Sandbox
highlight it
In registry Editor go ro Registry tab (top left)
choose "unload hive" from menu

then deleting sandbox should work ok

kwise · Post by **kwise** » Tue Sep 15, 2009 7:44 am

I have "hkey_local machine" and "hkey_users" My best guess is there's a folder under "hkey_users" called .DEFAULT. not defaultbox. could this be it. I'm concerned about really messing up my machine. I'm not experienced in registry editing, and know the wrong edit could really mess things up. What does unload hive do?

I also noticed there's two files in my Defaultbox called "reghive" that i can't delete, along with an empty folder farther down called Desktop. thanks for your help

Guest10 · Post by **Guest10** » Tue Sep 15, 2009 8:19 am

kwise wrote:I have "hkey_local machine" and "hkey_users" My best guess is there's a folder under "hkey_users" called .DEFAULT. not defaultbox. could this be it.

Definitely, NOT! Don't touch that one.
Forget Registry editing. That's something for Windows 2000, and you haven't said that you use that operating system.

If you haven't restarted Windows, since the failure to delete the sandbox, try that first. Then see if you can delete the DefaultBox folder.
Also, just using a sandbox folder again can sometimes break any locks that might be there.

If the folder still won't delete, install Unlocker from the link listed in a message above.
Then in Windows Explorer, expand the C:\Sandbox folder by clicking the + signs, until you can see the DefaultBox folder.
Don't left click on the DefaultBox folder, because selecting it in Windows Explorer can cause Explorer to create a lock on the folder.
Instead, right-click the DefaultBox folder and choose "Unlocker".
See if Unlocker reports that any locks were found, and if so, what program has a lock on the files.

kwise · Post by **kwise** » Tue Sep 15, 2009 8:24 am

Thanks. No, i'm running XP. What could be causing this? a virus?

Guest10 · Post by **Guest10** » Tue Sep 15, 2009 9:15 am

Sometimes a program can maintain a lock on a file in the sandbox, even though you have closed all sandboxed programs.
In the past, Foxit Reader was known to do that, with a .pdf file that was viewed in the browser.
Restarting Windows would be one method to break the locks on the file(s).

An anti-virus program can also maintain a lock on files. And it is running outside of the sandbox - so it isn't affected by closing sandboxed programs.

The Unlocker program is one way of trying to determine what might be responsible for locking files in a sandbox, using the procedure I described above. There's a more complex method to find locking programs, using Process Explorer, but Unlocker would be the method that I would use.
Unlocker can also break the locks, in some cases, but it might cause a lock-up of your computer and require a restart - depending on what has the file(s) locked.

What version of Sandboxie are you using?

paddyt · Post by **paddyt** » Tue Sep 15, 2009 1:56 pm

Sometimes when you're in this situation having run a browser sandboxed and then this lock up
just open the browser again sandboxed then close it and then the sandbox may delete as normal.

I don't think this has anything to do with being infected with a virus etc.

Regarding the regedit I described above the unload hive
you will see your sandbox in regedit32

HKEY_USERS on Local Machine

as "Sandbox_something_thenameofyoursandbox" folder

bo.elam · Post by **bo.elam** » Thu Sep 17, 2009 11:45 pm

This happened once to me and the solution was a restart and it was OK afterward.
Bo

kwise7764 · Post by **kwise7764** » Fri Sep 18, 2009 9:45 am

Thanks all, restart did the trick

Sandboxie Support

can't delete contents

can't delete contents

Who is online