Sandboxie-Plus v1.16.7

Okay...via 5.71.7...added chrome.exe as write-only.

Code:

C:\Program Files\Google\Chrome\Application\chrome.exe
C:\Users\Public\Desktop\Chrome.lnk

Run Sandboxed against Chrome desktop shortcut

Spoiler: related pic

--
Run Sandboxed

Spoiler: related pic

======================

Edit: on dust collector machine....Sandboxie+ 1.16.3 clean uninstall (config & boxes) -> Sandboxie+ 1.16.7 install = same missing Chrome Home button and corrupted extensions with DefaultBox & Chrome sbox.

two machines = same issue with Chrome

 

Sorry for not replying earlier. Power outage for a long time. Power got back just a few minutes ago.

 

You can create a regular shortcut for Sandboxie control with the code below, and move the shortcut to the taskbar, and run it from there.

"C:\Program Files\Sandboxie\SbieCtrl.exe" /open



Bo

 

Tinkering a bit, I added some settings from your ini to a chrome profile and Home Button + Extensions are there as always.

Spoiler

Code:

Template=LessConfidentialBox
Template=Chrome_Bookmarks_DirectAccess
SandboxieLogon=y
TemplateReject=Avast_Antivirus
TemplateReject=NortonInternetSecurity
TemplateReject=BitDefenderInternetSecurity
TemplateReject=AdGuard
TemplateReject=7zipShellEx
TemplateReject=Edge_Fix
TemplateReject=OfficeClickToRun
TemplateReject=OfficeLicensing
TemplateReject=SynapticsTouchPad
TemplateReject=WindowsLive
TemplateReject=WindowsRasMan
MarkOfTheWebBox=Chrome
ConfidentialBox=y
CoverBoxedWindows=y
EditAdminOnly=y

Image your system drive as a backup before attempting the following:
Did you empty/delete the actual [Chrome] sandbox?
Did you try a new chrome profile
Did you try a new ini file?

 

@Mr.X
I've clean installed Sandboxie+ on dust collector machine. Odd behavior remains.
Created new test Chrome profile on dust collector machine...with one change...enabled Home button.
Call [Chrome] to find missing Home button with my profile and new test profile.
Home button enabled with cycle Chrome and seeing Home button (my profile and test profile) is missing/disabled with [Chrome].
Reproduced test profile odd behavior on daily rider machine.
Thanks for tinkering

 

@bo elam
I need on occasion to reference SbieCtrl.
I'd forgotten (remember wrong) SbieCtrl pinned to taskbar does not open from taskbar.
Yes, I'd forgotten SbieCtrl shortcut + pin to taskbar...needs /open.
Thanks

 

@Mr.X
as tinkering: Installed 1.16.7 (defaults) on friends machine.
Confirm Chrome up-to-date and Home button enabled.
Create Chrome sbox (defaults)
Create Chrome sbox shortcut
Call [Chrome]...expect to see Home button
Home button missing + Extensions Error
Note: friends machine never had Sandboxie...friends machine runs different Chrome Settings & Extensions.
I've reproduced "odd behavior" on three machines
fwiw ~ friends machine ini

Spoiler: ini

#
# Sandboxie configuration file
#

[GlobalSettings]

[UserSettings_0CDE0223]
SbieCtrl_AutoStartAgent=SandMan.exe -autorun
BoxGrouping=DefaultBox

[DefaultBox]
Enabled=y
BlockNetworkFiles=y
RecoverFolder=%Desktop%
RecoverFolder=%Personal%
RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}%
BorderColor=#00FFFF,ttl
Template=AutoRecoverIgnore
Template=LingerPrograms
Template=BlockPorts
Template=qWave
Template=FileCopy
Template=SkipHook
Template=OpenBluetooth
ConfigLevel=10

=======================
Edit: more tinkering: on dust collector machine
Rename Chrome UserData folder = UserDataOLD
Call Chrome creates new UserData folder
Change one Chrome Setting = enable Home button
Cycle Chrome to confirm Home button enabled
Clean install 1.16.7 (defaults)
Call Chrome to DefaultBox = Home button missing
I've reproduced "odd behavior".

Spoiler: ini

#
# Sandboxie configuration file
#

[GlobalSettings]
MarkOfTheWebBox=DefaultBox
Template=7zipShellEx
Template=Edge_Fix
Template=NotepadPlusPlus_fix
Template=OfficeLicensing
Template=WindowsLive
Template=WindowsRasMan

[UserSettings_04D4013A]
SbieCtrl_AutoStartAgent=SandMan.exe -autorun
BoxGrouping=DefaultBox
SbieCtrl_EnableAutoStart=y

[DefaultBox]
Enabled=y
BlockNetworkFiles=y
RecoverFolder=%Desktop%
RecoverFolder=%Personal%
RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}%
BorderColor=#00FFFF,ttl
Template=AutoRecoverIgnore
Template=LingerPrograms
Template=BlockPorts
Template=qWave
Template=FileCopy
Template=SkipHook
Template=OpenBluetooth
ConfigLevel=10

