[SBIE2101]Chrome won't work
Posted: Sun Oct 15, 2017 6:39 pm
Hi!
First my specs:
Windows 10 Pro N
Sandboxie Version 5.20 (64-Bit)
Chrome Version 61.0.3163.100 (64-Bit)
AV Software? Yes. Sure. 360 Internet Security as you will see.
I've been using Sandboxie for many years now and I'm always happy to run certain programs in my main system without having to use VMs, but also without cluttering up my system. So thank you for that! I'm really happy with your software!
Seemingly since I've installed the Windows Update
Windows 10 Insider Preview 16299.15 (rs3_release)
yesterday I've had Problems with my Sandbox.
I've now uninstalled the Windows Insider thing and reinstalled Sandboxie, trying to fix this.
It did not work though. I'm now kind of concerned about my system.
The Sandboxed Browser did at first start but give this errormsg:
The Browser than starts, but is not sandboxed!
The Window is in that border, that signalises it's a sandboxed process. It's also listed in the sandboxed processes and the little dots in the sandboxie Control appear.
BUT Changes made in that browser directly effect my browser in the real system. It's not sandboxed.
The errormassage I have in the title was the one I had when I made the topic, the one in the Code is another code, that appeared when I tried reproducing the Problem.
I can't even terminate the programs in the Sandbox right now! At least not using Sandboxie Control.
I assume I'll be able to get rid of this problem by uninstalling the Browser Plugin and maybe some other tweaks.
The fact that what ever Program, Windows Update, or Browser Plugin may have caused this somehow seems to have broken the very purpose of Sandboxie frightens me though.
I logged out the Chrome Profile in the Sandbox and when using my non-sandboxed Browser I was logged out. That happened multiple times until I realised the things I do in the Sandbox actually were the cause that influenced my non-sandboxed Browser. This never happened to me before.
First my specs:
Windows 10 Pro N
Sandboxie Version 5.20 (64-Bit)
Chrome Version 61.0.3163.100 (64-Bit)
AV Software? Yes. Sure. 360 Internet Security as you will see.
I've been using Sandboxie for many years now and I'm always happy to run certain programs in my main system without having to use VMs, but also without cluttering up my system. So thank you for that! I'm really happy with your software!
Seemingly since I've installed the Windows Update
Windows 10 Insider Preview 16299.15 (rs3_release)
yesterday I've had Problems with my Sandbox.
I've now uninstalled the Windows Insider thing and reinstalled Sandboxie, trying to fix this.
It did not work though. I'm now kind of concerned about my system.
The Sandboxed Browser did at first start but give this errormsg:
Code: Select all
SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000001 - chrome.exe [FF000000]
SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000001 - chrome.exe [FF000000]
SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000001 - chrome.exe [FF000000]
SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000001 - chrome.exe [FF000000]
SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000001 - chrome.exe [FF000000]
SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000001 - chrome.exe [FF000000]
SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000001 - chrome.exe [FF000000]
SBIE2335 Initialization failed for process 360webshield.exe [33 / 0]
The Window is in that border, that signalises it's a sandboxed process. It's also listed in the sandboxed processes and the little dots in the sandboxie Control appear.
BUT Changes made in that browser directly effect my browser in the real system. It's not sandboxed.
The errormassage I have in the title was the one I had when I made the topic, the one in the Code is another code, that appeared when I tried reproducing the Problem.
I can't even terminate the programs in the Sandbox right now! At least not using Sandboxie Control.
I assume I'll be able to get rid of this problem by uninstalling the Browser Plugin and maybe some other tweaks.
The fact that what ever Program, Windows Update, or Browser Plugin may have caused this somehow seems to have broken the very purpose of Sandboxie frightens me though.
I logged out the Chrome Profile in the Sandbox and when using my non-sandboxed Browser I was logged out. That happened multiple times until I realised the things I do in the Sandbox actually were the cause that influenced my non-sandboxed Browser. This never happened to me before.