Upon upgrading to 3.68, my previous problem of Chrome not starting every time is happening again (dots appear in yellow sandboxie icon, with only 1 chrome task listed, but it doesn't actually start), but only about half of the time (even though I still have */ISWSHEX.dll still blocked, as per our previous thread). The other half of the time, it starts fine. Also, I'm now getting this error about 1/4 of the time:

SBIE2203 Failed to communicate with Sandboxie Service: connect C0000022
SBIE2203 Failed to communicate with Sandboxie Service: RPCSS_SXS - chrome.exe [C0000080]
SBIE2334 Cannot load DLL file: SHLWAPI.dll
SBIE2304 Initialization failed for process chrome.exe

I figured I'd post this, in case it helps narrow down what's going on with my particular installation and the problems I've been having with chrome not starting properly. Just as a test, I downgraded to 3.66 again, and all worked fine (keeping */ISWSHEX.dll blocked)... but I went back up to 3.68 since I can get it to work about half the time, and maybe it will help us figure out what's happening. I know you couldn't replicate the problem, but just fyi, I'm currently using chrome version 18.0.1025.162.

Thats just a guess, but I recommend you go ahead and delete the folders of the older chrome versions under the Google app folder. secondly please run the resource access monitor and post the results here. also try deleting the sandbox. Finally make sure this is reproducible under a sandbox with default settings.

The first error message (which includes the detail "connect C0000022") suggests that you have some other security software that is blocking communications between chrome.exe and SbieSvc.exe.

The reason that switching between 3.66 and 3.68 makes a difference is probably because the "allow/deny" lists in your other security software all whitelist SbieSvc.exe from version 3.66, and the whitelisting doesn't apply to SbieSvc.exe from version 3.68.

Hi Tzuk,
I have Zone Alarm (free) 10.1.079.000 and Avast Free 7.0.1426. Could this still be related to the "race condition" you were thinking was happening previously on my system? Should I run the resource access monitor as DIGIT@L suggested? Sorry if I shouldn't have started a new thread, and perhaps should have posted this as an update to my last thread located at:

http://www.sandboxie.com/phpbb/viewtopic.php?t=12464&postdays=0&postorder=asc&start=0

Thanks,
~Mark

The part about the race condition was an attempt to explain why this only happens some of the time. Even if there is some race condition somewhere, I don't know what to suggest that you could try to find out what's causing this.

Perhaps you should post another Resource Access Monitor, let's see if any other DLLs are involved in this. It wouldn't explain why 3.66 works and 3.68 fails, but if we can find another DLL to block and fix the problem this way, then that would probably be a reasonable solution nonetheless.

Hi Tzuk,

Fairly good news: I decided to remove the blocked */ISWSHEX.dll from version 3.68 (which I needed to have blocked for 3.66 to work), and now it works most of the time! (probably almost 90% of the time now). Perhaps it's a combination of updates of sandboxie, avast, zone alarm, and perhaps even windows updates... but at least it works now more times than not. I'll keep using it this way for now, and upon your next update, I'll let you know if anything changes.

Thanks again for your help.
~Mark

Hi Tzuk,

I wanted to post an update with some great news! I think I finally figured out what was causing all my problems (posted in this thread and also my previous thread which I linked to above). I manually terminated programs one by one using the Windows Task Manager, and then ran Chrome sandboxed (over and over) to see if the problem would occur or not. I finally disabled one and upon doing so, chrome started up 100% of the time sandboxed! I did some research on the file, and it appears other people have had it cause problems with other software as well. Here are the details of the file, in case you want to test and see if you experience the same problems with it in combination with sandboxed versions of chrome.

Name: LVPrcSrv.exe
Description: Logitech LVPrcSrv Module
Locations: C:\Program Files\Common Files\LogiShrd\LVMVFM\LVPrcSrv.exe
Version: 11.5.0.1158
Product Name: Logitech QuickCam

Upon reading other forums where people had trouble with this file, I learned to disable it by running "services.msc" and then finding the service titled "Process Monitor", which I could disable from automatically starting at boot. Upon rebooting, LVPrcSrv.exe no longer appeared in the Windows Task Manager, and so far, Sandboxie is working 100% now with Chrome!!

This particular service comes with the software for my Logitech QuickCam, and apparently isn't vital. It just allows the QuickCam to do special effects... and even with it disabled, the cam will still work fine normally without using any effects.

Anyway, I wanted to let you know the great news that I got it working, and also to let you know so that you can troubleshoot why/how sandboxie is conflicting with this service.

Thanks again for your time and help.

~Mark

Thanks for the update and I'm glad to hear you finally found the real cause of the problem.

I don't have this webcam but I'll try to install the driver and see if I get this service installed, and if it causes similar problems on my end.

Version 3.69.03 adds a compatibility setting for the Logitech Process Monitor Service which should fix this problem.

Related topics:
http://www.sandboxie.com/phpbb/viewtopic.php?t=12907
http://www.sandboxie.com/phpbb/viewtopic.php?t=10678