=====================
Edit: more tinkering: on dust collector machine
Uninstall Chrome + scour remnants
Restart
Chrome install
Change one Chrome Setting = enable Home button
Cycle Chrome to confirm Home button enabled
Create Chrome sbox (defaults)
Create Chrome sbox shortcut
Call [Chrome] = Home button missing
I've reproduced "odd behavior".

Spoiler: ini

#
# Sandboxie configuration file
#

[GlobalSettings]
MarkOfTheWebBox=DefaultBox
Template=7zipShellEx
Template=WindowsRasMan
Template=NotepadPlusPlus_fix
Template=WindowsLive
Template=Edge_Fix
Template=OfficeLicensing
Template=7zipShellEx
Template=Edge_Fix
Template=NotepadPlusPlus_fix
Template=OfficeLicensing
Template=WindowsLive
Template=WindowsRasMan

[UserSettings_04D4013A]
SbieCtrl_AutoStartAgent=SandMan.exe -autorun
SbieCtrl_EnableAutoStart=y
SbieCtrl_UserName=bjm
SbieCtrl_NextUpdateCheck=1764526918
SbieCtrl_EnableLogonStart=n
SbieCtrl_AddDesktopIcon=n
SbieCtrl_AddQuickLaunchIcon=n
SbieCtrl_AddContextMenu=y
SbieCtrl_AddSendToMenu=n
SbieCtrl_WindowCoords=200,150,970,348
SbieCtrl_ActiveView=40021
SbieCtrl_BoxExpandedView=Chrome
BoxGrouping=DefaultBox,Chrome

[DefaultBox]
Enabled=y
BlockNetworkFiles=y
RecoverFolder=%Desktop%
RecoverFolder=%Personal%
RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}%
BorderColor=#00FFFF,ttl
Template=AutoRecoverIgnore
Template=LingerPrograms
Template=BlockPorts
Template=qWave
Template=FileCopy
Template=SkipHook
Template=OpenBluetooth
ConfigLevel=10

[Chrome]
Enabled=y
ConfigLevel=10
AutoRecover=y
BlockNetworkFiles=y
Template=OpenSmartCard
Template=OpenBluetooth
Template=SkipHook
Template=FileCopy
Template=qWave
Template=BlockPorts
Template=LingerPrograms
Template=AutoRecoverIgnore
RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}%
RecoverFolder=%Personal%
RecoverFolder=%Desktop%
BorderColor=#00FFFF,ttl,6,192

 

@bjm_ as far as I see it chrome added some mechanism to detect changed to settings, and it seams when you share a profile between the host and the box this gets triggered ans options reset.
Ensure sandboxed chrome only uses an own exclusive profile
WriteFilePath=%Local AppData%\Google\Chrome\
this line will prevent the boxed chrome from reading any unboxed profile files.
this should resolve the issue and prevent chrome from tinging the settings were tempered with.

 

David, but he's used an orange and yellow boxes unsuccessfully. Orange and yellow boxes don't need that line for chrome in my experience. Or perhaps I'm missing something.

 

During my tests when the profile files was shared between unsandboxed and sandboxed chrome it did not like when settings were changed on host

Well yes you get a new profile, you can manually copy the old profile into the sandbox if you dont waht to set it up from scratsch.

 

Hello @DavidXanatos
So, after adding

Code:

WriteFilePath=%Local AppData%\Google\Chrome\

I need to setup my Chrome profile again from scratch...on host?
Or, each empty sbox call...I need to manually copy old profile into empty sbox?
Chrome profile is setup on host. As far as I'm aware...calling my Chrome sbox copies necessary items from host into my Chrome sbox.
Why am I setting up Chrome profile on host from scratch?
Why am I manually copying profile to sbox?
Will each Chrome empty sbox call...prompts setup Chrome profile...again??
My apologies for being slow to grasp Chrome sbox recent "odd behavior" reproduced on three machines.

 

Are you saying when I'm browsing in my Chrome sbox. I should not open Chrome unsandboxed and change a setting?
Hmm, I may on occasion open unsandboxed Chrome to check for updates while I'm browsing in my Chrome sbox.
When I've observed/reproduced odd behavior. I'm only (as far as I know) in my Chrome sbox.
--
Okay...my six sbox's are empty. Task Manager does not report Chrome processes.
I'll call [Chrome] -> Home button is missing.
---
Yesterday, I clean installed Chrome & Sboxie and setup [Chrome] sbox. I called unsandboxed Chrome to enable Home button. I close Chrome. I call [Chrome] -> Home button is missing.

 

Correct 2 independant instances of chrome running simultaniusly should not share the same profile files

 

the sandman message can happen when you terminate sandman early on startup while itrs checking compatybility tempaltes based on installed updates.

the second message is from chrome and a product of when it gets confised about the profile files

 

Then I'm all head scratch. Is this requirement unique to Chrome? Is this Chrome requirement recent? I do not recall an issue running unsandboxed browser and sandboxed browser at the same time. I'm running Edge unsbox'd & Edge sbox'd now.