How long before Sandboxie is stable in Windows 10????????

Hi jps99, Sandboxie is stable in W10 1903. What Sandboxie version are you using? Is it 5.30 or beta 5.31.2?

Version 5.30 works only "partially" in W10 1903, if this is the version you are using, you should upgrade to Sandboxie beta 5.31.2 as it is the version that's up to date with W10 1903 build 18362.207.

You mention that you are getting RegHives errors. Are you getting Sandboxie messages, if you are, what are they? Are you using ESET? I ask about ESET, because after a recent ESET NOD update, other ESET/Sandboxie users are having an issue when Sandboxie attempts to automatically delete contents of the sandbox. This issue occurs due to ESET locking files and/or RegHives in the sandbox after the user closes sandboxed programs. The lock/hold doesn't allow SBIE to delete contents, so a reboot is needed to free the lock. After rebooting, you should be able to easily delete contents mannually. Anyway, tell me details. But also, remember to update SBIE to 5.31.2.

Bo

Until Bo answers, please note that Windows 10 1903 includes the Sandbox feature which is completely different from Sandboxie. The Sandbox feature in 1903 not working has no connection with Sandboxie. Sandboxie beta 5.31.2 is working as expected on my system (although I don't use any third party anti-virus- only the built in defender).

[QUOTE=jps99;1667078]Thank you for responding Mr. Elam
Windows 10 pro 64-bit 1903 build 18362.175
I have upgraded Sandboxie to 5.30. I'm kind of afraid to use a beta version.

ERROR message from Sandboxie:
Sandboxie start Delete Sandboxie DefaultBox.
Could not move the sandbox folder out of the way. The object (file or folder)
may be in use by another program. Close any application or windows that may
prevent the access. System Error Code: Access is denied. (5)
End ERROR message.

Another confusing issue is I have just found out that Microsoft has included
Sandboxie in Windows 10. Where does that leave me???????

I am using ESET

I found this disturbing answer to a post I made on the Masm32 Forum.
Please read it and kindly give me your opinion.
masm32.com/board
Go to the "orphange" forum
Look for my post titled: Windows 10 1903

I will wait to read your response before updating Sandboxie beta to 5.31.2.

jps99 said:

I kind of afraid to use a beta version.

jps99, historically, Sandboxie betas are as stable as the stable version itself. Thats how it has always been with Sandboxie. I know the label "Beta" sort of means not ready or not ready for mass distribution, but in the particular case of Sandboxie, that's not so. Besides, it always takes a long time in between releases of stable versions, so, if you are in W10, it behooves you to use the latest released beta as it is the Sandboxie version that keeps compatibility with the most recent updates released by Microsoft for W10. Dont be afraid, jp.

jps99 said:

ERROR message from Sandboxie:
Sandboxie start Delete Sandboxie DefaultBox.
Could not move the sandbox folder out of the way. The object (file or folder)
may be in use by another program. Close any application or windows that may
prevent the access. System Error Code: Access is denied. (5)
End ERROR message.

Another confusing issue is I have just found out that Microsoft has included
Sandboxie in Windows 10. Where does that leave me???????

I am using ESET

When I read your opening post, I figured you were using ESET. ESET and Sandboxie have always worked well together but right now there is a conflict, this conflict is whats causing the sandbox dont delete message you are seeing. It seems a recent update by ESET created the conflict. I explained what the issue is about in my first reply to you.

Right now your solutions are as follow:

Short term. When you close the sandboxed program, if you get the sandbox dont delete message from Sandboxie, reboot the computer, doing so frees the lock ESET has on files within the sandbox folder, after rebooting, you ll be able to delete contents manually.

You could also temporarily switch to Windows defender. With WD, you wont get the SBIE message and wont have an issue. WD and Sandboxie have traditionally gotten along very well. You could do this and wait for an update by ESET that would solve the issue. Other users who use Sandboxie and ESET are experiencing same issue, so, is likely a fix will be released soon in an update by ESET.

Long term solution. If ESET doesn't release an update that fixes the problem, switch to WD. Windows defender and Sandboxie have gotten along very well for a long time. The only time SBIE and WD conflicted was when WD was first released about 9 years ago.

Updating to Sandboxie beta 5.31.2 wont fix the issue between ESET and Sandboxie but you should still update to 5.31.2. With 5.30, the version you are using now, you cant recover files that you download out of the sandbox. So, you should update.

jps99 said:

Another confusing issue is I have just found out that Microsoft has included
Sandboxie in Windows 10. Where does that leave me???????

........

I found this disturbing answer to a post I made on the Masm32 Forum.
Please read it and give me your opinion.
masm32.com/board
Go to the "orphange" forum
Look for my post titled: Windows 10 1903

I will wait to read your response before updating Sandboxie beta to 5.31.2

Right now, the Windows sandbox is a baby, I doubt any long time Sandboxie user would even think of switching to the Windows sandbox. I haven't, and don't have any curiosity to even check it out. Besides that, the Windows sandbox has a lot of problems, this is understandable as it was just released but in the end, there's no reason to stop using a mature program like SBIE for something that doesn't work well and dont have the features, settings, usability and flexibility that Sandboxie has.

I read the thread you mentioned, I think that guy was talking about the Windows sandbox.

Bo

Thank you very much for your time and expertise Mr. Elam.
I will follow your instructions.

jps99 said:

Thank you very much....

You are welcome, jps99, I am glad to help if I can.

You might like to follow the threads I am linking below, one is at ESET forum, and the other one is at Wilders. The matter that's being discussed is the issue that's affecting you and other Sandboxie users who are also using ESET.

ESET issue with Sandboxie - Persistent holding of registry keys - ESET NOD32 Antivirus - ESET Security Forum

Sandboxie Acquired by Invincea | Page 212 | Wilders Security Forums

I just thought of something that you might like to try. I know ESET has some sort of HIPS, perhaps you like disabling that portion of the program, to see what happens. Also, if it has (probably does), some sort of web guard, browser guard, disable it, to see if Sandboxie is able to delete contents successfully after doing this changes. Try also creating an exclusion to the Sandbox folder in C drive. I am not talking about the Sandboxie folder in Program files but the Sandbox folder in C drive. This are things you can try, try one at a time.

Tell me what program or programs you are running sandboxed that trigger the Sandboxie message after you close the program. Is it Chrome, Firefox, or what? Do you run under Sandboxies supervision anything else, other than your browser? If you do, is sandbox content deleting successfully when you close this programs that are not browsers?

Bo

I went looking for your post on ESET SS. Did not find it but found some
disturbing remarks about the Life of Sandboxie. Many there feel Sandboxies
days are numbered. God I hope not!!
The internet is a very dangerous place and Sandboxie is desperately needed
or another program as good as Sandboxie.

JPS99, I didnt post at the ESET forum, I dont use ESET. But I posted about this ESET/Sandboxie issue at Wilders, in the thread I linked. You can read those posts, I wrote there basically the same that I told you. Regarding the future of Sandboxie, all I am going to tell you is that it was a bad day for Sandboxie and for us users the day Sandboxie fell in the hands of Sophos.

jps99 said:

The internet is a very dangerous place and Sandboxie is desperately needed
or another program as good as Sandboxie.

Unfortunately, there is nothing like Sandboxie.

Bo