Sandboxie and allowing direct access to entire Chrome profile

Sandboxie has a setting that, if checked, allows direct access to the entire Chrome profile folder.
Can anyone elaborate for me how that impacts everyday browsing with Chrome in SBIE?
Will some things not work, or perhaps not stick, because direct access to the profile is denied?
From reading the SBIE forum, it looks as though having the profile folder access enabled, a user opens himself up to things like FunMoods.
What are the effects of having this setting unchecked?
And also, on a similar note, what can anyone tell me about SBIE having (or not having) direct access to Chrome sync data?
Thanks.

 

Hi Page,
waiting for some expert to reply to your specific questions I have SB configured with only "Allow direct access to Google Chrome bookmarks". I have never experienced any problems with Chrome that would require less restrictions.

 

Hi Osaban,
I might reconfigure my settings to match yours, i.e. only access to Chrome bookmarks. Maybe I have had to much access allowed.

 

Thats what I would do if I was using Chrome.

In my opinion, Sandboxie works better. Sandboxing is not bypassed to allow changes to the profile folder while sandboxed.

That setting is for users that like to allow changes to the browser while running sandboxed. Thats not me. I don't want any changes to my browser while sandboxed, except saving bookmarks.

Bo

 

I only have bookmarks and cookies allowed. That way I can maintain my browser without having to launch it out of the sandbox. The only time I have to launch out of the sand box is to update the browser itself, and extensions/plugins.