Appguard discounted price

[aladdin]

Originally Posted by pegr

Hi Aladdin,

Welcome to the AppGuard club.

Thanks for the link. If I've understood the issue correctly, it affects forced applications. I don't use forced applications, which is why I've never encountered the problem reported in the Sandboxie forum. The reason there is a problem with Sandboxie forced applications is that any process spawned by a guarded application will automatically be guarded by AppGuard unless it is defined as a Power App.

The procedure recommended in the Sandboxie forum was a suggested workaround before Power Apps was added to the consumer version of AppGuard. If adding SandboxieRpcSs.exe as a Power App works (I haven't tried it but in principle it should), it is better than the suggested procedure for two reasons: -

1. Browsers should normally have Privacy set to Yes so that any folders defined as private within AppGuard cannot be accessed by the browser. Browsers access to private folders should be restricted wherever possible. Whilst you can do the same thing within Sandboxie, there may be times when you are using the browser outside of the sandbox, and it is still desirable to be able to restrict access using AppGuard.

2. Adding a MemoryGuard exception may resolve the issue but, without making SandboxieRpcSs.exe a Power App, it will still be guarded when executed from the browser and you don't want that. Assuming that adding SandboxieRpcSs.exe as a Power App works, you probably won't need the MemoryGuard exception.

One of the main uses for Power Apps is to enable processes to be launched unguarded from guarded applications. This is why you should you use Power Apps sparingly: Only with your most trusted executables and only then when necessary to resolve an issue. Power Apps provides guarded applications with a potential back door into System Space by spawning an unguarded process. In this case, SandboxieRpcSs.exe is a trusted key component of Sandboxie that should clearly be added as a Power App in order for forced applications to work properly.

Regarding the J: drive partition, AppGuard will automatically treat any additional partition as part of User Space, which means that guarded applications will have read/write access. You don't need to do anything to make this happen and you won't see it reported anywhere. It's just the way AppGuard works.

Kind regards

Dearest Pegr,

Thank you for such detailed explanation.

Best regards,

[pegr]

Originally Posted by aladdin

Dearest Pegr,

Thank you for such detailed explanation.

Best regards,

You're most welcome, and I hope you enjoy AppGuard.

Kind regards

[silat]

Originally Posted by pegr

You're most welcome, and I hope you enjoy AppGuard.

Kind regards

Hi Pegr,

So adding SandboxieRpcSs.exe as a Power App is all one needs to do to use SB properly and without issue? No need to add the C/sandboxie folder also? Sandboxie is installed using default locations.
EDIT:
1 cannot add c/sandboxie. AppG will not let me
2 FF crashes when closing and I get error about container
3 SB hangs on emptying the SB

And this is taken from Appguard:
07/18/12 03:32:33 Prevented process <Windows Command Processor> from writing to <c:\sandbox\silat\__delete_defaultbox_01cd64cb3bbf09ea\user\current\appdata\local\mozilla\firefox\profiles\f3k5ih0u.default\urlclassifier.pset>.
07/18/12 03:32:33 Prevented process <Windows Command Processor> from writing to <c:\sandbox\silat\__delete_defaultbox_01cd64cb3bbf09ea\user\current\appdata\local\mozilla\firefox\profiles\f3k5ih0u.default\startupcache>.
07/18/12 03:32:33 Prevented process <Windows Command Processor> from writing to <c:\sandbox\silat\__delete_defaultbox_01cd64cb3bbf09ea\user\current\appdata\local\mozilla\firefox\profiles\f3k5ih0u.default\startupcache\startupcache.4.little>.
07/18/12 03:32:33 Prevented process <Windows Command Processor> from writing to <c:\sandbox\silat\__delete_defaultbox_01cd64cb3bbf09ea\user\current\appdata\local\mozilla\firefox\profiles\f3k5ih0u.default\offlinecache>.
07/18/12 03:32:33 Prevented process <Windows Command Processor> from writing to <c:\sandbox\silat\__delete_defaultbox_01cd64cb3bbf09ea\user\current\appdata\local\mozilla\firefox\profiles\f3k5ih0u.default\offlinecache\index.sqlite>.
07/18/12 03:32:33 Prevented process <Windows Command Processor> from writing to <c:\sandbox\silat\__delete_defaultbox_01cd64cb3bbf09ea\user\current\appdata\local\mozilla\firefox\profiles\f3k5ih0u.default\jumplistcache>.
07/18/12 03:32:33 Prevented process <Windows Command Processor> from writing to <c:\sandbox\silat\__delete_defaultbox_01cd64cb3bbf09ea\user\current\appdata\local\mozilla\firefox\profiles\f3k5ih0u.default\jumplistcache\y0ytqbnvwj3tjxto0uh3ga==.ico>.
07/18/12 03:32:33 Prevented process <Windows Command Processor> from writing to <c:\sandbox\silat\__delete_defaultbox_01cd64cb3bbf09ea\user\current\appdata\local\mozilla\firefox\profiles\f3k5ih0u.default\jumplistcache\xurx6mfyu7njofer7xmyla==.ico>.
07/18/12 03:32:33 Prevented process <Windows Command Processor> from writing to <c:\sandbox\silat\__delete_defaultbox_01cd64cb3bbf09ea\user\current\appdata\local\mozilla\firefox\profiles\f3k5ih0u.default\jumplistcache\xl2v17k_ziivesogwbs3ow==.ico>.
07/18/12 03:32:33 Prevented process <Windows Command Processor> from writing to <c:\sandbox\silat\__delete_defaultbox_01cd64cb3bbf09ea\user\current\appdata\local\mozilla\firefox\profiles\f3k5ih0u.default\jumplistcache\xbbg64r0nfjwg2zoitap+g==.ico>.
07/18/12 03:32:33 Prevented process <Windows Command Processor> from writing to <c:\sandbox\silat\__delete_defaultbox_01cd64cb3bbf09ea\user\current\appdata\local\mozilla\firefox\profiles\f3k5ih0u.default\jumplistcache\wodyuz9q_vgtmfrxmovpww==.ico>.
07/18/12 03:32:33 Prevented process <Windows Command Processor> from writing to <c:\sandbox\silat\__delete_defaultbox_01cd64cb3bbf09ea\user\current\appdata\local\mozilla\firefox\profiles\f3k5ih0u.default\jumplistcache\vwqgsh_britrifft2mnanq==.ico>.

[Moosehead77]

Thanks Pegr. Something useful on this program if you install anything new set it to install. Than back to high, has worked wonders for me.

[pegr]

Originally Posted by Moosehead77

Thanks Pegr. Something useful on this program if you install anything new set it to install. Than back to high, has worked wonders for me.

Yes, you do have to set the protection level to Install in order to install new programs or apply software updates. Part of the protection that AppGuard provides is to prevent software installs from occurring that you didn't intend.

Kind regards

[pegr]

Originally Posted by silat

So adding SandboxieRpcSs.exe as a Power App is all one needs to do to use SB properly and without issue? No need to add the C/sandboxie folder also? Sandboxie is installed using default locations.

The point of adding SandboxieRpcSs.exe as a Power App is purely to allow applications to be automatically forced to run in the sandbox on launch. If you don't use Sandboxie's forced application feature, you don't need to make SandboxieRpcSs.exe a Power App.

Either way, the sandbox folder needs to be in user-space because guarded applications running in the sandbox need to be able to write to it. You should be able to add C:\sandbox as an exclusion folder under the Guarded Apps tab, setting the access type to Read/Write. If AppGuard is preventing you from doing this, you may need to contact support for assistance. Alternatively, try moving the sandbox folder to another partition if you have one. By default, it will then be in user-space without the need for an exclusion. The location of the sandbox folder can be changed using the Sandboxie GUI.

Also check the protection level. If set to Lockdown, try lowering it to High. High represents the best compromise between compatibility and security, which is why it is the default when installing AppGuard.

Kind regards

[AMD]

Originally Posted by pegr

I am using AppGuard with avast! Free Antivirus without any problems so avast! IS should work too. In order to optimize performance and minimize the risk of conflict, I made the following real-time shield exclusions: -

File System Shield: AppGuardAgent.exe and AppGuardGUI.exe excluded from automatic sandboxing; and AppGuard program files folder excluded from scanning on execution.

Behaviour Shield: AppGuardAgent.exe and AppGuardGUI.exe added as trusted processes.

I didn't need to make any exceptions for avast! within AppGuard but if you do run into problems, try listing avast! services as Power Apps. You could also consider adding AVAST Software to the trusted Publisher list from an avast! digitally signed file.

Kind regards

Is Appguard similar to having Winpatrol and Secunia PSI or does it have further facilities too ?

[mick92z]

Hello, I installed the trial last night. I could not open a browser that was forced by Sandboxie.
I added SandboxieRpcSs.exe as a Power App , and also to the application exception list
I keep getting cannot mount registry hive message from Sandboxie.
Any suggestions please

[Moosehead77]

Originally Posted by mick92z

Hello, I installed the trial last night. I could not open a browser that was forced by Sandboxie.
I added SandboxieRpcSs.exe as a Power App , and also to the application exception list
I keep getting cannot mount registry hive message from Sandboxie.
Any suggestions please

Mick this is what i did to make sandboxie work. Understand im new at this too so tread with caution. Follow instructions in link its pretty easy.

-http://techexplored.com/2012/04/02/configure-appguard-to-work-with-sandboxie/-


Just remove the dashes at the beginning and end when you place it in your browser addy window.

[mick92z]

Originally Posted by Moosehead77

Mick this is what i did to make sandboxie work. .

Nice one Mousehead77,
I am up and running, excellent. I will continue with the 30 day trial, and see how it goes. Sandboxie is my priority program, but if the two continue to work together, I will buy a license.
Cheers

[Moosehead77]

Originally Posted by mick92z

Nice one Mousehead77,
I am up and running, excellent. I will continue with the 30 day trial, and see how it goes. Sandboxie is my priority program, but if the two continue to work together, I will buy a license.
Cheers

Congrats....Glad its up and running.

Really credit goes to the person who put the webpage up with the info.

But im glad i was able to help you get to the website.

So your welcome and i hope it works out for you.

[Dark Shadow]

Thats exactly what I did with to setup SBIE and AG to work as suggested by Kid Shamrock in this thread. http://www.wilderssecurity.com/showthread.php?t=310812

The problem I still have, is a longer then normal to open my browser in sandboxie session and a much longer content deletion on browser close.Two systems here both on windows 7 32 bit and same problem on both.Your mileage may very but for me to Invoc the auto deletion is a pita as It takes approx 30 seconds or so to delete and close,otherwise sandboxie alone is almost instant on both systems.

[silat]

Originally Posted by pegr

The point of adding SandboxieRpcSs.exe as a Power App is purely to allow applications to be automatically forced to run in the sandbox on launch. If you don't use Sandboxie's forced application feature, you don't need to make SandboxieRpcSs.exe a Power App.

Either way, the sandbox folder needs to be in user-space because guarded applications running in the sandbox need to be able to write to it. You should be able to add C:\sandbox as an exclusion folder under the Guarded Apps tab, setting the access type to Read/Write. If AppGuard is preventing you from doing this, you may need to contact support for assistance. Alternatively, try moving the sandbox folder to another partition if you have one. By default, it will then be in user-space without the need for an exclusion. The location of the sandbox folder can be changed using the Sandboxie GUI.

Also check the protection level. If set to Lockdown, try lowering it to High. High represents the best compromise between compatibility and security, which is why it is the default when installing AppGuard.

Kind regards

Settings were default. Anyway I called Blue Ridge and was advised to put the SB container folder into "user space" as mentioned in this thread by you.
That seems to have done the trick.
You were correct and I thank you very much. I was using this program when it was in beta but gave up after many tries as it was making it to hard to use my system. Now after this thread and your posts I am able to use AppGuard without issue.

1. Terminate all programs in SB
2. Open Sandboxie and go to:
Sandbox\Set Container Folder.
Override the default location by typing this in:
C:\Users\(USER NAME HERE)\Sandbox\%USER%\%SANDBOX%

That will move the SB container folder to the "User Space".

Thanks again to pegr and the rest of you software genius's.

[silat]

Ok Im back...
More problems..

1. Clicking on links in Outlook I get error messages("General failure. The url was .......... An error occurred in sending the command to the application") but it connects to Sandboxed browser after a delay. This error does not occur when I turn off Appguard.
2. Sandboxie will not empty the box automatically like it is set up to do.
I have to manually do so.