_Delete_Sandbox_01CD822B8691803B

If it's not about a problem in the program
Post Reply
ADayOlder

_Delete_Sandbox_01CD822B8691803B

Post by ADayOlder » Sat Aug 25, 2012 11:42 am

Hi,

These don't appear to be causing any problems but I have noticed on a number of occasions on different PCs and users that folders are generated named something like in the title with a different code each time alongside the sandboxes.

There is only one of each sandbox generated and appears to be quite random.

Very often they are 0KB and can usually be deleted (Have to be because they just sit there otherwise). Sometimes though they do have data in them and I have one user account where they cannot be deleted even as an administrator, I have not tried from safe mode.

Why are they generated?

Why are they not deleted especially when some of the original sandboxes are set to auto-delete?

Why when a sandbox is set to delete is this folder generated, doesn't this then leave the data I wanted deleted on my PC and unless I was to specifically look I would not know they were there?

Regards

ADayOlder

Guest10
Posts: 5127
Joined: Sun Apr 27, 2008 5:24 pm
Location: Ohio, USA

Post by Guest10 » Sat Aug 25, 2012 12:49 pm

Sandboxes are renamed before the command is sent to delete their contents.
This makes the sandbox by that name available for re-use almost immediately, while the previous contents of that sandbox are being deleted.

If some process still has a lock on something in the sandbox that's being deleted, then the sandbox cannot be completely deleted, and leaves those file(s) and the renamed sandbox folder behind.
If Delete Contents was run manually, then a message will be generated that the sandbox contents could not be deleted.
If auto-delete is used for the sandbox, then Delete Contents will fail quietly - without notice.

Regardless of which method of Delete Contents is used, each time that a sandbox is deleted Sandboxie Control looks to see if there are any sandboxes that previously failed to delete, and it tries again. Hopefully, by that time the lock that was on a file has been removed.
In rare cases people have had to reboot their computer before a renamed sandbox could be deleted.

http://www.sandboxie.com/index.php?Star ... ine#delete
Paul
Win 10 Home 64-bit (w/admin rights) - Zone Alarm Pro Firewall, MalwareBytes Premium A/V, Firefox, Thunderbird
Sandboxie user since March 2007

ADayOlder

Thanks for the Prompt Reply

Post by ADayOlder » Sat Aug 25, 2012 2:26 pm

Hi,

Thank you for the comprehensive reply.

I have just tested this on another users login that had an outstanding _Delete folder. This did indeed auto delete 'Stage 2' this time along with the current sandbox.

This still leaves the folders I have on a different PC that for some reason cannot be accessed or deleted. Very unusual. Possibly some oddity of the OS. I will delete them from within Linux and see if this occurs again.

Sorry, XP Pro by the way.

Regards

ADayOlder

Guest10
Posts: 5127
Joined: Sun Apr 27, 2008 5:24 pm
Location: Ohio, USA

Post by Guest10 » Sat Aug 25, 2012 2:47 pm

One other thing I forgot to mention.
If you are using the SDelete program to secure delete sandboxes, be advised that version 1.6 doesn't work correctly.
It will leave behind an undeleted folder. SDelete v1.51 works correctly.
Paul
Win 10 Home 64-bit (w/admin rights) - Zone Alarm Pro Firewall, MalwareBytes Premium A/V, Firefox, Thunderbird
Sandboxie user since March 2007

Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests