Sandboxie Support

I updated to the newest release of SDelete (1.6), which I use for one sandbox.
The program does not delete the sandbox folder, and leaves behind the:
__Delete_Boxname_xxxxxxxxxxxxxxxx
folder.
The folder is not locked in any way, and can be deleted with Windows Explorer.

Anyway, that's what's happening for me.
I'm looking for the previous version on my DVD-R's, since most sites link to SysInternals for the program.

[Edit] Working fine again, with SDelete v1.51

Thanks for the advice about not updating sdelete.exe.
I've been using v1.51 for along time without issues.

Confirmed.

Also same problem with this:

@echo off
:: This uses SDelete to securely erase sandbox.
:: It assumes the SDelete.exe program is located in C:\SDelete.
cls
c:\SDelete\sdelete.exe -p 1 -s "C:\Sandbox\xxxxx\DefaultBox"
echo.
echo.
echo Press any key to close this window . . .
pause > nul
exit

Ugly workaround... run the sdelete command twice. It will delete the empty folder on the second pass.

Is there any particular reason why SDelete v 1.6 does not remove the folder??

Is the an automated way to runSDelete (V 1.6) twice as wraithdu suggests??

Many thanks.

Just stay away from v1.6
There are several bug reports at the SysInternals forum that may result in another update to the program:
http://forum.sysinternals.com/miscellan ... 5286805556

And, Sandboxie cannot make use of any workaround, such as running the delete command twice.
The first time Control runs SDelete, the sandbox is renamed, prior to deleting the files and folders.
Trying to run Delete Contents a second time will fail, with the message that the sandbox is empty, because it was renamed and now the sandbox with that name no longer exists.

I did wonder why these "__Delete_(Sandbox)_xxxxxx" folders were accumulating.
Typically, they still contained a file or sub-folder that hadn't been deleted, so they were not completely empty.

I had 3 or 4 of them, since another one would be added each time I deleted contents.
I could easily delete them using Windows Explorer, and yet Control wasn't deleting them.

Guest10 wrote:Just stay away from v1.6

Man, I'm glad I read this thread!
I'm currently using 1.51 and don't want to update now!

I have tried SDelete 1.6 and its recursive deletion switch "-s or -r" does not work properly. After running it on a folder with some subfolders there are a bunch of (sub)folders left behind which are not deleted. Only through repeatedly running "sdelete -s" multiple times can we hope that the top-level folder be finally deleted. In other words, the recursive deletion is not reliable at all.

That said, when used in Sandboxie, stay away from SDelete v1.6 and use v1.51.

Hi,

I wish I have read this post before upgrading to Sdelete V 1.6; But yes it's a mess after upgrading Sdelete.
As Guest10 says, I also have same problem ' __Delete_Boxname_xxxxxxxxxxxxxxxx ' and I have to delete all contains twice.

Is there any solution on that?
Is anyone know where to find Sdelete V 1.51......b'cause I search every well known site for getting it, but no chance.
or tzuk (or any other respected member) plz will u upload Sdelete V 1.51 for download for us ? (I known it's too harsh, but there is no other choice)

Thanks !

I have sent you a Private Message with a link to a .zip file that contains "sdelete.exe" (v1.51)

The .zip file also contains two .txt files that I made for myself.
You can read them if you like, but you only need the "sdelete.exe" file that is in the .zip.

Guest10 wrote:I have sent you a Private Message with a link to a .zip file that contains "sdelete.exe" (v1.51)

Thanks Guest10 !

zRcHo0y wrote:

Code: Select all

http://web.archive.org/web/20110624072636/http://download.sysinternals.com/Files/SDelete.zip

SHA-1: 187beea1ed4738cd3af648b6ee51d631fc059a71

I verified that the SHA-1 checksum for the file at this link matches the checksum for my copy of SDelete.exe v1.51

Guest10 wrote:I updated to the newest release of SDelete (1.6), which I use for one sandbox.
The program does not delete the sandbox folder, and leaves behind the:
__Delete_Boxname_xxxxxxxxxxxxxxxx
folder.
The folder is not locked in any way, and can be deleted with Windows Explorer.

Anyway, that's what's happening for me.
I'm looking for the previous version on my DVD-R's, since most sites link to SysInternals for the program.

[Edit] Working fine again, with SDelete v1.51

EEeee! Thanks for the advice about not updating .exes

Great. Thanks for help