Discussion in 'sandboxing & virtualization' started by ad18, Dec 16, 2013.
There is free version of ReHIPS, with some limitations though.
Does it give less problems? But to me it looks too complex, so I have no interest. But yes, seems like the newest version of Sandboxie has introduced problems with Chrome and Vivaldi. Chrome can't launch and close correctly, and Vivaldi can't close correctly.
Have you entered Vivaldi.exe under Lingering Programs?
Worked for me.
I also have it under Leader Programs.
Less issues? yes since it uses Windows' tightened user-profiles and other Windows mechanisms so less breakage of apps.
Complex? yes and no. Yes at first, you have to learn how to use it (if you can handle an HIPS, you shouldn't have much problems. ). No, because with time, it becomes relatively easy to use.
Of course, it may have some issues with some softs, nothing is perfect, but the devs work hard to fix them for the next version, they always listen reports and mention if a fix will be applied or not.
Yes but it doesn't work. I'm guessing it's because I use quite a lot of tabs, and Vivaldi often stays in memory for hours. Older versions of Sandboxie didn't have any problems with closing Vivaldi, it took only about 30 seconds or so.
Yes, I forgot it works a bit different. But I prefer to use virtualization.
Is Lingering Programs even a consideration for latest Windows 10, I wonder (not older OS)? I'm at the point where it helps to have another product mentioned. I'm saying this b/c it's the first time I have multiple issues, including hardware, and can't make Sbie work with a certain browser. We'll see about upcoming versions, I guess. But I want something to substitute for HitmanPro.Alert and Sbie has been just about perfect in that respect.
Rasheed, Vivaldi is officially a supported browser. You should make a report in Problems at the Sandboxie forum.
Hi plat1098, sure, Lingering programs is still a valid Sandbox setting.
I dony know, but I think this thread ...is getting hijacked by the MT boys .
1 Not all the boisterous participants in the recent discussion are current members of MT.
2 Attempted hijack, yes. Aborted by pilot.
3 Both Sandboxie and ReHIPS do sandboxing of selected applications, albeit in different ways. But let's not talk about ReHIPS in this thread.
Hi shumu26, I thought that was funny.
Sandboxie RC 5.28 has been released.
Changes in 5.28
No code changes, just testing a Release Candidate prior to releasing.
I read earlier this thread at the Sandboxie forum, is about the Chrome issue between Sandboxie and Chrome 72. This is a FYI type of post for people who don't go to the Sandboxie forum, at this moment the workaround is to disable Hardware acceleration. That seems to fix the issue for some users. The developers need your help, as of yet, they havent been able to reproduce the problem. You guys having the issue should post in the thread below and give as much information that you can to help developers replicate the problem. Fixing the problem is easy, the hard part is reproducing and finding whats causing the problem.
Thank you for the info. It doesn't sound encouraging that the issue cannot, as of now, be reproduced. Personally, I had other hardware issues in addition to the SBIE2101 so I ditched Chrome altogether. All I can say is that the issue popped up seemingly randomly after Chrome updated, making it probably even more difficult to pinpoint the source. Disabling hardware acceleration, for me with a NVIDIA processor, is at best an extremely temporary situation. I find Sandboxie worthwhile so it's no big deal for me to switch browsers.
I don't know whether it has been happening after the latest Win 10 home update (vers. 1809 build 17763.316) or it has something to do with Chrome (latest 64 bit), but the sandbox is not automatically deleted when closing Chrome, I have to use "File/Terminate all programs" to delete the sandbox. I have 'Chrome.exe and Chrome programs' listed in 'Lingering programs'. SB version: 5.28
FWIW ~ I have chrome.exe as Lingering and Leader Programs.
Hey thanks! By adding Chrome.exe to 'Leader Programs' solved the problem...
Sandboxie v5.28 Released (February 15, 2019)
Thank you mood--an anticipated release. Reinstalled and configured Chrome, unfortunately still getting the Sbie2101 error upon opening Chrome. Can't link anything specific to it, it seems to hitch a little when opening, then the error occurs but not every time you open the browser. The changelog didn't note anything specific to Chrome anyway. Not disabling Hardware Acceleration but has anyone found this to be successful w/this error?
Spoiler: sbie v. 28.0.0 error 2101 w/latest Chrome
I dont use Chrome so I cant confirm the workaound works but it probably does. Is just a temporary workaround that you can revert after the fix is released.
Read this 2 posts from users using the workaround successfully. Guest10 writes about another workaround, that tested successfully for him, perhaps you want to try that one instead of disabling Hardware acceleration.
i started chromium v74 (as a portable) in sandboxie (still v5.27beta) on win81 x86, no issues. but i need to test on win10 x64 later to verify. could be a x64 issue only!?
The reason why I didn't is because I figured that if they fix the problem with Chrome, the problem with Vivaldi will also be fixed. But I will upgrade to the new version, let's see.
Rasheed did you try having vivaldi.exe added to both lingering and leader programs.
Works for me.
Good suggestion, but I'm afraid this isn't an option for me, because I run both Opera 12 and Vivaldi in the same sandbox. So this would also terminate Opera 12. But like I said before, it must be some "bug" in Sandboxie, I'm sure they will fix it.
Separate names with a comma.