http://www.appguardus.com/index.php/sup ... rd-supportAppGuard and Sandboxie. There is no conflict between Sandboxie and AppGuard 4.2. Depending on where Sandboxie is installed, you may need to fine-tune AppGuard’s policy as follows.
If Sandboxie is using a folder C:\Sandbox, add this as an “Exception” folder on the Guarded Apps Tab.
Okay, thanks....I just became aware of...Nix wrote:http://www.appguardus.com/index.php/sup ... rd-supportAppGuard and Sandboxie. There is no conflict between Sandboxie and AppGuard 4.2. Depending on where Sandboxie is installed, you may need to fine-tune AppGuard’s policy as follows.
If Sandboxie is using a folder C:\Sandbox, add this as an “Exception” folder on the Guarded Apps Tab.
Is there an AppGuard templates?! Ever since this is the only advice/workaround applied for SBIE/AGv4 that I know...
Sorry for the delay, only just seen this.Craig@Invincea wrote:@Hottrochottroc wrote:I upgraded from 5.06 to fix this issue:
"Fixes in 5.07.2
1) More improvements to application startup. SBIE2204 Cannot start sandboxed service RpcSs (-1) in Win 10 browser startup no longer occurs in our testing."
...However I received the error message yesterday. So it is not completely fixed (although it seems to occur less often).
I've also noticed that the "lag" that is mentioned in the post above this one is generally improved but occasionally reappears also.
If possible, we'd like you to remove 5.06 and revert back to 5.07.2. We're curious about something. Yes, that rcpss-1 can still exist, we want to see if changes after .2 may have made it worse (Win10). There is also a VERY good chance it's just hardware on your machine, as dependcy of hardware is also a factor.
bjm wrote:Okay, thanks....I just became aware of...Nix wrote:http://www.appguardus.com/index.php/sup ... rd-supportAppGuard and Sandboxie. There is no conflict between Sandboxie and AppGuard 4.2. Depending on where Sandboxie is installed, you may need to fine-tune AppGuard’s policy as follows.
If Sandboxie is using a folder C:\Sandbox, add this as an “Exception” folder on the Guarded Apps Tab.
Is there an AppGuard templates?! Ever since this is the only advice/workaround applied for SBIE/AGv4 that I know...
[Template_KnownConflicts]
Tmpl.Entry=Blue Ridge Networks AppGuard | {2C9B1E69-DD05-40F5-8378-056A117028F9}.
Probably been there all along. I'm not the brightest bulb in the box. Thanks
Yep, I can l install and get that GUID for AppGuard. Curt is right about the rest. I know the App Guard GUID isn't one of the ones we've added or modified in the recent months... but I can def check.Curt@invincea wrote:The check for AppGuard was in the templates.ini when Invincea acquired Sbie. The only thing that section does is cause the Known Conflicts dialog to be displayed to alert the user of potential problems. If it is not detecting AppGuard properly, then the GUID may be outdated. Craig can verify this.
Did you have success with Slack before? Installed outside of a sandbox and then "run as' sandboxed? I can understand if it didn't install directly into a sb. What OS are you using? What antivirus / anti-malware do you have installed? (If any)C3CvUJugtI3eMv wrote:Today detected that lastest sandboxie not work with Slack. Even not possible to install it inside sandbox. Constantly crash.
Yes i understand that i can do it like you recommended. But normally i use sandboxie to not allow crappy installers to create mess in windows registry and in file system. Because almost every modern application developer think that his application have to be in startup, almost every modern application try to create tonns of files in windows system directory, install strange libraries , install 3rd party programs which i not need etc . Due to such actions after year or two years Windows boot time dramatically increase. With sandboxie application uninstallation is really easy - just simple delete of sandbox. And all registry and files mess go away with deleted sandbox.Craig@Invincea wrote:I can confirm that running the .msi installer within SBIE causes a crash.
However, if you install Slack on your host, set up and log in (then exit)
Then, right click on Slack and run as sandboxed, it works just fine.
Win10x64 SBIE 5.07.7 Slack v. 1.2.7 32bit.
What extensions? What about just the core browser. Normally we test just the core browser with SBIE to make certain that works. Add ons and extensions can be problematic. So we focus on the core and work from there.Umbra wrote:Sbie makes Chrome some extensions to crash
- win10 x64
- Chrome beta v49 x64
- Sandboxie x64 v5.07.5
While a lot of programs can be installed in SBIE, some just won't. For varying reasons. Driver/services needed, etc. this is where a VM comes into play as it offers an actual Windows environment. You can use SBIE to contain the download, analyze the download, scan, poke it with a stick etc. then try to install it inside SBIE. If no luck, after analyzing or if you don't want to bloat your system, a VM is something that can work side by side with SBIE.C3CvUJugtI3eMv wrote:Yes i understand that i can do it like you recommended. But normally i use sandboxie to not allow crappy installers to create mess in windows registry and in file system. Because almost every modern application developer think that his application have to be in startup, almost every modern application try to create tonns of files in windows system directory, install strange libraries , install 3rd party programs which i not need etc . Due to such actions after year or two years Windows boot time dramatically increase. With sandboxie application uninstallation is really easy - just simple delete of sandbox. And all registry and files mess go away with deleted sandbox.Craig@Invincea wrote:I can confirm that running the .msi installer within SBIE causes a crash.
However, if you install Slack on your host, set up and log in (then exit)
Then, right click on Slack and run as sandboxed, it works just fine.
Win10x64 SBIE 5.07.7 Slack v. 1.2.7 32bit.
So almost every application i prefer to set in separate box.
is it possible to enable special debug mode or so for sandboxie to detect what exactly application try to do ?
PS . Also yesterday found one more issue with installer of Transmission-Qt Gui build for Windows. Installer not crash but show window "Installer initialization failed. The installer will now exit".
Look like that installers support little bit broken in sandboxie. I found small workaround : Windows installed on vmware with snapshot of original system. I install application in vmware and after it just copy folder where app installed to sandbox. After it i return Windows to previous snapshot for next app installation. But such solution work only for some programs.
in my case: Lastpass, NetcraftCraig@Invincea wrote:What extensions? What about just the core browser. Normally we test just the core browser with SBIE to make certain that works. Add ons and extensions can be problematic. So we focus on the core and work from there.Umbra wrote:Sbie makes Chrome some extensions to crash
- win10 x64
- Chrome beta v49 x64
- Sandboxie x64 v5.07.5
Users browsing this forum: No registered users and 1 guest
