Have you tried using the logger to see if something is blocked? I'm using Ublock with dynamic filtering enabled and I can enter my email just fine. what filters do you have enabled?
I have tried completely disabling UBO but it made no difference. I installed Slimjet and it works fine so I will probably use that for a while until I figure out what the problem is. My problem appears to be unique in that I cannot enter any characters into the Hotmail login screen and as soon as I click on the screen the browser locks up completely.
Chinook9, I would try testing with a new Firefox profile. Create one and test first without any extensions or SBIE. If all is well, then try running Firefox sandboxed, and later add NoScript, UBO, etc. Bo
Thank you for the recommendation Bo. I will go ahead and try it to see if it works and if I like it better than Slimjet which seems to be working OK at this time.
Hi K, everybody who has used Sandboxie for a long time has seen that message at one point or another. The quick fix is to reboot the computer, afterward, you ll be able to delete contents. Usually you get this type of message when you close a sandboxed program, and sandbox content cant be deleted because your antivirus has a lock on files inside the sandbox. The lock happens when the AV scans the files inside the sandbox as Sandboxie tries to delete contents. So, the reboot frees the lock on files, and this allows contents to be deleted afterward. If you start getting this type of message often (like everyday, week), then perhaps you ll want to switch AV. If it happens rarely, and I think this is your case, you can ignore this event and don't let it bother you because it is nothing important to worry about. Bo
In some cases that would work, but excluding Sandboxie or sandbox contents from being scanned is probably something you dont want to do if you are using an AV You want the AV to scan it. Bo.
How would one exclude Sandboxie with ESET? The above error has happened again for me. (I did recently switch from Webroot to ESET.)
There was a discussion of some conflict between ESET and Sandboxie. https://forum.eset.com/topic/20056-eset-issue-with-sandboxie-persistent-holding-of-registry-keys/ Perhaps your issue is also related to it.
Thank you. From that page: Believe I know what might be the "culprit" here. Eset recently implemented "Deep Behavior Inspection" in the HIPS. For anyone having this issue with Sandboxie, do the following: 1. Open the Eset GUI and navigate to the HIPS section. 2. Verify that a Deep Behavior Inspection section exists there. If so, add exceptions for all of Sandboxie's executables there. -EDIT- Or alternatively, just whitelist Sandboxie's entire directory using the "\*.*" notation. Hopefully, this will resolve the registry access issues with Sandboxie.
Windows live login with sandboxie just takes a while, let it load. I use firefox, as far as I'm aware this issue doesn't happen with chrome, but I don't like chrome.
Pretty sure that means that something in the sandbox is still running and it couldn't be terminated for whatever reason. The solution is to soft reboot and then make another attempt to clear it. if it still doesn't work after that, then it's probably a good idea to do some malware scans.
Any more news on this feature? I specifically use Sandboxie with my browsers for its ability to automatically delete any data I accumulated during a browsing session leaving upon exit keep them clean.
We don't know yet when the next version of ReHIPS will be released, but it will offer major feature improvements. You can clean up isolated environments even with the current version, it's not just a one-click operation, that's all. For more details, ask @umbra or get on the ReHIPS forum.
